design
Skill8 starsChanged 11 days agoMITView on GitHub
Very Happy UI design and visual refactoring. Use when creating or changing App pages, shared components, responsive layouts, loading, branding, Landing, docs, login, or product screenshots. Preserve real features while applying the approved compact workspace style.
198 other projects use a version of this.
Adopted by
Most recently taken up by
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- GoBeromsu/craft-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- StitchSlop/claude-plugintheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- fatihkan/baditheir own version, first seen Nov 16, 2026
Used with
Projects with it also use ui-styling, infra-audit and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillui-styling
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.
Also in 39 projects that use this
mayankjain1815-commitsSkillinfra-audit
Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.
Also in 3 projects that use this
JetBrainsSkillslides
Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.
Also in 42 projects that use this
AnthropicSkilldesign-system
Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.
Also in 49 projects that use this
henrikthome-archSkillinfra
Manage all infrastructure for the Volos school project — Render (API backend), Cloudflare (DNS + Pages frontend), PostgreSQL database, and GitHub Actions workflows.
Also in 3 projects that use this
Daeguk-SunSkillacceptance
story 또는 epic 구현 완료 후 제품 단위 검수를 수행하는 MVP skill. 사용자가 "/acceptance story", "/acceptance epic", "story 검수", "epic 검수", "AC 기준으로 완료됐는지 봐줘" 등을 말할 때 사용한다. full E2E 검증은 MVP 범위 밖이지만, 핵심 AC가 mock-only green이나 대상 사용자에게 부적합한 입력/진행 동선으로만 닫히는 것은 gap으로 분리한다. direct `/impl` 단발 작업에 자동 강제하지 않는다.
Also in 3 projects that use this
Other versions198 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 198
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tokio-rs/toasty★ 3.3ksame name
- PaulWoitaschek/Voice★ 3.3ksame name
- joye61/pic-smaller★ 2.9ksame name
- oxsecurity/megalinter★ 2.7ksame name
- Infisical/agent-vault★ 2.5ksame name
- static-web-server/static-web-server★ 2.4ksame name
- SethGammon/Citadel★ 927same name
- Ohh-889/skyroc-admin★ 795same name
188 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- control-flowSkill
- devSkill
- metrics-graphanaSkill
- office-hoursSkill
- releaseSkill
- sessionsSkill
- agent-browserSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read docs/design-language.md from the repository root before changing UI.
- Very specific: line 14
Verify real rendered pages in light/dark, desktop and 320/390px coarse viewports.
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Very Happy design
Read docs/design-language.md from the repository root before changing UI. It is the sole design authority; packages/happy-web-v2/src/styles/tokens.css owns concrete tokens. Do not substitute a fresh style or copy the review prototype's reduced feature set.
- Product direction: compact, content-first workspace inspired by Codex, with the Very Happy reverse-video
^_^block mark (B-724; rules in design-language §Logo) and live connection signals. Public Landing/docs/login must retain deliberate brand expression; workspace density does not mean shrinking public hero sections. - Surfaces, borders and depth follow
docs/design-language.md§2.1 (CDS-derived, B-614): the 1-Border Rule (at most one closed outline per line of sight — no card wrapping a card), the surface/alpha ladder, radius/motion tokens and the shared atoms insrc/styles/surfaces.css(.vh-panel,.vh-pill,.vh-segmented). Runnode scripts/dev/nesting-audit.mjs --base <dev-server>(target 0 violations) before shipping UI that adds borders. - For a visual migration, inspect actual routes, actions, capability checks, shortcuts and persistence first. Use
specs/2026-09-workspace-entry-audit.mdas an index, then verify current code. Record coverage inspecs/2026-09-workspace-rollout.md; a pretty fixture is not proof of retained functionality. - Reuse
ui/primitives and real feature components. Migrate owners instead of appending a parallel override stylesheet. Delete superseded components/assets only after checking imports and route references; compare production entry/chunk sizes and avoid new dependencies for cosmetic work. - Verify real rendered pages in light/dark, desktop and 320/390px coarse viewports. Use
scripts/dev/css-probe.mjsbefore/after, including pixels for layered decoration. Keep xterm geometry and always-dark behavior separate. Mobile editable controls use 16px; keyboard focus remains visible without external glow. - Touch (design-language §6 U1–U3, B-798): long-press is only a shortcut — every
ActionContextMenurow also shows a ⋯ over the same items; hide row actions only inside@media (hover: hover) and (pointer: fine)(visible by default); touch targets are 44×44 (widen small visuals with an absolute::after). Gates: linthover-reveal-needs-touch/touch-target,src/ui/touchParity.test.ts, andscripts/dev/device-shots.mjs(smallTargets/hiddenActionsagainstscripts/dev/touchGate.mjs). - Documentation and screenshots must show the implemented UI. Update Landing/docs/README together with user-visible release notes; test workflows from the coverage matrix, not only screenshots. Mark fixtures as examples and do not invent connection/model metrics.
界面审查清单
审查界面、截图或原型时(包括 review 别人的 UI PR),逐条对照 docs/design-language.md 检查:配色语义、对话区字号、§6 的反馈时机、组件选择、文案规则,以及相邻组件是否一致。还要跑 node scripts/dev/check-design-lint.mjs --base <PR base>。结论按下面的顺序输出,每条都点名具体元素,不写泛泛的评价:
- 最该改的 3 处:按对用户的影响排序。
- 摩擦点:杂乱、没对齐、文案问题、焦点问题、流程多出来的步骤、违反 design-language 的地方,各自写明所在元素和对应条款。
- 具体改法:写到布局、层级、控件、文案、空状态和错误态、渐进展开这一层,能直接照着实现,并标出复用哪个现有组件。
- 键盘与步数:常用流程能不能 1–2 步完成;默认焦点是否落在最可能用到的字段或主操作上;Enter 是否触发预期的主操作(破坏性确认不响应 Enter);Esc 能否安静地退出。
- 缺失的外链与恢复路径:错误或空状态有没有直接的获取、配置、重试入口,以及文档、设置页链接;需要阅读或重试的错误是否常驻在行内,而不是只弹一个 toast。
Development and release mechanics remain in .agents/skills/dev/SKILL.md, .agents/skills/release/SKILL.md and docs/PROCESS.md. Design approval is not proof of implementation or deployment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

