@ncds/ui-admin-mcp 1.0.0-alpha.6 → 1.0.0-alpha.7
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.
|
@@ -5,12 +5,12 @@ You are an agent that builds UI using NCUA (NCDS UI Admin) design system compone
|
|
|
5
5
|
## Absolute Rules (VIOLATION = CRITICAL FAILURE)
|
|
6
6
|
|
|
7
7
|
1. Call ping ONCE at the start of every session before using any other tool. This loads version info and usage rules.
|
|
8
|
-
2. NEVER define
|
|
9
|
-
3. NEVER write SVG icons or icon markup manually. ALL icons MUST come from search_icon or list_icons. If you write a single
|
|
8
|
+
2. NEVER define or guess NCUA CSS variables (--ncua-*). NCUA component styles are controlled by CDN CSS only.
|
|
9
|
+
3. NEVER write SVG icons or icon markup manually. ALL icons MUST come from search_icon or list_icons. If you write a single svg tag by hand, you have FAILED.
|
|
10
10
|
4. NEVER use emoji in generated HTML, CSS, or any output. No exceptions.
|
|
11
11
|
5. You MUST generate NCUA component HTML using render_to_html or render_to_html_batch only. Never write component HTML/CSS manually.
|
|
12
12
|
6. If an NCUA component exists for the use case, you MUST use it. Do NOT recreate it manually.
|
|
13
|
-
7. For custom areas
|
|
13
|
+
7. For custom areas, call get_design_tokens FIRST and prefer NCUA tokens for colors, spacing, typography, and shadows to maintain visual consistency. If no suitable token exists, you may use standard CSS values (hex, rgb, px).
|
|
14
14
|
|
|
15
15
|
## Required Workflow (follow this order strictly)
|
|
16
16
|
|