frontend-design
Skill0 starsChanged 2 months agoMITView on GitHub
Define a distinctive and coherent visual direction for a new interface or a substantial redesign. Use when visual hierarchy, typography, color, layout rhythm, and interaction character must be decided before UI implementation; do not use for routine component edits.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- RostislavDugin/postgresustheir own version, first seen Nov 8, 2026
- databasus/databasustheir own version, first seen Nov 8, 2026
- ceilf6/FrontAgenttheir own version, first seen Nov 8, 2026
- maxtrigify/Ottotheir own version, first seen Nov 8, 2026
- rvdbreemen/OTGW-firmwaretheir own version, first seen Nov 8, 2026
- open-slide/open-slidetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use instantly-campaign, albert-dm and 10 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.
yawningwhaleAISkillinstantly-campaign
Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.
Also in 6 projects that use this
- yawningwhaleAISkill
albert-dm
Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).
Also in 5 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
- naman10parikhSkill
fractal-delegation
Also in 5 projects that use this
julianoczkowskiSkillbrief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Also in 7 projects that use this
SeifBenayedSkillfile-reading
Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.
Also in 6 projects that use this
- +6 more from naman10parikh
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- anthropics/skills★ 189ksame name
- bytedance/deer-flow★ 85ksame name
- anthropics/claude-plugins-official★ 46ksame name
- novuhq/novu★ 40ksame name
- Dokploy/dokploy★ 38ksame name
- markmead/hyperui★ 12ksame name
- mengxi-ream/read-frog★ 10ksame name
- 1weiho/open-slide★ 9.7ksame name
- open-slide/open-slide★ 9.7ksame name
- basketikun/infinite-canvas★ 9.5ksame name
177 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 repository21 other files it gives its agents.
- global/AGENTS.mdAGENTS.md
- api-designSkill
- backend-patternsSkill
- brandSkill
- contract-firstSkill
- database-migrationsSkill
- engineering-task-workflowSkill
- error-handlingSkill
- fixing-accessibilitySkill
- frontend-ui-engineeringSkill
- intent-driven-developmentSkill
- react-native-patternsSkill
- react-patternsSkill
- react-testingSkill
- security-best-practicesSkill
- shadcnSkill
- supabase-postgres-best-practicesSkill
- systematic-debuggingSkill
- tdd-workflowSkill
- ui-ux-pro-maxSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
6
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 11
Create an intentional visual direction that can be implemented in the repository's real stack.
- Distinctive: line 15
Read the product goal, audience, existing brand, screenshots, and design tokens that are actually available.
- Distinctive: line 19
Check responsive behavior, content density, interaction states, contrast, and reduced-motion expectations.
- Distinctive: line 24
Avoid generic template styling and arbitrary decoration.
- Distinctive: line 25
Do not invent brand rules when authoritative brand material exists.
- Distinctive: line 26
Do not add fonts, asset libraries, or design dependencies without a concrete requirement.
“Common” is measured: kept by at least 6 in 10 of the 181 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
Create an intentional visual direction that can be implemented in the repository's real stack.
Workflow
- Read the product goal, audience, existing brand, screenshots, and design tokens that are actually available.
- State one concise direction covering mood, hierarchy, type, color, spacing, shape, imagery, and motion.
- Preserve established product conventions unless the user requested a redesign.
- Turn the direction into concrete implementation decisions and reusable tokens where the current task needs them.
- Check responsive behavior, content density, interaction states, contrast, and reduced-motion expectations.
- Hand implementation to
frontend-ui-engineering; useimagegenonly when a raster asset is requested or clearly necessary.
Boundaries
- Avoid generic template styling and arbitrary decoration.
- Do not invent brand rules when authoritative brand material exists.
- Do not add fonts, asset libraries, or design dependencies without a concrete requirement.
- A visual proposal is not completion; verify the implemented interface in its runnable environment.
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.