Convert domain concepts into predicate-driven relationships mapped to classes and contracts.
npx skills add https://github.com/thistleknot/skills --skill architecture-thistleknot
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/thistleknot/skills/tree/main/architecture Command: npx skills add https://github.com/thistleknot/skills --skill architecture-thistleknot
It helps you turn an unclear idea or domain into a coherent system design by structuring the reasoning from first principles (FOL-style relationships), mapping concepts to code abstractions, and choosing appropriate design patterns and requirements discipline.
Use the architecture skill to design a new system by first converting your domain into predicates and entities, then mapping them into abstract classes and concrete implementations, and finally selecting GoF patterns that match the interaction and creation complexity.
High-intent search queries and answers about installing and using this skill.
System design maps domain concepts to abstract classes by converting them into predicate-driven relationships, ensuring correct dependency direction and interface segregation before implementing concrete classes.
Structure system design by organizing inputs, processes, entities, and outputs from a Dev perspective, then locking a verifiable spec to prevent scope-change churn during implementation.
Select design patterns in software architecture when facing creation, interface mismatch, or interaction complexity, using a GoF-based guide to choose creational, structural, or behavioral patterns.
FOL reasoning clarifies software requirements by expressing system structure as predicates acting on subjects and objects, defining what interacts and through which operations before locking the spec.
Yes, this system design approach applies to greenfield architecture, abstract class planning, and novel system structure by mapping domain concepts to code-level contracts with requirements discipline.
Requirements should be locked before implementation in system design to reduce nondeterministic scope changes, ensuring exploratory requirements are finalized into a verifiable spec to prevent mid-implementation churn.
zhongadamwangExtract domain concepts, entities, and relationships from requirements into JSON and Markdown.
vathymutConvert high-level specifications and tickets into executable code.
kenlckConvert a PRD into a multi-phase implementation plan with tracer-bullet vertical slices saved as Markdown.
OutlineDrivenEmits predicate-based statements and Hoare-triple framing using ASCII keywords.
