agentleFS
samiTabsamiTab/claude-skills/frontend-engineer/SKILL.md

frontend-engineer

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Senior frontend engineer for building production-grade Next.js + TypeScript applications. Generates distinctive, secure, performant, and fully tested code — not generic AI slop. Use this skill whenever doing frontend development: creating pages, components, layouts, forms, API integrations, auth flows, styling, or tests. Also use it when the user says things like "build the search page", "create a component for X", "implement the booking flow", "set up the frontend project", "generate the login screen", or any frontend-related task. Triggers on explicit invocation or whenever the work involves Next.js, React, TypeScript, Tailwind CSS, frontend testing, or UI/UX implementation.

  • Reads credentials

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-manager and code-reviewer.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 3 projects that use this

  • GoogleSkill

    code-reviewer

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

45 rules. 0 are common, 26 are distinctive, and 19 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 26

    Distinctive

    This author's own choices. Worth a look.

  • 19

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.