Help us improve
Share bugs, ideas, or general feedback.
From blueprints
Manages blueprints directory structure preferring flat layouts, enforces kebab-case naming conventions, maintains README indexes, and prevents duplication by searching with Grep/Glob before creating new files.
npx claudepluginhub thebushidocollective/han --plugin blueprintsHow this skill is triggered — by the user, by Claude, or both
Slash command
/blueprints:blueprints-organizationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
Creates or updates technical blueprint documentation for features, APIs, and architecture. Searches existing blueprints first via Glob/Grep to avoid duplication, using standard structure and frontmatter.
Initializes Blueprint development structure: creates manifest.json, sets up optional feature tracking from requirements docs, migrates existing Markdown files to organized docs/ folders like prds/, adrs/.
Organizes project documentation into intent-based structure (BUILD/FIX/UNDERSTAND/LOOKUP) by auditing files and creating directories. Use for new projects, chaotic docs, or navigation issues.
Share bugs, ideas, or general feedback.
blueprints/
├── README.md # Index and overview
├── {system-name}.md # One file per system
├── {feature-name}.md # One file per feature
└── {integration-name}.md # One file per integration
Prefer flat structure for most projects:
Use subdirectories only for very large projects:
blueprints/
├── README.md
├── core/
│ ├── README.md
│ └── *.md
├── features/
│ └── *.md
└── integrations/
└── *.md
user-authentication.mdapi-rate-limiting.md not api.mdutils.md, helpers.mdmcp-server.md - Specific systemsettings-merge.md - Specific featuregithub-integration.md - Specific integrationoverview.md - Too generic (use README.md)misc.md - Catch-all is a smellnew-feature.md - Not descriptiveEvery blueprints/ directory needs an index:
# Technical Blueprints
Implementation documentation for {Project Name}.
## Overview
Brief description of what this project does and how blueprints are organized.
## Systems
Core systems and their documentation:
### Core
- [Settings Management](./settings-management.md) - How configuration is loaded and merged
- [Plugin System](./plugin-system.md) - Plugin discovery and loading
### Features
- [MCP Server](./mcp-server.md) - Model Context Protocol implementation
- [Hook Dispatch](./hook-dispatch.md) - How hooks are executed
### Integrations
- [GitHub Integration](./github-integration.md) - GitHub API integration
## Contributing
When adding new blueprints:
1. Check for existing related documentation
2. Use consistent naming and structure
3. Update this index
Duplicate documentation:
Search before creating using native tools
# List all existing blueprints
Glob("blueprints/*.md")
# Search for blueprints mentioning a topic
Grep("auth", path: "blueprints/", output_mode: "files_with_matches")
# Read a specific blueprint to check coverage
Read("blueprints/authentication.md")
One source of truth
Merge related topics
Cross-reference liberally
For authentication details, see [User Authentication](./user-authentication.md).
Keep together when:
Split apart when:
When systems overlap:
Document in one place, reference from others:
# System A
## Authentication
This system uses shared authentication. See [Authentication](./authentication.md) for details.
Create a shared blueprint that both reference:
# System A
Uses [Shared Auth](./shared-auth.md)
# System B
Uses [Shared Auth](./shared-auth.md)
# Shared Auth
Details here...
Document the overlap in each, scoped to that system:
# System A
## Authentication (System A Specific)
How System A specifically uses authentication...
When systems are removed:
Periodically check:
# Files not in README.md
for f in blueprints/*.md; do
grep -q "$(basename $f)" blueprints/README.md || echo "Orphan: $f"
done
# Similar file names
ls blueprints/*.md | xargs -n1 basename | sort | uniq -d
# Similar content
grep -l "specific term" blueprints/*.md