Loading...
Loading...
Found 17 Skills
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four types: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
architecture design system planning structure pattern integration features
Use this skill when brainstorming, designing, or planning any Swift feature. This is the right skill whenever the user describes a feature they want to build, asks "how should I implement X", wants to think through a design, or starts with something like "I want to add..." or "let's plan...". Use it even if they don't explicitly say "brainstorm" — if there's a feature to figure out, start here before touching any code.
This skill should be used when a designer wants to produce a holistic design for a full feature before it is broken into tasks — for example "design feature