- [Philosophy](#philosophy)
/plugin marketplace add athola/claude-night-market/plugin install imbue@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/anti-overengineering.mdmodules/baseline-scenarios.mdmodules/branch-management.mdmodules/decision-framework.mdmodules/github-integration.mdscope-guard:worthiness-scored)scope-guard:backlog-compared)scope-guard:budget-checked)scope-guard:decision-documented)Prevents overengineering by both Claude and human during the brainstorm→plan→execute workflow. Forces explicit evaluation of every proposed feature against business value, opportunity cost, and branch constraints.
Core Belief: Not all features deserve implementation. Most ideas should be deferred to backlog until proven necessary.
Three Pillars:
Use the Worthiness formula:
(Business Value + Time Criticality + Risk Reduction) / (Complexity + Token Cost + Scope Drift)
Verification: Run the command with --help flag to verify availability.
See decision-framework.md for details.
Thresholds:
Compare against docs/backlog/queue.md:
Default: 3 major features per branch
If at capacity, must drop existing feature, split to new branch, or justify override.
Watch for Yellow/Red zones:
See branch-management.md for monitoring.
scope-guard:worthiness-scored)Score each factor (1, 2, 3, 5, 8, 13):
Details: decision-framework.md
scope-guard:backlog-compared)docs/backlog/queue.md for existing itemsscope-guard:budget-checked)Count current features in branch. If at budget (default: 3), new feature requires:
scope-guard:decision-documented)Record outcome:
scope-guard:github-issue-created completedocs/backlog/queue.md with issue linkIMPORTANT: Deferral is NOT complete until a GitHub issue exists. This prevents context loss when branches are merged or abandoned.
Key Principles:
See anti-overengineering.md for full rules and red flags.
**Verification:** Run the command with `--help` flag to verify availability.
docs/backlog/
├── queue.md # Active ranked queue
└── archive/
├── ideas.md # Deferred feature ideas
├── optimizations.md # Deferred performance work
├── refactors.md # Deferred cleanup
└── abstractions.md # Deferred patterns
Verification: Run the command with --help flag to verify availability.
When deferring, add to docs/backlog/queue.md:
| Rank | Item | Worthiness | Added | Branch/Epic | Category |
|------|------|------------|-------|-------------|----------|
| 1 | [New item description] | 1.8 | 2025-12-08 | current-branch | idea |
Verification: Run the command with --help flag to verify availability.
Re-rank by Worthiness Score after adding.
At end of brainstorming, before documenting design:
Self-invoke prompt: "Before documenting this design, let me evaluate the proposed features with scope-guard."
Before finalizing implementation plan:
Self-invoke prompt: "Before finalizing this plan, let me verify scope with scope-guard."
Periodically during execution:
Self-invoke prompt: "This branch has grown significantly. Let me check scope-guard thresholds."
When evaluating a feature, create these todos:
scope-guard:worthiness-scoredscope-guard:backlog-comparedscope-guard:budget-checkedscope-guard:github-issue-created (MANDATORY if deferring - blocks step 5)scope-guard:decision-documentedNote: Step 4 (github-issue-created) is REQUIRED when deferring items. You cannot mark decision-documented complete without first completing github-issue-created for deferrals.
superpowers:brainstorming - Ideation workflow this guardssuperpowers:writing-plans - Planning workflow this validatesimbue:review-core - Review methodology patternCommand not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.