About use-style
A design skill that selects and loads a named visual style before building, using aliases and project or global rules to resolve the style. It is for people creating visual interfaces and directs them to stop for a style choice when none can be determined.
Key features
- 01Style names and aliases
- 02Fallback style selection
- 03Project override support
- 04Style gallery preview
Use cases
- 01Load a named style before UI work
- 02Choose a style from the project rules
- 03Browse available styles before choosing
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ melvynx/ ai-maxxing-skills --skill use-styleAfter installing, type/use-stylein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlassets/codex-icon.svgexamples/anthropic.htmlblack-grid.htmldusk.htmlgallery.htmlgrid.htmlgumroad.htmlios-app.htmllinear.htmlluma.htmlnew-york-times.htmlraycast.htmlstripe.htmltestspirite.htmlvercel.htmlstyles/anthropic.mdblack-grid.mddusk.mdgrid.mdgumroad.mdios-app.mdlinear.mdluma.mdnew-york-times.mdraycast.mdstripe.mdtestspirite.mdvercel.mdDetails
From the project READMELoad 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.