frontend-design
Skill1 starsChanged 9 months agoMITView on GitHub
Frontend visual design constraints for web UI tasks. Use when Codex is asked to design or style UI/UX, build frontend layouts, or propose visual direction, especially when creating new pages or components outside an established design system.
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 repository13 other files it gives its agents.
- axum-single-page-uiSkill
- feishuSkill
- git-opsSkill
- gui-automationSkill
- macos-gui-automationSkill
- mermaidSkill
- npmSkill
- playrightSkill
- playwright-cliSkill
- pythonSkill
- python-uvSkill
- rust-coding-styleSkill
- youtrackSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
7
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
Avoid safe, average-looking layouts.
- Distinctive: line 17
Avoid purple-on-white defaults and avoid a default dark-mode bias.
- Distinctive: line 18
Use a non-flat background: gradients, shapes, or subtle patterns to build atmosphere.
- Distinctive: line 19
Add a few meaningful animations (page-load, staggered reveals).
- Distinctive: line 20
Ensure the page loads properly and remains readable on both desktop and mobile.
- Distinctive: line 24
If working inside an existing website or design system, preserve its established patterns, structure, and visual language.
- Distinctive: line 31
Add purposeful motion that supports content scanning.
“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 Constraints
Overview
Apply a bold, intentional visual direction for frontend work while keeping layouts usable on desktop and mobile.
Core Constraints
- Avoid safe, average-looking layouts; make the design feel intentional and slightly surprising.
- Choose expressive, purposeful fonts; avoid default stacks like Inter, Roboto, Arial, or system UI.
- Define CSS variables for color and spacing to establish a clear visual direction.
- Avoid purple-on-white defaults and avoid a default dark-mode bias.
- Use a non-flat background: gradients, shapes, or subtle patterns to build atmosphere.
- Add a few meaningful animations (page-load, staggered reveals); avoid generic micro-motions.
- Ensure the page loads properly and remains readable on both desktop and mobile.
Exception
If working inside an existing website or design system, preserve its established patterns, structure, and visual language.
Execution Checklist
- Pick a clear visual direction (type, palette, background motif).
- Define CSS variables for colors, spacing, and typography early.
- Implement layout with responsive behavior and readable hierarchy.
- Add purposeful motion that supports content scanning.
- Review for default-stack fonts, purple bias, and flat backgrounds.
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.