Loading...
Loading...
Found 3 Skills
Internal/shared core rules for design-tree skills. Use only when maintaining the design-tree system itself or when another design skill needs shared governance rules for derivation, handoff, boundaries, or anti-bloat controls. Do not trigger for ordinary user design requests, and do not use as a replacement for design-orchestrator, design-structure, or design-refinement.
Build the initial design structure from a vague or partially formed idea. Use when the task lacks a clear design tree, scope boundaries, core objects, key flows, or explicit decision points. Trigger when the user has an idea, feature request, or system goal that needs to be turned into a structured design skeleton before deeper refinement. Do not use when the design tree already exists and the main need is to deepen or validate it.
Refine an existing design tree until key branches become implementation-ready. Use when the high-level structure already exists but important branches remain vague, shallow, or unresolved. Trigger when the user needs deeper decomposition, edge-case coverage, failure-path clarification, interface detail, or validation criteria for a partially designed system. Do not use to create the initial design skeleton from scratch or to compare options for a single explicit decision node.