Menú
Design system architecture with components and patterns
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Close a PROJECT_PLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECT_PLAN lifecycle.
Commit a selected candidate goal into a durable, governed Goal artifact. The D71-Strict singular committer of the propose-goals→create-goal verb pair (L1067/L1085). Two-tier (REQ-3): committed goals = a structured section in governance/GOALS.md; aspirational = agent-internal .aget/goals/aspirational.jsonl. Direct authoring of a committed-Goal section is PROHIBITED once this skill is invoked. Implements AGET_GOAL_SPEC v0.2.0 (CAP-GOAL-001..011).
Scaffold approved initiative manifests at planning/initiatives/INIT-*.md. Mirrors /aget-create-project STRICT (D71 Layer 2) — direct Write/Edit to planning/initiatives/ is PROHIBITED once this skill is invoked. Implements SOP_initiative.md (graduated procedure) + future AGET_INITIATIVE_SPEC. Consumes PROPOSAL_init_*.md substrate produced by /aget-propose-initiative.
Create lightweight initiative proposals (PROPOSAL_init_*.md) before full INIT-*.md scaffolding. Follows 'propose -> review -> approve -> create' governance pattern. Advisory enforcement. Implements AGET_INITIATIVE_SPEC v1.0.1 CAP-INIT-PROP-001..012.
Record principal authorization (GO) with Healthy Friction enforcement of the principle-triad (spec+verify-first, coherence-next, evidence-driven); release agent execution within authorized scope. Authorization-only — does not execute the authorized work.
Generate standalone narrative documents from session artifacts, optimized for a target consumption medium (NotebookLM, slides, memo, share-draft). Use when the user says "create briefing", "create a briefing for NotebookLM", "make this listenable", "summarize session for [medium]", "prepare a listen", "brief me on [topic]", or "create a summary I can share".
| name | aget-design-architecture |
| description | Design system architecture with components and patterns |
| archetype | architect |
| allowed-tools | ["Read","Glob","Grep"] |
Design system architecture including components, relationships, and patterns. Addresses quality attributes and produces architectural artifacts.
When this skill is invoked:
Understand Requirements
Decompose the System
Select Patterns
Define Relationships
Address Quality Attributes
## Architecture Design: [System Name]
### Overview
[2-3 sentence description of the architecture]
### Components
| Component | Responsibility | Interface |
|-----------|---------------|-----------|
| [Name] | [What it does] | [API/Events/etc.] |
### Architecture Diagram
┌─────────────┐ ┌─────────────┐ │ Component A │────▶│ Component B │ └─────────────┘ └─────────────┘ │ ▼ ┌─────────────┐ │ Component C │ └─────────────┘
### Patterns Applied
| Pattern | Rationale |
|---------|-----------|
| [Pattern] | [Why chosen] |
### Quality Attributes
| Attribute | Approach |
|-----------|----------|
| Scalability | [How addressed] |
| Reliability | [How addressed] |
| Security | [How addressed] |
### Dependencies
A → B (sync API) B → C (async events)
### Risks & Trade-offs
- [Trade-off 1]: [What was traded for what]