メニュー
Use after modifying existing systems to update blueprint documentation. Read blueprints before changes, update after. Prevents documentation drift.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.
Use when handling async operations in Angular applications with observables, operators, and subjects.
Use when building Angular 16+ applications requiring fine-grained reactive state management and zone-less change detection.
Guides end-to-end feature development through 8 phases: discover requirements, explore codebase patterns, clarify ambiguities with the user, design architecture, implement with TDD, run multi-agent code review, validate all quality gates, and write a blog post. Use when asked to add a feature, implement a new capability, build functionality, or develop a feature end-to-end.
Use when creating or modifying Han plugins. Covers plugin structure, configuration, hooks, skills, and best practices.
Minimize token consumption through efficient tool usage patterns
| name | blueprints-maintenance |
| user-invocable | false |
| description | Use after modifying existing systems to update blueprint documentation. Read blueprints before changes, update after. Prevents documentation drift. |
| allowed-tools | ["Read","Write","Edit","Grep","Glob"] |
Documentation drifts from implementation when:
Find relevant blueprints:
# Search for blueprints related to your system
Grep("auth", path: "blueprints/", output_mode: "files_with_matches")
# Read the blueprint to understand current documentation
Read("blueprints/authentication.md")
Note what documentation exists:
Plan documentation updates alongside code changes
Re-read the blueprint to verify accuracy:
Read("blueprints/authentication.md")
Verify each section:
Update the blueprint:
# Read current content, modify as needed, write back
Write("blueprints/authentication.md", updated_content_with_frontmatter)
Remove stale content - outdated docs mislead
When adding functionality:
When changing behavior:
When deprecating or removing:
When restructuring without behavior changes:
Signs blueprints need attention:
Prioritize by impact:
When reviewing blueprints:
## Verification Checklist
- [ ] Overview matches current purpose
- [ ] All public APIs documented
- [ ] API signatures accurate
- [ ] Examples execute correctly
- [ ] Behavior matches implementation
- [ ] File paths exist
- [ ] No removed features documented
- [ ] Related systems links work
- [ ] No duplicate content with other blueprints
/blueprints command to regenerateThe blueprints hooks automatically: