UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

54 lines (38 loc) • 2.62 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
--- name: motion-review description: 'Checks that animations meet the motion.md budgets and respect prefers-reduced-motion. Use when a design-test run has finished responsive-review.' metadata: model_tier: medium cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Audits the project's motion against `motion.md`: declared duration ceiling, easing curve set, reduced-motion behavior. Catches transitions that exceed the duration budget, ad-hoc easing curves not in the declared set, and components that ignore `prefers-reduced-motion`. ## Use This When Use for every design-test run after `responsive-review`. ## Inputs - Read `docs/instructions/design-system/motion.md`. - Read `references/motion-checklist.md`. - Read the live phase's reduced-motion screenshot results from `runtime-checks.ts` if available. ## Procedure Scan and budget parsing are deterministic: drive them with the scripts. 1. Run `scripts/parse-motion-budget.sh <motion.md>` → key/value rows: `duration-ceiling`, `easing`, `reduced-motion`. This is the declared budget. 2. Run `scripts/scan-animations.sh [search-root]` → `<file>:<line>\t<duration-ms>\t<excerpt>` rows. Every duration is normalized to milliseconds (`300ms`, `0.5s` → `500ms`, framer-motion `duration: 0.3` → `300ms`). 3. Compare each emitted ms value to the declared duration ceiling. Over budget → `motion` finding, **medium** by default. 4. Run `scripts/find-reduced-motion-violations.sh [search-root]` → one row per file that animates without `prefers-reduced-motion` or `useReducedMotion()`. Each row is a **high** severity finding (a11y blocker). 5. Cross-check with the live phase: did the reduced-motion walk produce identical screenshots to the static walk for animated components? ## Output Contract - Match `assets/output.template.md`. `contract_ref` is `motion.md → duration` / `motion.md → easing` / `motion.md → reduced-motion`. - Severity: ignored `prefers-reduced-motion` → **high** (accessibility), over-budget duration → **medium**, ad-hoc easing → **low**. - Output must pass `scripts/lint-findings.sh` (exit 0). ## Escalate / Stop Conditions - Ask when `motion.md` is missing. ## Resources - `references/motion-checklist.md` - `scripts/parse-motion-budget.sh`: declared budget from `motion.md`. - `scripts/scan-animations.sh`: every animation declaration in source, duration normalized to ms. - `scripts/find-reduced-motion-violations.sh`: files that animate without a reduced-motion guard. - `scripts/lint-findings.sh` - `assets/output.template.md` - `agents/openai.yaml`