@ryuenn3123/agentic-senior-core 4.3.8 → 4.3.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -7,8 +7,24 @@ Use this prompt for UI, UX, frontend layout, screen, or redesign work. Create or
|
|
|
7
7
|
- Use current repo evidence, project docs, and `.agent-context/` as style context.
|
|
8
8
|
- Do not copy layout rhythm, palette, component skin, or brand posture from external references without explicit user approval.
|
|
9
9
|
- WCAG 2.2 AA is the hard compliance floor.
|
|
10
|
+
- When generating any UI component that renders or accepts user data, explicitly state in the prompt: "ensure all user-supplied input is sanitized, all status indicators have non-color alternatives, and all interactive elements have visible focus states."
|
|
10
11
|
- Before choosing a new UI library, research current official docs.
|
|
11
12
|
|
|
13
|
+
## Design Reference Retrieval
|
|
14
|
+
|
|
15
|
+
Before generating tokens from scratch, check if a proven brand reference matches
|
|
16
|
+
the product aesthetic. Run `npx getdesign list` to see all available references.
|
|
17
|
+
Pick by spatial mechanics and typographic character, not by color.
|
|
18
|
+
|
|
19
|
+
Fetch: `npx getdesign add <slug> --out docs/DESIGN.md`
|
|
20
|
+
|
|
21
|
+
Customize: replace brand colors with product OKLCH equivalents, replace brand name
|
|
22
|
+
with product name, remove brand iconography, keep spatial rhythm and density logic.
|
|
23
|
+
|
|
24
|
+
If no brand matches or terminal is unavailable, skip and generate from scratch below.
|
|
25
|
+
|
|
26
|
+
Source: https://github.com/VoltAgent/awesome-design-md
|
|
27
|
+
|
|
12
28
|
## Design Direction Process
|
|
13
29
|
|
|
14
30
|
1. **Name Your Defaults**: Name three temptations (e.g. SaaS admin default, AI-startup landing) and why they flatten this product. Derive your search direction by rejecting them.
|
|
@@ -50,3 +66,13 @@ Only three gates. Do not add more:
|
|
|
50
66
|
1. Anchor exists and is specific.
|
|
51
67
|
2. Token values are derived from the anchor.
|
|
52
68
|
3. WCAG 2.2 AA compliance floor is met.
|
|
69
|
+
|
|
70
|
+
## Pre-Commit Critique
|
|
71
|
+
|
|
72
|
+
Before committing any UI output, answer:
|
|
73
|
+
|
|
74
|
+
1. Rename test: if the product name changed to an unrelated category, would this UI still look identical? Yes = too generic, reset anchor.
|
|
75
|
+
2. Token drift test: does any color, font, or spacing in the output contradict the DESIGN.md token definitions? Yes = align before commit.
|
|
76
|
+
3. Security test: is user-controlled data rendered unsanitized, or does any status depend on color alone? Yes = fix before merge.
|
|
77
|
+
|
|
78
|
+
Max 3 revision cycles. If unresolved, reset the anchor entirely.
|