Design Style

Community

NakanoSanku

design-style

Use this skill when the user asks to build, create, design, develop, or improve ANY frontend interface, web page, UI component, or visual element. This includes: - Building landing pages, websites, web apps, dashboards, portfolios, or any web interface - Creating UI components (buttons, forms, cards, navbars, modals, etc.) - Designing pages with React, Vue, Next.js, Svelte, or any frontend framework - Adding styling or improving visual design of existing components - Implementing specific design aesthetics (modern, dark, minimalist, brutalist, etc.) - User mentions "frontend", "UI", "UX", "design", "interface", "web design", or "styling" - User asks for "beautiful", "modern", "professional", "clean", or any aesthetic adjective - User requests help with CSS, Tailwind, styled-components, or any styling approach This skill automatically retrieves the appropriate design system prompt (Neo-brutalism, Modern Dark, Bauhaus, Cyberpunk, Material, etc.) to help create visually distinctive, production-grade frontend code instead of generic UI. IMPORTANT: Trigger this skill proactively for ANY frontend/UI work, not just when design style is explicitly mentioned.

Overview

Publisher	NakanoSanku
Repository	`OhMySkills`
Skill name	`design-style`
Stars	163
Forks	14
Bundled files	36
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
36 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by NakanoSanku on GitHub. Read the source before you install it.

Installation

Install the Design Style AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/NakanoSanku/OhMySkills.git /tmp/OhMySkills
mkdir -p .claude/skills
cp -r /tmp/OhMySkills/design-style .claude/skills/design-style

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design Style in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design Style on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design Style is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Design Style Skill

Purpose

This skill helps Claude Code create beautiful, distinctive frontend interfaces by automatically retrieving design system prompts from the prompts/ directory. Instead of producing generic UI, this skill enables Claude to build interfaces with specific design aesthetics like Neo-brutalism, Modern Dark, Luxury, Cyberpunk, and more.

When to Use

This skill is automatically invoked when:

User asks to build a web page, landing page, or web application
User requests a UI component with a specific design style
User mentions frontend, React, Vue, or web development
User asks for a specific aesthetic (e.g., "make it look modern and dark" or "use a brutalist style")

Available Design Styles

The following design systems are available in the prompts/ directory:

Academia - Scholarly, classic, refined
ArtDeco - Luxurious 1920s glamour
Bauhaus - Functionalist, geometric minimalism
BoldTypography - Type-driven design
Botanical - Nature-inspired, organic
Claymorphism - Soft, clay-like 3D elements
Cyberpunk - Futuristic, neon, high-tech
Enterprise - Professional, corporate, scalable
FlatDesign - Clean, minimal, 2D
Fluent2 - Microsoft Fluent 2 Design System
HumanistLiterary - Warm, literary, conversational (Claude aesthetic)
Industrial - Raw, mechanical, utilitarian
Kinetic - Dynamic, motion-focused
Luxury - Premium, elegant, sophisticated
Material - Google Material Design
Maximalism - Bold, expressive, abundant
MinimalDrak - Minimal dark theme (note: typo in original)
ModernDark - Contemporary dark UI with depth
Monochrome - Black and white, high contrast
Neo-brutalism - Bold, raw, colorful brutalism
Neumorphism - Soft UI, skeuomorphic
Newsprint - Newspaper-inspired
Organic - Natural, flowing forms
PlayfulGeometric - Fun geometric shapes
Professional - Clean, business-focused
Retro - Vintage, nostalgic
Saas - Modern SaaS aesthetic
Sketch - Hand-drawn, artistic
Swiss - International Typographic Style
TerminalCLI - Command-line interface aesthetic
Vaporwave - 80s/90s aesthetic, nostalgic
Web3 - Decentralized, crypto-inspired

How It Works

Step 1: Understand User Intent

When the user requests frontend work, first determine:

Tech stack - What framework are they using? (React, Vue, Next.js, etc.)
Design preference - Did they mention a specific style or aesthetic?
Component scope - Single component, full page, or entire application?

Step 2: Select Design Style

If user specifies a style:

Match their request to available styles (e.g., "brutalist" → Neo-brutalism)
Case-insensitive matching (brutalism, Brutalism, BRUTALISM all work)

If user doesn't specify:

For modern, professional projects → ModernDark or Professional
For creative, bold projects → Neo-brutalism or BoldTypography
For minimal, clean projects → FlatDesign or Swiss
For enterprise/corporate → Enterprise

Ask the user if you're uncertain about which style fits their needs.

Step 3: Retrieve Design System

Use the Read tool to load the appropriate prompt file:


Read: prompts/<StyleName>.md

For example:

prompts/Neo-brutalism.md
prompts/ModernDark.md
prompts/Cyberpunk.md

Step 4: Apply Design System

Once you've loaded the design system prompt:

Internalize the design philosophy - Understand the core principles, visual signatures, and differentiation factors
Extract design tokens - Colors, typography, spacing, shadows, borders
Follow component patterns - Use the specified button styles, card layouts, etc.
Apply the "Bold Factor" - Implement signature elements that make the design authentic
Avoid anti-patterns - Don't use techniques that break the aesthetic

Step 5: Build with Context

Before writing code:

Identify the user's existing tech stack
Understand their component architecture
Note any constraints (CSS frameworks, design libraries, etc.)

When writing code:

Match their existing patterns and conventions
Centralize design tokens in CSS variables or a config file
Create reusable, composable components
Explain your architectural choices briefly

Quality standards:

Preserve or improve accessibility
Ensure responsive design across devices
Make deliberate, creative design choices (not generic boilerplate)
Leave the codebase cleaner than you found it

Examples

Example 1: User Specifies Style

User: "Create a landing page for my SaaS product with a neo-brutalist design"

Skill Actions:

Detect keywords: "landing page", "neo-brutalist"
Map "neo-brutalist" → prompts/Neo-brutalism.md
Read the design system prompt
Ask clarifying questions: "What tech stack are you using? React, Vue, or plain HTML/CSS?"
Build the landing page following Neo-brutalism principles (thick borders, hard shadows, bold colors, etc.)

Example 2: User Doesn't Specify Style

User: "Help me build a portfolio website"

Skill Actions:

Detect: "portfolio website" (creative context)
Suggest options: "Would you like a specific design style? I can create it in Modern Dark (sophisticated), Neo-brutalism (bold and creative), or Swiss (minimal and clean)."
User responds with preference
Load appropriate prompt and build

Example 3: Component Request

User: "Add a contact form to my Next.js app. Make it look modern and professional."

Skill Actions:

Keywords: "Next.js", "modern and professional"
Select: ModernDark.md (modern) or Professional.md (professional)
Read design system
Build form component matching their Next.js patterns
Use design tokens from the prompt (colors, typography, shadows, etc.)

Quick Reference Commands

When implementing, you can quickly reference specific sections:

Colors:


Grep: pattern "Token|Value|Usage" path "prompts/<Style>.md"

Typography:


Grep: pattern "Font|Weight|Size" path "prompts/<Style>.md"

Component Patterns:


Grep: pattern "Button|Card|Input" path "prompts/<Style>.md"

Tips for Best Results

Read the full prompt - Don't just skim. The design philosophy and differentiation sections are critical.
Implement signature elements - Every design system has a "Bold Factor" section. These elements are what make it authentic.
Avoid anti-patterns - Each prompt lists what NOT to do. Follow these rules strictly.
Ask questions - If the user's needs are unclear, ask before building.
Match existing code - Don't fight their tech stack. Integrate the design system into their existing patterns.

Notes

All design system prompts follow the same structure: <role> and <design-system> sections
Prompts include detailed color palettes, typography scales, component patterns, and implementation examples
Each style is production-ready and has been carefully crafted for visual distinctiveness
The prompts are designed to prevent generic, AI-looking interfaces

Future Enhancements

Potential improvements to this skill:

Style combination support (e.g., "Cyberpunk + Minimal")
Custom style creation workflow
Design token extraction to JSON/CSS
Component library generation from prompts

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Design Style AI skill do?

Why use Design Style on TypingMind?

Because you install it once and use it with any model. Design Style is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design Style in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/NakanoSanku/OhMySkills/tree/main/design-style. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Design Style?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design Style?

As many as you like. As long as a model supports skills, you can use Design Style with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design Style AI skill free?

It is published on GitHub by NakanoSanku. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Canvas Design

anthropics

OrganizationPopular

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create…

Frontend Design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated…

Web Artifacts Builder

anthropics

OrganizationPopular

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state…

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors",…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Design Style Skill

Purpose

When to Use

Available Design Styles

How It Works

Step 1: Understand User Intent

Step 2: Select Design Style

Step 3: Retrieve Design System

Step 4: Apply Design System

Step 5: Build with Context

Examples

Example 1: User Specifies Style

Example 2: User Doesn't Specify Style

Example 3: Component Request

Quick Reference Commands

Tips for Best Results

Notes

Future Enhancements

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now