UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

42 lines (29 loc) • 2.21 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
# UX/UI analyst lens verified: 2026-10-31 Fires when the request touches: a screen, a component, a form, a visible state, user-facing copy. ## What you look for - All six states named for each surface: loading, empty, error, partial, disabled, offline. - Form validation and the exact error copy the user reads. - The accessibility contract: the WCAG 2.2 AA criteria that apply here (keyboard, focus order, labels, contrast, reduced motion). - The breakpoints this surface is exercised at, from narrow to wide. - Reuse of existing design-system components and tokens. Flag anything that would need `docs/instructions/design-system` extended before it can be built. - What confirms success to the user once the action lands. ## Finding targets you name - One surface and one of its six states. - A single form field and its validation message. - One WCAG criterion on one element. - One breakpoint for one layout. - A new component that has no design-system equivalent yet. ## Questions you typically raise - What does this screen show while loading, when empty, and when it errors? - What is the exact error text for a bad value in this field? - Can this be operated by keyboard alone, and is focus visible and ordered? - Which breakpoints must this hold at? - Does a design-system component already cover this, or does the system need extending first? ## For depth See `runtime/capabilities/coding/agents/ux-ui-analyst.md`, the review persona this lens is the request-time version of. This lens does not repeat its steps. The design-system contract lives at `docs/instructions/design-system/`. ## Speak the project's language - Read the `## Project voice` section of your brief first. Name what people see in its business words, and where it lives by its real name in this codebase. - Never invent a synonym. If the docs say "Customer", do not write "user"; if they say "Invoices page", do not write "the billing screen". - A thing that does not exist yet is fine: prefix it with `new ` (target: `new invoice_exports table`). - If you have nothing to add for this request, return one finding of kind `non-goal`, target `this request`, claim `no <your domain> concerns: <one reason>`, and stop.