Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
Before any creative or architectural work — feature design, component creation, or behavioral changes. Used when a direction needs to be decided quickly with the user.
A clear, approved direction with rationale and key decisions, enabling fast, focused implementation without process overhead.
Use Cases
A developer is about to add a new feature to a web app. They invoke fun-brainstorming first. The skill assesses context, asks 2 multiple-choice questions about scope, proposes 2 implementation approaches with trade-offs, and gets approval. This prevents building the wrong thing and aligns the team in minutes instead of after a sprint.
An architect needs to change a module's behavior but is unsure of the best approach. Using fun-brainstorming, they batch questions on constraints, receive a recommended option with reasoning, and approve it. The chosen direction is captured inline. This saves time over formal design docs and keeps momentum on small-to-medium tasks.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
