agentleFS
Fadi88Fadi88/one-man-startup/.cursor/rules/skill-frontend-design.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

Distinctive, intentional visual design for any UI being built or reshaped - aesthetic direction, typography, layout, motion and interface copy that does not read as a templated default. Use on every ticket that changes what users see.

We split this skill-frontend-design.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and follow skills/frontend-design/UPSTREAM.md: Anthropic's frontend-design skill, copied unchanged from …

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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-frontend-design.mdc
---
description: "Distinctive, intentional visual design for any UI being built or reshaped - aesthetic direction, typography, layout, motion and interface copy that does not read as a templated default. Use on every ticket that changes what users see."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from skills/frontend-design/SKILL.md. Edit the source, not this file. -->

# Frontend design

Read and follow `skills/frontend-design/UPSTREAM.md`: Anthropic's frontend-design skill, copied
unchanged from https://github.com/anthropics/claude-plugins-official
(`plugins/frontend-design/skills/frontend-design/SKILL.md`) on 2026-10-14, under the Apache
License 2.0 in `skills/frontend-design/LICENSE.txt`. `tools/checks/upstream_check.py` fails if
the copy is edited.

## How it fits this template

- **The brief is the spec.** The design brief the upstream skill asks for is
  `docs/work/<id>/spec.md` and `ux.md`, plus `project.toml [product]` (audience, regions). The
  product designer writes `ux.md` itself, from the spec; where the founder has set a direction,
  follow it ("the brief's own words always win").
- **Plan before code, in the work folder.** The design plan the upstream skill asks for (palette,
  type, layout, principles) goes in `docs/work/<id>/ux.md` or beside it, so `qa` and later
  tickets can see it.
- **The quality floor is a requirement**, not a nicety: responsive to phone width, visible
  keyboard focus, reduced motion respected, contrast to the bar in `agents/product-designer.md`.
- **Copy follows the project's style rules** (`project.toml [style]`), including the banned
  characters, which the upstream text itself uses in places.
- **Fonts and images** are checked for licence before use, and their cost if any is sourced
  (`skills/verified-claims/`).

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.

Reviews can't be read right now.

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.