UNPKG

paqad-ai

Version:

Spec-driven development framework — AI agents that think before they type

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

53 lines (38 loc) • 2.2 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
--- name: ux-state-machine description: 'Defines interface states and transitions for UI-heavy work. Use when a UI change adds async behavior, branching flows or recovery paths that are hard to reason about from the happy path.' metadata: model_tier: medium cacheable: 'true' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Defines the user-visible states, transitions, and triggers for a changed interface so design, implementation, and documentation all operate from the same state model. ## Use This When When a UI change introduces new async behavior, branching flows, or recovery paths that are hard to reason about from the happy path alone. ## Inputs - Read the affected screen or component docs and any existing state inventory first. - Read `references/state-inventory-template.md` before enumerating states. - Read `runtime/capabilities/coding/checklists/edge-cases-coding.md` to avoid missing loading, stale, and error paths. ## Procedure 1. Walk `assets/canonical-states.txt` (idle, loading, success, empty, error, disabled, stale, permission, retry); include every state the UI actually exposes. 2. For each transition, name the trigger explicitly (user event, async resolve, timeout, permission denied): never imply it. 3. Build the table per `assets/output.template.md` (From / Trigger / To / Notes). 4. Surface any contradictory or undocumented state under `## Gaps`. 5. Validate with `scripts/lint-output.sh`. ## Output Contract - Return sections named `State Inventory`, `Transitions`, and `Gaps`. - Each state entry must name the visible UI condition and the user or system trigger. - If no gaps remain, write `Gaps: none`. ## Escalate / Stop Conditions - Ask when the request does not define the source of async updates, permissions, or recovery behavior. - Warn when two states imply conflicting outcomes for the same trigger. - Do not collapse materially different visible states into one generic label. ## Resources - `references/state-inventory-template.md` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/canonical-states.txt` - `runtime/capabilities/coding/checklists/edge-cases-coding.md` - `agents/openai.yaml`