UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

64 lines (46 loc) • 3.55 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
54
55
56
57
58
59
60
61
62
63
64
--- name: design-system-sync description: Sync docs/instructions/design-system/* when a token, component, or breakpoint is added to source. Mirror of canonical-doc-sync. metadata: model_tier: medium cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does When a token, component, or breakpoint is added to source (Tailwind theme entry, design-token export, new component file), this skill updates the matching contract clause in `docs/instructions/design-system/*` so the contract stays in step with reality. Mirror of `canonical-doc-sync`, scoped to the design system. ## Use This When From the `documentation_sync` stage of `feature-development.yaml` whenever the diff touches: - `src/design-tokens/**` - `tailwind.config.*` - `src/components/**` (added/removed components) - A CSS-in-JS theme provider definition Also runs during `design-test` Step 5 when a finding's resolution implies the contract should expand (e.g. a `documentation-drift` finding noting a token used in code but not declared). ## Inputs - Read the diff (`git diff --name-only HEAD`). - Read the current `docs/instructions/design-system/*.md` files. - Read `references/sync-rules.md`. ## Procedure Proposal generation is deterministic: the scripts produce unified-diff hunks ready for the Decision Pause Contract. The LLM never hand-writes the diff. 1. Capture the current diff: `git diff HEAD > /tmp/sync.diff` (or read from the workflow's staged diff). 2. Run `scripts/detect-token-additions.sh /tmp/sync.diff` → `<key>\t<value>` rows for every added token-shaped entry (accepts identifier and quoted-numeric keys; only token-shaped values: hex/px/rem/em). 3. Pipe those rows into `scripts/propose-tokens-diff.sh` → a unified-diff hunk targeting `docs/instructions/design-system/tokens.md`. Surface this hunk to the user via the Decision Pause Contract. 4. Run `scripts/detect-component-additions.sh /tmp/sync.diff` → `<Component>\t<source-file>` rows for every newly-added component file (uppercase-named, under `src/components/`, not a test/spec/story/barrel/type decl). 5. Pipe those rows into `scripts/propose-components-diff.sh` → a unified-diff hunk for `components.md` with the default skeleton (variants: TBD, states: default/hover/focus/disabled, composition: TBD). 6. Never auto-apply. Surface every proposal via the Decision Pause Contract; the user accepts, modifies, or rejects each. ## Output Contract - Match `assets/output.template.md`: one proposal block per contract file affected, with the proposed unified diff. - Output is advisory; this skill never emits `## Findings`. ## Escalate / Stop Conditions - Ask when a new token replaces an existing one (e.g. `color.primary.500` value changes): that's a contract-breaking change, not a sync. - Warn when the diff removes a component that other components depend on per `components.md`. ## Resources - `references/sync-rules.md` - `scripts/detect-token-additions.sh`: extract added token-shaped `<key>: '<value>'` entries from a unified diff. - `scripts/detect-component-additions.sh`: extract newly-added component files from a unified diff. - `scripts/propose-tokens-diff.sh`: render a unified-diff hunk appending tokens to `tokens.md`. - `scripts/propose-components-diff.sh`: render a unified-diff hunk appending components (with default skeleton) to `components.md`. - `scripts/lint-findings.sh`: used when sync emits a `documentation-drift` finding inside the design-test workflow. - `assets/output.template.md` - `agents/openai.yaml`