concept-design
Installation
SKILL.md
Concept design
Summary of Daniel Jackson's concept design: Application = Concepts + Synchronizations.
“With the concepts in hand, we now associate their actions through synchronizations:” — Daniel Jackson, Concept composition and sync (2022-09-14)
Start from user needs. Concepts define independent behavior; external synchronization rules compose that behavior by specifying which action completions, under which conditions, trigger subsequent actions.
Core constraints
- Each concept owns state and actions for one purpose; concepts do not invoke one another or read one another's state. External identities carry no internal structure from another concept.
- The operational principle (OP) illustrates how the purpose is fulfilled through a representative history; it does not replace the full contract or guarantee progress.
- Composition may restrict behavior but must preserve each concept's contract. Check contracts, OPs, purposes, and application scenarios separately.
- Each definition has one authoritative source. Distinguish confirmed, proposed, inferred, and open statements; test decisions with evidence, assumptions, and counterexamples. Keep unresolved matters open and unexecuted checks unverified.
- Compare alternatives, including no change or removal; revisit assumptions after repeated failures. Refactoring preserves behavior; state intentional changes explicitly.
For engineering design, implementation, review, or project rules, apply the architecture contract for directories, naming, responsibilities, and dependencies.