design-tree-core
Design Tree Core
Overview
This skill is the shared governance core for the design-tree skill family.
It is not a general design skill. It is not a user-facing entrypoint for normal design work. It exists to define the minimum shared contract that all design-tree skills must honor.
Its job is to protect only the rules that stay stable across the family:
- required
design_statefields (including the mandatorydesign_target_type) design_target_typevocabulary and the prohibition on silent inference- derivation criteria
- parent/child handoff contracts
- anti-bloat governance
When to Use
More from freeacger/loom
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
23writing-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
22test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
22executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
22systematic-debugging
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
22finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
20