Miyamura80Miyamura80/MCP-Template/.agents/skills/frontend-design-principles/SKILL.md

frontend-design-principles

Skill1 starsChanged 5 months agoMITView on GitHub

Core visual principles for frontend work - subtract text, prefer SVG over prose, detail behind summary, one CTA. Use when building or editing UI, React components, pages, dashboards, docs or marketing sections, modals, or reviewing a frontend diff.

1 other project uses a version of this.

Adopted by

Most recently taken up by

joshuadavidthomas/agent-skillstheir own version, first seen May 9, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
joshuadavidthomas/agent-skills★ 49same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent.mdcCursor rule
- .cursor/rules/coding_style.mdcCursor rule
- .cursor/rules/commit_msg.mdcCursor rule
- .cursor/rules/common.mdcCursor rule
- .cursor/rules/deprecated.mdcCursor rule
- .cursor/rules/github_actions.mdcCursor rule
- .cursor/rules/langfuse.mdcCursor rule
- .cursor/rules/llm.mdcCursor rule
- .cursor/rules/long_run_code.mdcCursor rule
- .cursor/rules/makefile-commands.mdCursor rule
- .cursor/rules/package-management.mdCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typing.mdcCursor rule
- .cursor/rules/uv.mdcCursor rule
- goose-gui-e2eSkill
- local-sandboxSkill
- manage-agent-configSkill
- new-agent-ruleSkill
- onboardingSkill
- push-releaseSkill
- cleanupSkill
- code-qualitySkill
- prek-precommit-hookSkill
- thermo-nuclear-code-quality-reviewSkill
- usageSkill
- waitSkill
- gmail-mcpSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
2. A picture beats a thousand words: If an icon or diagram can say it, don't write the paragraph.
line 14

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

Frontend design principles

Apply to every UI change.

1. Subtract. "Perfection is when there is nothing left to subtract." Before adding anything, delete something: helper text, headings, borders, badges, duplicated labels.

2. A picture beats a thousand words. If an icon or diagram can say it, don't write the paragraph. Reuse below first, then https://svgl.app or https://eito.me/icons. Inline it.

3. Detail → summary. Show the summary only; reveal detail on hover, click, or expand. Never dump the full record upfront. Hover alone never counts: the same detail must open by keyboard and by touch, so lean on native details/summary or a real button before inventing a hover affordance.

4. Keep the main thing the main thing. Exactly one CTA per view, with the only high-contrast treatment on screen. Everything else stays dull, so contrast itself points the eye. Same CTA color, shape, and placement app-wide.

Reuse before creating

This repo has three separate frontends with no shared bundle between them, so "reuse" means reuse within a surface.

Landing page (Astro + Tailwind v4), landing-page/

Client and agent marks: public/logos/*.svg (claude, chatgpt, codex, goose, cursor, vscode, perplexity, github, mcp, cli, api, openclaw). Reference as /logos/<name>.svg with <img>, or as a CSS mask when the mark has to take the surrounding text color (see src/components/Nav.astro).
Chat-client chrome already exists in src/components/chat/: ClaudeShell, ChatGptShell, GooseShell, VsCodeShell. Reuse a shell instead of rebuilding a client mock. Buttons and code samples likewise have components: src/components/CtaButtons.astro, src/components/CodeBlock.astro.
Copy is mostly data. Page-level marketing strings live in src/config/landing/ and design tokens in the @theme block of src/styles/global.css; reach for config and tokens before markup. It is not the whole story though, so grep before assuming: component-local labels, accessibility text, and the mock dialogue in src/components/chat/ live in the component and belong there.
Favicon: public/favicon.svg.

Docs (Next.js + Fumadocs), docs/

Sidebar brand icons are inline SVG components in components/icons.tsx, registered in the iconMap in lib/source.ts, and selected per page with icon: <key> frontmatter. Add a component plus an iconMap entry. Never hot-link an external asset; the mark ships with the bundle.
Shared page chrome: components/ai/page-actions.tsx, lib/layout.shared.tsx.

MCP Apps (React in a sandboxed iframe), mcp_server/apps/<app>/

Each app is its own single-file Vite bundle, so styles are per-app by design: src/styles.ts in gmail_inbox, gmail_composer, and pdf_signer. Copy the style module into a new app rather than importing across apps.
dist/mcp-app.html is committed. Rebuild with make build_apps after any visual change, or the shipped bundle silently keeps the old UI.

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.

Check your setup, free