Frontend Design

Community

ceilf6

frontend-design

Create distinctive, production-grade frontend interfaces with a clear visual direction while respecting project design specification constraints, existing design systems, and minimal-diff engineering boundaries. Use when building or restyling pages, landing screens, dashboards, marketing surfaces, or other frontend UI where visual quality materially affects the result.

Overview

Publisher	ceilf6
Repository	`FrontAgent`
Skill name	`frontend-design`
Stars	120
Forks	19
Bundled files	7
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.
7 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ceilf6 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/ceilf6/FrontAgent/tree/develop/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/ceilf6/FrontAgent.git /tmp/FrontAgent
mkdir -p .claude/skills
cp -r /tmp/FrontAgent/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

Use this skill to produce frontend work that feels intentionally designed rather than generic. The goal is not maximalism by default. The goal is a clear visual point of view that matches the product context and still ships as maintainable code.

Trigger

New frontend surfaces where look and feel matter:
- landing pages
- dashboards
- product pages
- hero sections
- marketing sites
- polished application views
Requests to beautify, restyle, refine, or modernize an existing UI
Cases where the code must be working and production-usable, not just a mockup

Do Not Use

Pure bug fixes, refactors, or backend tasks
Review or audit requests
Small code changes where the user did not ask for visual improvement
Existing design-system work where the user only wants strict conformance and no meaningful visual interpretation

Workflow

If the request is visually underspecified, ask only the next 1-3 questions needed to clarify audience, tone, and acceptance criteria. Use requirement-interviewer when the ambiguity is material.
Read references/design-direction.md to choose one clear visual direction before coding.
Read references/aesthetics-guidelines.md for typography, color, motion, composition, and background treatment.
Read references/integration-guardrails.md before modifying an existing codebase, design system, or shared component surface.
For a new page or major redesign, use assets/templates/visual-brief.md to form a short visual brief before implementation.
Implement working code that matches the chosen direction and stays within project constraints.
Read references/delivery-checks.md before handing off.

Output Contract

State the chosen visual direction in one short sentence when it meaningfully affects implementation.
Produce working frontend code, not mood-board prose.
Keep the implementation cohesive:
- typography should support the direction
- color should feel intentional
- motion should be meaningful, not noisy
- layout should feel composed rather than assembled from defaults
When editing an existing product, preserve the established system unless the user explicitly wants a stronger redesign.

Guardrails

Project design specification constraints, protected files, project stack rules, and user requirements remain hard boundaries.
Respect the existing design system first. Only deviate when the request explicitly calls for redesign or the current surface clearly lacks a defined visual direction.
Prefer minimal diffs for scoped tasks. Do not turn a local UI tweak into a whole-app restyle.
Do not add new dependencies, font loaders, or animation libraries unless the task clearly justifies them.
Avoid generic AI aesthetics:
- default-looking font stacks for new standalone surfaces
- timid palettes
- predictable card grids with no visual idea
- purple-gradient-on-white defaults
Do not optimize for ornament over clarity. If visual flair hurts usability, accessibility, or maintainability, scale it back.

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/ceilf6/FrontAgent/tree/develop/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 ceilf6 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

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Canvas

Present hosted widget documents on a connected macOS panel and control panel visibility or navigation.

Diagram Maker

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Grill With Docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Frontend Design

Trigger

Do Not Use

Workflow

Output Contract

Guardrails

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now