vardhan23v

Front End Skill Claude Code — Git skill for Claude Code

Git community

create-frontend — a Claude Code skill that turns 'build me a frontend' into a production-oriented workflow: classify, decide the stack, draw the backend boundary, build, verify in seven categories, pr.

How to install Front End Skill Claude Code

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vardhan23v/front-end-skill-claude-code and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Front End Skill Claude Code does

create-frontend — a Claude Code skill that turns 'build me a frontend' into a production-oriented workflow: classify, decide the stack, draw the backend boundary, build, verify in seven categories, prepare deploy.

Alternatives in Git

  • Copilot API — Turns GitHub Copilot into an OpenAI/Anthropic API compatible server, usable with Claude Code 3.1k ★
  • Codebase To Course — by Zara Zhang - A Claude Code skill that turns any codebase into a beautiful, interactive single-page HTML cou 2.1k ★
  • Contributing To Ctf-skills — Thanks for helping expand the CTF skills collection 820 ★

README

front-end-skill-claude-code

A Claude Code skill (`create-frontend`) that turns "build me a frontend" into a production-oriented workflow: classify the project, respect or choose the stack, draw the frontend/backend boundary, build with real states and accessibility, verify in seven explicit categories, and finish with an honest verification report.

**Version:** 3.0.0 · **Status:** specification complete, not yet validated on real projects (see [Validation Status](#validation-status))


Contents


What it does

Stage Outcome
Classify Decides whether the project is new, existing, partially implemented, or needs refactoring, and sizes the task so a one-component change does not get the new-project treatment
Read Inspects package.json, lockfile, config, routing, styling, components, data layer, tests and environment; runs the existing checks once and records what already fails
Decide Chooses the stack by a fixed priority (user → existing architecture → conventions → team constraints → requirements → defaults)
Boundary Detects features that need a backend, writes the API contract, and refuses to fake them
Build Design tokens first, then screens with loading/empty/error/success states, responsive layout, acces