agentleFS
Sign inStart free
ankitluthraankitluthra/frontend-quality-graph/skills/frontend-implement/SKILL.md

frontend-implement

Skill0 starsChanged 3 months agoMITView on GitHub

Implements frontend/UI against an agreed plan and thin high-signal taste skills — production look, not vibe-coded sameness. Invoked automatically by frontend-graph as the worker step.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. aniketshukla1/sdlc-kit★ 1same 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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the plan’s done criteria.

    line 13
  2. Distinctive:

    If a design system exists, preserve it — don’t invent a parallel look.

    line 15
  3. Very specific:

    Taste stack (thin): follow frontend-design. If ui-ux-pro-max produced a brief, use it.

    line 16
  4. Very specific:

    React/Next: follow vercel-react-best-practices when the repo uses that stack.

    line 17
  5. Distinctive:

    Prefer CSS variables / existing tokens.

    line 19
  6. Distinctive:

    Anti-sameness while coding: no Inter-default hero type, purple/indigo glow themes, cream+terracotta cliché, emoji icons, decorative card …

    line 20
  7. Distinctive:

    No drive-by refactors outside touched UI.

    line 21
  8. Distinctive:

    After edits: note what to verify (route, breakpoints, keyboard).

    line 22
  9. Very specific:

    Follow the repo’s React guidance (Compiler, no unnecessary memo).

    line 33

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

Rules

  1. Follow the plan’s done criteria; don’t expand scope.
  2. Match the repo’s stack, components, tokens, and file layout.
  3. If a design system exists, preserve it — don’t invent a parallel look.
  4. Taste stack (thin): follow frontend-design. If ui-ux-pro-max produced a brief, use it. If impeccable is installed, honor its anti-patterns while building.
  5. React/Next: follow vercel-react-best-practices when the repo uses that stack.
  6. Ship loading/empty/error where the plan requires them.
  7. Prefer CSS variables / existing tokens; expressive fonts when not constrained by the system.
  8. Anti-sameness while coding: no Inter-default hero type, purple/indigo glow themes, cream+terracotta cliché, emoji icons, decorative card grids, or “generic SaaS template” section stacks unless the existing system requires them.
  9. No drive-by refactors outside touched UI.
  10. After edits: note what to verify (route, breakpoints, keyboard).
  11. Before claiming done on visually led work: run Sameness Shield and fix until exit 0:
python3 ~/.agents/frontend-quality-graph/bin/sameness-check <changed-ui-files>

Fallbacks: ~/.agents/frontend-quality-graph/repo/scripts/sameness-check.py or scripts/sameness-check.py. Do not skip. Do not set SAMENESS_ALLOW=1 unless the user asks.

React note

Follow the repo’s React guidance (Compiler, no unnecessary memo). Don’t add useMemo/useCallback by default.

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