Frontend Technical Spec

Frontend Technical Spec is a Frontend skill for Claude Code, published by shinpr in ai-coding-project-boilerplate.

227 stars25 forkson shinpr/ai-coding-project-boilerplateAdded 2026/09/03Repository updated 2026/09/01

agent-skillsagentic-aiagentic-workflowai-agentsanthropicboilerplateclaude-codecontext-engineeringdeveloper-toolsllm-orchestrationproductivityquality-gatestypescript

Install in seconds

Install Frontend Technical Spec

Copy Frontend Technical Spec into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/shinpr/ai-coding-project-boilerplate/tree/main/.claude/skills-en/frontend-technical-spec ~/.claude/skills/frontend-technical-spec

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/shinpr/ai-coding-project-boilerplate.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .claude/skills-en/frontend-technical-spec/SKILL.md in shinpr/ai-coding-project-boilerplate
Installs to: ~/.claude/skills/frontend-technical-spec
Collection: One of 25 skills cataloged from this repository
Category: Frontend — 621 skills

What Frontend Technical Spec does

Frontend Technical Spec defines React environment, component architecture, state and data flow, and build verification from repository evidence. Use it when configuring or designing a React frontend, its build, or its runtime boundaries.

Frontend Technical Spec is cataloged under Frontend on DirSkills. Frontend Technical Spec comes from a repository tagged agent-skills, agentic-ai, agentic-workflow, ai-agents and anthropic.

Documentation

README

Excerpt

Technical Design Rules (Frontend)

Prerequisite Detection

Inspect package.json, the lockfile, TypeScript/build configuration, CI definitions, and representative components before applying a tool- or framework-specific rule. Treat React, Vite, Next.js, a state library, form library, or script as available only when repository evidence names it. Label surrounding-pattern conclusions as inferred. When a missing decision changes rendering architecture, compatibility, security, or verification, stop and name the exact evidence or user decision required.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Frontend Technical Spec

What else does shinpr publish alongside Frontend Technical Spec?
Frontend Technical Spec is one of 25 skills that DirSkills catalogs from shinpr/ai-coding-project-boilerplate, the repository it ships in. Its siblings there include Coding Standards, Coding Standards and Create Skill. Each one is a separate skill with its own page in this directory, installs the same way Frontend Technical Spec does, and is maintained by shinpr in that same repository. The rest of the collection is listed on the shinpr/ai-coding-project-boilerplate page.
How does Frontend Technical Spec compare to other Frontend skills?
Frontend Technical Spec ranks #568 by stars among the 621 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Frontend Technical Spec against them. Open each page to compare what they document and how they install.