frontend-design-direction
Skill0 starsChanged 25 days agoMITView on GitHub
Create deliberate, distinctive, accessible frontend visual direction and interface composition grounded in the product's users and brand.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- gongyijie85/dsh-ecctheir own version, first seen Oct 13, 2026
- Fmarzochi/EGCtheir own version, first seen Sep 16, 2026
- pekral/cursor-rulestheir own version, first seen Aug 5, 2026
- SamuelNDCE/claude-super-skill-librarytheir own version, first seen Aug 1, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Fmarzochi/EGC★ 61same name
- pekral/cursor-rules★ 10same name
- gongyijie85/dsh-ecc★ 8same name
- SamuelNDCE/claude-super-skill-library★ 1same name
- davidanthonyn/claude-skills★ 0same name
- renepf/claude-skills★ 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 repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-api-engineerSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- playwright-webapp-testingSkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- qa-test-strategySkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- software-architectSkill
- technical-project-orchestratorSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use screenshots and browser testing when a UI execution environment exists.
- Distinctive: line 17
Do not substitute a static mockup for functioning behavior when the user requested an application.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Frontend design direction
- Establish audience, primary task, brand, information hierarchy, target devices and emotional tone. Explore references only when authorized/available.
- Choose a clear visual concept justified by product context, rather than adding gradients or illustrations by default.
- Plan hierarchy: navigation, primary action, content density, typography, spacing, rhythm, imagery and meaningful empty states.
- Sketch interactions and account for loading, error, partial data, zero results, disabled actions, destructive confirmation and permission denial.
- Design mobile-first; consider touch targets, keyboard navigation, readable contrast, screen readers, RTL and localization.
- Implement against the project's current design system/components; avoid unrelated framework changes or broad refactors.
- Use screenshots and browser testing when a UI execution environment exists; correct broken layouts before calling it done.
Output: visual rationale, key screen/state inventory, responsive rules, implementation details, visual verification and limitations. Do not substitute a static mockup for functioning behavior when the user requested an application.
Local RTL example
Review examples/frontend-rtl/index.html and tokens.css for a Persian RTL accessible-form prototype. The node --test examples/frontend-rtl/ui.test.mjs check covers state logic only. Perform real browser layout, keyboard and screen-reader checks before asserting visual/accessibility quality.
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.