use-style
Skill32 starsChanged 25 days agoMITView on GitHub
Apply a named visual style to anything the user will look at - landing pages, apps, dashboards, HTML reports, documents, visuals. Use for /use-style, "list styles", a style name (vercel, stripe, linear, raycast, anthropic, gumroad, new-york-times, dusk, luma, testspirite, grid, black-grid, ios-app), or whenever you create a file with a visual design and the global rules name a default style.
In this repository42 other files it gives its agents.
- skills/setup-my-hermes-dashboard/template/AGENTS.mdAGENTS.md
- audit-safetySkill
- betterSkill
- cleanupSkill
- create-projectSkill
- doneSkill
- dreamSkill
- projectsSkill
- setup-brainSkill
- cloudflareSkill
- code-debugSkill
- codex-imagesSkill
- connect-googleSkill
- connect-instagram-developer-platformSkill
- connect-toolSkill
- connect-vpsSkill
- connect-youtube-developer-platformSkill
- convexSkill
- create-internal-appSkill
- create-landingSkill
- create-softwareSkill
- dev-browserSkill
- grill-meSkill
- initializeSkill
- install-skillsSkill
- lumailSkill
- safe-shipSkill
- setup-cloudflareSkill
- setup-convexSkill
- setup-dev-browserSkill
- setup-githubSkill
- setup-lumailSkill
- dashboardSkill
- setup-my-hermes-dashboardSkill
- setup-nodeSkill
- setup-stripeSkill
- setup-vpsSkill
- show-meSkill
- skill-managerSkill
- stripe-checkoutSkill
- verifySkill
- wait-whatSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 13
Read styles/<name>.md from this skill folder.
- Very specific: line 14
Prefer project overrides when they exist: .agents/styles/<name>.md, <name>-theme.md.
- Distinctive: line 15
Treat the loaded style as hard constraints.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Load a named style before designing or building anything visual. Parse the name from $ARGUMENTS or the message. Aliases: ios/iphone/expo → ios-app; geist → vercel; old vercel/black grid → black-grid; testsprite/test sprite → testspirite; lu.ma → luma; nyt/newspaper → new-york-times; claude → anthropic; attio → dusk.
With no name, use the style in the ## Style section of the global rules (~/.agents/AGENTS.md). Without one, pick by what you build: Expo / React Native screens → ios-app. Builder or course landings → grid. Developer infrastructure marketing → vercel. Austere monochrome tools → black-grid. Issue tracker or dense app shell → linear. Newspaper, magazine, long read → new-york-times. Warm calm AI product → anthropic. Loud creator commerce → gumroad. Glossy dark marketing → raycast. Data-rich dark dashboard → dusk. Light paper dashboard → testspirite. Events and RSVP → luma. Clean light product UI and payments → stripe.
If the name is list or nothing matches, list the styles in styles/ with one line each and stop until the user chooses. To let the user see them, open examples/gallery.html from this skill folder (open on Mac, xdg-open on Linux, start on Windows): it shows a live preview of each style.
- Read
styles/<name>.mdfrom this skill folder. - Prefer project overrides when they exist:
.agents/styles/<name>.md,<name>-theme.md. - Treat the loaded style as hard constraints. Reuse the project's existing components and tokens before writing new ones.
Match the vibe exactly. Honor the style file's anti-patterns. Scaffold the page shell first on landing pages.
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.