uinaf design
This is a manual skill. Its presence never authorizes uinaf styling outside explicitly scoped uinaf work.
Workflow
- Keep implementation with its owner. This package supplies the design system and general brand guidance. Product-specific UI and copy belong in that product's repository.
- Fetch one live source before writing. Prefer the MCP server at
https://design.uinaf.dev/mcpwhen it is connected:- Whole product screen →
get_page - uinaf.dev surface or export artboard →
get_template - Component →
list_patterns, thenget_pattern - Token value →
get_tokens - Voice or general rule →
search_guidelineswith one exact topic such asvoice,type,color,layout, ormotion
- Whole product screen →
- Fall back to Markdown, not memory. When MCP is unavailable, read
https://design.uinaf.dev/llms.txt, choose the one relevant link, and fetch it. Use/design.mdfor voice and general guidance and/readme.mdfor package setup. Do not load the whole catalog. If neither route is reachable, stop and report the missing design context. - Reuse the shipped system. Import
@uinaf/design/css, copy the fetched structure, and adapt content. Do not recreate a component from prose. - Finish through the owning repo's gate. Run its existing
design:checkscript through the repo's declared package manager. If the script is missing, consult/readme.md; do not install dependencies, create a ratchet, or widen the task without approval.