agentleFS
MarvellbrazilMarvellbrazil/my-agentic-skills/skills/design-it/SKILL.md

design-it

Skill4 starsChanged 51 days agoMITView on GitHub

Routes frontend design tasks to 48 specific UI styles. Triggers for websites, app screens, or UI components requesting a specific aesthetic.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  1. Distinctive:

    Use this skill when a user requests building any frontend interface (website, app screen, UI component) and you want to apply a specific, …

    line 19
  2. Distinctive:

    When a user asks you to build a frontend interface (web or app):

    line 23
  3. Distinctive:

    Identify the Style (Fuzzy Matching): Look for keywords in their prompt (e.g., "minimal", "glass", "retro").

    line 24
  4. Distinctive:

    If they don't specify a style, choose one that best fits the project context.

    line 30
  5. Very specific:

    Read the Style Reference: Check the Style Index below to find the correct path for the chosen style.

    line 31
  6. Distinctive:

    Pick a Palette: If the user explicitly defined a theme or colors, use their requested colors.

    line 32
  7. Distinctive:

    Execute: Write the code following the specific principles of the chosen style.

    line 33
  8. Distinctive:

    If the user provides their own colors, use them.

    line 36
  9. Very specific:

    Web (React/Vue/HTML): Use CSS variables natively.

    line 163
  10. Distinctive:

    Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.

    line 169

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design-It: Sophisticated UI Style Router

This is the main entry point for the design-it skill system. Instead of falling back to generic "AI slop" aesthetics, you have access to 48 distinct, deeply opinionated design styles.

When to Use

Use this skill when a user requests building any frontend interface (website, app screen, UI component) and you want to apply a specific, opinionated design aesthetic instead of generic defaults.

How to Use This Skill

When a user asks you to build a frontend interface (web or app):

  1. Identify the Style (Fuzzy Matching): Look for keywords in their prompt (e.g., "minimal", "glass", "retro"). You do not need an exact match. Use your semantic understanding to map their request to one of the 48 styles. For example:
    • "Apple style" or "VisionOS" -> spatial-design, bento-ui, or glassmorphism
    • "Windows 8" or "Metro" -> tile-design
    • "Terminal" or "Hacker" -> sci-fi-interface or brutalist-typography
    • "Bauhaus" or "Clean" -> swiss-design
    • "Cyber" or "Matrix" -> cyberpunk-ui If they don't specify a style, choose one that best fits the project context.
  2. Read the Style Reference: Check the Style Index below to find the correct path for the chosen style. Use the view_file tool to read its specific SKILL.md.
  3. Pick a Palette: If the user explicitly defined a theme or colors, use their requested colors. If they did NOT specify colors, you MUST choose from one of the 10 Universal Palettes below.
  4. Execute: Write the code following the specific principles of the chosen style. Do not blend styles unless requested.

Universal Color Palettes

If the user provides their own colors, use them. Otherwise, you MUST use one of these 10 award-winning, highly sophisticated palettes to avoid generic neon/purplish gradients. When picking a palette, stick to these exact hex codes and establish CSS variables for them.

  1. Yacht Club (Nautical / Classic Elegance)
    • Backgrounds: #F9F6F0
    • Primary Text/Accents: #1B2A49
    • CTA/Highlights: #C85A32
    • Secondary Base: #E2D8C9
  2. Desert Mirage (Warm / Organic)
    • Backgrounds: #F4EFEA
    • Primary Text/Accents: #2D2B2A
    • CTA/Highlights: #A65E44
    • Secondary Base: #8C8781
  3. Industrial Chic (Strong / Minimalist)
    • Backgrounds: #D1D1D1
    • Primary Text/Accents: #111111
    • CTA/Highlights: #9A3B3B
    • Secondary Base: #757575
  4. Monochromatic Brown (Comfort / Nostalgic)
    • Backgrounds: #D9CBBF
    • Primary Text/Accents: #4A362D
    • CTA/Highlights: #7A4C3A
    • Secondary Base: #948275
  5. Earth-Grounded Elegance (Calm / Sustainable)
    • Backgrounds: #F7F5F0
    • Primary Text/Accents: #3A4B3A
    • CTA/Highlights: #8A9A86
    • Secondary Base: #D3CEC4
  6. Minimalist Slate (Professional / Tech)
    • Backgrounds: #F4F4F9
    • Primary Text/Accents: #2B303A
    • CTA/Highlights: #5C6B73
    • Secondary Base: #C0C5C1
  7. Midnight Luxury (Premium / Dark Mode)
    • Backgrounds: #0A0A0A
    • Primary Text/Accents: #F5F5F0
    • CTA/Highlights: #B59A5F
    • Secondary Base: #1C1C1C
  8. Sophisticated Neutral (Upscale / Lifestyle)
    • Backgrounds: #E6E2DD
    • Primary Text/Accents: #1F1C1B
    • CTA/Highlights: #524036
    • Secondary Base: #B8B0A8
  9. Warm Tech (Corporate / Modern)
    • Backgrounds: #EAEAEA
    • Primary Text/Accents: #1C252E
    • CTA/Highlights: #C28F79
    • Secondary Base: #2C3E50
  10. Modern Editorial (Magazine / High Contrast)
    • Backgrounds: #F9F9F9
    • Primary Text/Accents: #121212
    • CTA/Highlights: #D44A3A
    • Secondary Base: #8F8F8F

The 60-30-10 Rule

  • 60%: Backgrounds / Secondary Base
  • 30%: Primary Text / Accents
  • 10%: CTA / Highlights

Style Index (48 Styles)

To use a style, you MUST read its file at <style-folder>/SKILL.md relative to this file's directory.

Modern UI

  • minimalism
  • flat-design
  • flat-design-2
  • material-design
  • glassmorphism
  • neumorphism
  • skeuomorphism
  • claymorphism
  • aurora-ui
  • bento-ui

Depth & 3D

  • 3d-ui
  • isometric-design
  • layered-design
  • floating-ui
  • spatial-design

Typography

  • swiss-design
  • editorial-design
  • typography-first
  • brutalist-typography

Retro & Historical

  • brutalism
  • neo-brutalism
  • retro-design
  • y2k-design
  • cyber-y2k
  • vaporwave
  • synthwave
  • frutiger-aero
  • retro-futurism

Modern Trends

  • dark-mode
  • monochromatic-ui
  • gradient-design
  • duotone-design
  • color-blocking
  • soft-pastel
  • high-contrast
  • vibrant-maximalism
  • maximalism

Futuristic

  • cyberpunk-ui
  • sci-fi-interface
  • holographic-ui
  • ai-native-ui
  • spatial-computing-ui

Data & Product

  • dashboard-design
  • card-based-design
  • widget-based-design
  • tile-design
  • data-dense-design
  • command-center-ui

Web vs App Implementation

  • Web (React/Vue/HTML): Use CSS variables natively. Prioritize CSS grid/flexbox for layout. Use CSS transitions for hover states.
  • App (React Native/Flutter/SwiftUI): Map the palettes to the framework's theme engine. Use platform-specific shadows (elevation) and animations instead of CSS transitions. Maintain the core visual principles while adapting to mobile constraints.

Limitations

  • This skill does not replace environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.