TypingMindTypingMindThe best frontend for AI
Frontend Polish logo

Frontend Polish

Community
matyasstoch
frontend-polish

Improve the visual quality, cohesion, and finish of an existing frontend without changing the product direction. Use when the user asks to polish, refine, tighten, elevate, clean up, or make a UI feel more premium, clearer, or more consistent across pages, components, spacing, typography, color, motion, states, and responsive behavior.

Overview

Publishermatyasstoch
Repositorydavid-skills
Skill namefrontend-polish
Stars
61
Forks
11
Bundled files
1
Links
Skill sourceRepository
  • 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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by matyasstoch on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/matyasstoch/david-skills/tree/main/skills/frontend-polish
  4. 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.
2

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/matyasstoch/david-skills.git /tmp/david-skills
mkdir -p .claude/skills
cp -r /tmp/david-skills/skills/frontend-polish .claude/skills/frontend-polish
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Frontend Polish 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 Polish 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 Polish 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 Polish

Overview

Refine an existing interface so it feels intentional, consistent, and production-ready. Preserve the current product direction unless the user explicitly asks for a redesign.

Workflow

  1. Inspect the current UI before editing.
  2. Identify the few highest-leverage problems: unclear hierarchy, inconsistent spacing, weak typography, awkward card proportions, noisy color use, poor empty/loading states, or fragile mobile behavior.
  3. Improve the smallest surface area that creates a visible quality jump.
  4. Preserve working flows, copy meaning, and existing design-system patterns.
  5. Verify desktop and mobile behavior after changes.

Priorities

  • Strengthen visual hierarchy before adding decoration.
  • Prefer spacing, sizing, alignment, and contrast fixes over new components.
  • Make repeated UI patterns actually repeat: radii, shadows, gaps, text sizes, button styles, and card structure.
  • Use motion sparingly and only when it clarifies state or improves feel.
  • Keep accessibility intact: readable contrast, visible focus states, and sensible touch targets.

Editing Rules

  • Start from the existing visual language. Extend it; do not randomly restyle it.
  • Avoid new dependencies unless the user asks.
  • Prefer CSS and small component edits over broad rewrites.
  • Keep changes scoped and easy to review.
  • If the interface already has a design system, follow it.
  • If the interface has no clear system, create one with a few consistent tokens or repeated rules.

Common Fixes

  • Reduce oversized headings that overpower nearby content.
  • Tighten or loosen spacing so sections read as grouped.
  • Standardize card padding, border radius, and image treatment.
  • Improve button hierarchy and hover/focus states.
  • Clarify section intros with cleaner type scale and shorter line lengths.
  • Fix mobile wrapping, overflow, and uneven grid behavior.
  • Improve loading, empty, and error states so they feel deliberate.

Red Flags

  • Do not add trendy effects that fight the product.
  • Do not turn a simple interface into a control-heavy dashboard.
  • Do not introduce multiple accent colors without a reason.
  • Do not use generic "AI app" styling if the product needs a distinct tone.
  • Do not sacrifice clarity for novelty.

Output Style

  • Make the UI feel cleaner, calmer, and more intentional.
  • Prefer a few strong improvements over many small random tweaks.
  • Explain the main polish decisions in plain language after editing.

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

Improve the visual quality, cohesion, and finish of an existing frontend without changing the product direction. Use when the user asks to polish, refine, tighten, elevate, clean up, or make a UI feel more premium, clearer, or more consistent across pages, components, spacing, typography, color, motion, states, and responsive behavior.

Why use Frontend Polish on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/matyasstoch/david-skills/tree/main/skills/frontend-polish. 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 Polish?

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 Polish?

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

Is the Frontend Polish AI skill free?

It is published on GitHub by matyasstoch. 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.

Related AI Skills

View all
NousResearch logo

Concept Diagrams

NousResearch
OrganizationPopular

Generate flat, minimal educational SVG visuals as HTML.

53.5K
250.4K
19 files
View
NousResearch logo

Hyperframes

NousResearch
OrganizationPopular

Render MP4/WebM videos from HTML compositions.

53.5K
250.4K
7 files
View
NousResearch logo

Ip As Logo

NousResearch
OrganizationPopular

Design minimal cute IP mascot marks readable at 32px.

53.5K
250.4K
Instructions
View
NousResearch logo

Mono Color

NousResearch
OrganizationPopular

Generate one- or two-ink editorial print poster images.

53.5K
250.4K
9 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇