design-bible-updater

Create and update a Game Design Bible with YAML frontmatter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill design-bible-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-bible-updater
Source: https://github.com/cautiouskurns/Blood-and-Gold/tree/main/.claude/skills/design-bible-updater
Command: npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill design-bible-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps design teams document, maintain, and evolve a Game Design Bible that communicates the WHY behind decisions and guides future work.

Core Features & Use Cases

  • Living document for design vision, pillars, and philosophy that evolves with the project.
  • Onboarding & alignment: accelerates onboarding of new designers and harmonizes decisions across teams.
  • Guided decision framework: supports design reviews with IS/IS NOT, changelog, and reference materials.

Quick Start

Create or update the design bible using this skill and save the result to docs/design-bible.md. Then open that file to review and share with the team.

Frequently Asked Questions about design-bible-updater

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a Game Design Bible as a living document for my team?

To maintain a Game Design Bible as a living document, use a skill that captures evolving design vision, pillars, and philosophy, saving updates directly to a file like docs/design-bible.md. This ensures the document continuously reflects current project decisions and principles.

What is the best way to onboard new designers using design principles and pillars?

Onboarding new designers with design principles and pillars is best handled by providing a central design bible document. This living artifact communicates the WHY behind decisions, accelerating onboarding and harmonizing choices across teams.

How do I resolve design tensions and align vision during design reviews?

To resolve design tensions and align vision during reviews, reference an updated design bible that includes an IS/IS NOT framework and changelog. This guided decision framework supports consistent evaluations and captures evolving philosophy.

Do I need specific formatting to document design philosophy in a markdown file?

Yes, documenting design philosophy requires a SKILL.md file with YAML frontmatter containing at least a name and description. The skill then processes this input to save the structured design bible to a specified target like docs/design-bible.md.

Can I integrate a Game Design Bible with other design documentation tools?

Yes, you can integrate a Game Design Bible with other design tools by saving the output to a standard markdown file path. This allows the generated design vision and pillars documentation to be easily shared and referenced across your existing toolchain.