メニュー
Document an anti-pattern to avoid (any subject — code, schema, UI, infra)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | blueprint:bad-pattern |
| description | Document an anti-pattern to avoid (any subject — code, schema, UI, infra) |
| argument-hint | [description] - [correct approach] |
| allowed-tools | ["Glob","Grep","Read","Write","Edit","EnterPlanMode","ExitPlanMode"] |
COMMAND: Document something to avoid and the correct alternative. Anti-patterns are tree-agnostic — file all entries in patterns/bad/anti-patterns.md regardless of subject (code, database model, UI, infra).
| Input | Action |
|---|---|
/bad-pattern any type - use unknown | Document with both bad and good |
/bad-pattern inline SQL | Ask for correct approach |
/bad-pattern modal traps focus on close - return focus to trigger | UI anti-pattern, same file |
/bad-pattern | Ask what to document |
Add to patterns/bad/anti-patterns.md:
## [Category]: [Description]
**Severity:** Critical | High | Medium | Low
### Don't Do This
```[language]
[bad code]
Problems:
[good code]
Why: [Explanation]
## Severity Guide
- **Critical**: Security, data loss, accessibility violations (WCAG failures), destructive actions without confirmation
- **High**: Performance, maintenance burden, broken interaction patterns
- **Medium**: Code smell, inconsistent visual language
- **Low**: Style preference
## Output
Anti-pattern documented in patterns/bad/anti-patterns.md
If details missing, use TBD markers.
Capture decisions and context from the current conversation into blueprint docs, DESIGN.md, and design trees
Record a decision or cross-cutting design rule with rationale. Triages tech vs UX vs DESIGN.md rules vs requirements into the right document type and tree.
Explain Blueprint Mode plugin and available commands. Use when the user asks about Blueprint features, how to use skills, or needs guidance on the intent-capture workflow.
Opt-in. Add design intent capture to a Blueprint repo. Scaffolds design/ux-decisions/, offers to scaffold a minimal community-format DESIGN.md if absent, and can optionally surface a small number of candidate UX decisions found in existing UI/code for the user, developer, or designer to confirm.
Create Blueprint structure from existing repo. Run multiple times to refine.
Show overview of project's Blueprint structure plus important adjacent DESIGN.md context. Use when the user asks about documented decisions, project status, or wants to see what's been captured.