Frontend Design

Community

thiientv

frontend-design

Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design systems, and frontend polish. Not for backend logic, API-only work, or visual claims that cannot be rendered or inspected.

Overview

Publisher	thiientv
Repository	`godmode`
Skill name	`frontend-design`
Stars	99
Forks	76
Bundled files	9
License	MIT
Links	Skill source Repository Homepage

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.
9 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by thiientv on GitHub. Read the source before you install it.

Installation

Install the Frontend Design 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.
https://github.com/thiientv/godmode/tree/main/skills/frontend-design
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/thiientv/godmode.git /tmp/godmode
mkdir -p .claude/skills
cp -r /tmp/godmode/skills/frontend-design .claude/skills/frontend-design

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

Use it in TypingMind

Enable Frontend Design 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 Frontend Design 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 Frontend Design 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.

Frontend Design

Build an interface with a point of view and a usable system, not a collection of default cards.

Before writing UI code

Inspect the existing product, design tokens, routes, components, assets, fonts, and responsive conventions. Preserve a real system unless a scoped redesign is intended.
Identify product type, user context, primary action, content hierarchy, brand constraints, supported viewport range, and available visual assets.
Extract the existing visual system before inventing one. Inspect CSS variables, theme configuration, type loading, spacing, radii, breakpoints, component variants, and recurring layout patterns. Use the dependency-free helper when the system is spread across source files:
```
bash
python3 skills/frontend-design/scripts/extract_design_system.py ./src
```
Read design-system-extraction.md before replacing or normalizing an existing token system.
Choose a visual direction and record the reason: type pairing, color role, density, shape language, imagery, and motion voice. Use the local scripts/design_system.py helper for a deterministic starting brief when a project has no design system:
```
bash
python3 skills/frontend-design/scripts/design_system.py \
  --product "analytics dashboard" --tone "technical" --stack react
```
Search the small bundled design-intelligence catalog when a choice needs comparison; read design-intelligence.md for the supported domains and limits. Do not treat a catalog result as a substitute for inspecting the existing product.
Define semantic tokens before scattering raw values through components.
Sketch the primary flow and all meaningful states: loading, empty, error, disabled, success, permission, and long-content cases.

Build the system

Use real content, realistic dimensions, and an intentional type scale.
Prefer composition and hierarchy over decorative gradients, excessive shadows, or nested card stacks.
Make controls semantic, keyboard reachable, focus-visible, and labeled.
Design mobile and intermediate widths as first-class states, not a desktop layout squeezed into a phone.
Make motion explain state or spatial continuity; provide reduced motion.
Use icons consistently and never substitute emoji for product controls.

Read design-system.md for direction, tokens, and anti-generic heuristics. Read interaction-states.md for state and accessibility detail. Read stack-adapters.md only for the detected implementation stack. Use browser-testing for a real browser flow and ui-ux-review for a separate quality pass.

Visual verification

Render the actual route at the narrow, intermediate, and desktop widths. Check hierarchy, overflow, focus, contrast, state transitions, content wrapping, and reduced-motion behavior. Exercise the primary task with keyboard-only input and run the project's accessibility tooling when available. Capture the state and viewport matrix from runtime-validation.md. Record screenshots or observations; source inspection alone cannot prove a visual claim.

Completion condition

The primary flow is usable, visual decisions are coherent and intentional, states and responsive behavior are covered, accessibility is not traded for appearance, and relevant rendered evidence is fresh.

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 Frontend Design AI skill do?

Why use Frontend Design on TypingMind?

Because you install it once and use it with any model. Frontend Design 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 Frontend Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thiientv/godmode/tree/main/skills/frontend-design. 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 Frontend Design?

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 Frontend Design?

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

Is the Frontend Design AI skill free?

Yes. It is published on GitHub by thiientv under the MIT license. 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

Grilling

mattpocock

CommunityPopular

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Api Design

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

Accessibility

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Frontend Design

Before writing UI code

Build the system

Visual verification

Completion condition

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now