design-build
Skill4 starsChanged 5 days agoMITView on GitHub
Implement or refine frontend visual design, CSS, layout, typography, color tokens, and component states. Use when creating or styling an interface.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- PRoBoT2004/deck-skilltheir own version, first seen Nov 8, 2026
- boman-ng/skillstheir own version, first seen Oct 25, 2026
- ZachArticulateV/designer-pro-and-seotheir own version, first seen Oct 19, 2026
- accountsFON/Claude-Skillstheir own version, first seen Mar 25, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- yagizdo/quiver★ 16same name
- ZachArticulateV/designer-pro-and-seo★ 10same name
- boman-ng/skills★ 2same name
- accountsFON/Claude-Skills★ 0same name
- PRoBoT2004/deck-skill★ 0same name
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 repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- design-validateSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-feedback-and-performanceSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-reviewSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read only the specialist playbooks matching the design problem.
- Very specific: line 18
Verify screenshot comparisons at representative content lengths, mobile/tablet/desktop, zoom, themes and loading states.
- Very specific: line 25
Use references/implementation-contracts.md for CSS/token examples and state/viewport acceptance checks.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Build coherent, aesthetic, accessible frontend design
Scope
Implement visual design decisions within the existing product requirements and design system. Use specialist guidance for the specific composition problem.
Procedure
- Read before styling: existing brand/semantic tokens, component library, themes, accessibility target, user workflows, supported locales and responsive breakpoints. Do not invent a new visual identity if one exists.
- Choose the screen's purpose and focal point. Sketch content hierarchy and source/DOM order first. Select grouping, grid, whitespace and type roles before decoration.
- Read only the specialist playbooks matching the design problem. Use
../design-diagnose/references/remediation_recipes.jsonfor relevant repairs; avoid loading all ten specialists. Map visual primitives to semantic roles and existing components. Prefer scoped variables,minmax,clamp, flexible measures and maintained theme tokens over hardcoded one-off values. - Implement complete visual states: default, hover, focus-visible, active, disabled, loading, empty, error and success, plus dark theme if supported. Color is not the only indicator; focus rings and meaningful contrast must remain clear.
- Verify screenshot comparisons at representative content lengths, mobile/tablet/desktop, zoom, themes and loading states. Check actual task behavior with
ux-buildand accessibility withwcag-build. Design tokens are not a shortcut around interactive or WCAG tests. - Deliver a narrow component/style diff, explicit rules for reuse, and a short verification record. Avoid a giant custom design-system framework for one simple page.
Defaults are hypotheses, not mandates
A modest modular type scale, restrained palette, consistent spacing tokens, one main accent and intentional negative space are good starting points. Do not enforce 60/30/10 color area, a golden ratio, one hero or two fonts as immutable constraints. Dense dashboards, localized interfaces and critical operations may demand different treatments.
Use references/implementation-contracts.md for CSS/token examples and state/viewport acceptance checks.
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.