← ClaudeAtlas

context_uiux_designlisted

Use when the user explicitly asks to establish, adopt or repair durable UI/UX Design Authority, DESIGN.md, design-system governance, visual standards, stable interaction/surface Context, Impeccable review, visual polish, frontend redesign, or when material production UI lacks sufficient or consistent Design Authority in a Minimal Context Harness project. For standalone generation of low/high-fidelity wireframes, visual candidates, a design prototype or implementation resource handoff, use design-resource-authoring instead; do not trigger this Skill solely for resource generation, routine implementation with sufficient authority, local CSS fixes, UI bugs, explicit throwaway prototypes or generic mentions of design.
Seven128/project-tiny-context-harness · ★ 3 · Web & Frontend · score 69
Install: claude install-skill Seven128/project-tiny-context-harness
# Context UIUX Design ## Package-Managed Boundary This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_uiux_design` Skill directly. Project-specific UI/UX and visual design rules belong in a separate project-local Skill under `<harnessRoot>/skills/uiux_design/SKILL.md`. When a project-local Skill and this package-managed Skill both apply, use the more specific project-local Skill as the primary instruction source while keeping durable conclusions in `project_context/**` and `DESIGN.md`. Keep the project-local Skill front matter `description` trigger keywords aligned with this package-managed Skill and the project `AGENTS.md` role-trigger rule; if the project adds or narrows trigger terms, update both places together so agent activation and Tiny Context guidance do not drift apart. ## 目标 帮助 agent 在开发工作流中审查、采纳或修复设计权威,把已经选定的界面、交互和视觉结论沉淀成可恢复的 Minimal Context 和 `DESIGN.md`,并保持实现与验证对齐。 ## Design Context Depth / 设计上下文深度 按需使用而不是默认加载全部层级:全局体验原则;跨 surface 的 Product Surface Contract;单屏 Screen Contract;可复用的 Control interaction Context;`DESIGN.md` 视觉系统/引用解释;项目原生 authored targets;verification Context。继续使用现有 `global`、`contract`、area/subdomain、`decision-rationale`、`verification` 和 `implementation-index` 角色,不新增笼统 `design` 或 `screen` 角色。 一项事实只有一个主要 owner:跨页面职责属于 Surface Context,稳定的单屏层级/交互属于 Screen/interaction Context,视觉 token/rationale 属于 `DESIGN.md`,具体构图属于 selected target,交付范围与证明属于当前任务或现有 Delivery Contract/verification。使用稳定