blueprints-organization

Organize blueprints in a centralized directory with kebab-case naming and a searchable index README. Before creating new blueprints, search the existing collection to prevent duplicates across system, feature, and integration blueprints, using MCP tools to read and cross-reference related documentation.

Blueprints-organization supports both flat and nested directory structures. Choose based on project scale, apply consistent kebab-case naming throughout, maintain centralized cross-references in an index README, and use MCP tooling to enforce naming conventions and search workflows.

Link related blueprints using descriptive references in your centralized index README. MCP tools enable you to search, read, and write blueprints with consistent naming, ensuring all system, feature, and integration blueprints reference each other accurately during creation and updates.

Yes, blueprints-organization applies to projects with both flat and nested directory structures. The Skill enforces consistent naming, centralized indexing, and search-before-create workflows regardless of which structure your project uses.

Searching before creation prevents duplicate documentation across your blueprint collection. Using MCP tools to search existing blueprints ensures you link to or update related content instead of creating redundant system, feature, or integration documentation.