菜单
Use after building or changing UI — when new components were added and the design system could drift (buttons, spacing, colors, badges diverging across pages). Use when you suspect UI inconsistency has crept in across sessions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when setting up a project's structure, or when the agent needs the stack, folder layout, data flow, schemas, and the hard boundary rules it must never cross. Use when code keeps crossing layers (UI logic in API routes, DB calls in components).
Use when planning what to build and in what order — splitting a project into sequenced, scoped feature phases so the agent never has to decide "what's next" on its own. Use when work feels like random feature-hopping.
Use when establishing or enforcing how code is written in a project — naming, conventions, file structure, error handling — so the agent stays consistent across sessions instead of drifting into its own style by week two.
Use when a project depends on third-party libraries and the agent needs project-specific usage rules — and must check for an MCP server or current docs — before coding against a library it only half-remembers.
Use when tracking build progress across sessions — a living checklist updated as features complete, so a new session knows exactly where work left off without re-explaining.
Use when starting a new project, or when the agent lacks a clear picture of what's being built, who it's for, and what is explicitly out of scope. Use when a build keeps producing things nobody asked for.
| name | imprint |
| description | Use after building or changing UI — when new components were added and the design system could drift (buttons, spacing, colors, badges diverging across pages). Use when you suspect UI inconsistency has crept in across sessions. |
Across sessions, UI silently drifts — slightly different buttons, off spacing, one-off colors. imprint captures new component patterns into a UI registry and reconciles the codebase against it, so the design system stays coherent without you eyeballing every page.
context/ui-registry.md): its purpose + the exact classes/tokens it uses.A ui-tokens file (colors, spacing, radius, type scale as variables) and a ui-rules file (how components look/behave). The registry is the living index imprint maintains on top of them.