Frontend Technical Spec
React technical-design rules: env/secrets, component architecture, data flow, build gates
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 31, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 6cc3f05
Fetched SKILL.md (HTTP 200); frontmatter has name+description, single self-contained file, no referenced scripts/files, no security smells. Trigger phrasings: SHOULD — "design the component architecture and state management for our React dashboard", "set up env var config and build verification for our Vite React app", "how should data flow between our API and React components"; should NOT — "design a Postgres schema for our orders backend", "improve the visual design and color palette of our landing page". All 5 judged correctly. For output I wrote a UserProfile design note baseline vs skill-following (both in scratchpad): following the skill fixed a real API-key-in-URL exposure (proxy instead), corrected process.env to import.meta.env.VITE_ (baseline would be undefined in a Vite client bundle), and added unknown+type-guard parsing. Corrected category from design to coding: this is technical architecture, not visual design.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 5/5
What Frontend Technical Spec does
A design-time rules skill for TypeScript React frontends: it drives environment-variable and secret handling (client-exposure via bundler prefix, secrets kept server-side), component/state architecture selection, unknown-to-typed data flow, and phased build/quality gates from repository evidence. Triggers when configuring or designing a React frontend, its build, or its runtime boundaries. It is architecture/technical-spec guidance, not visual UI design.
How to install Frontend Technical Spec
git clone --depth 1 https://github.com/shinpr/ai-coding-project-boilerplate.git /tmp/frontend-technical-spec-src
mkdir -p ~/.claude/skills
cp -R /tmp/frontend-technical-spec-src/.claude/skills-en/frontend-technical-spec ~/.claude/skills/frontend-technical-spec
# Single self-contained SKILL.md, no reference files, no scripts, no external deps.
# A Japanese-language twin exists at .claude/skills-ja/frontend-technical-spec/ if preferred.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Frontend Technical Spec
-
/frontend-technical-specReact technical-design rules: env/secrets, component architecture, data flow, build gates
It also activates on plain-language prompts like these:
-
Set up environment variables for this React app -
Design the data flow for this component -
Write a technical spec for the frontend architecture
Frequently asked questions
- Is the Frontend Technical Spec skill free?
- Yes. The skill itself is free from shinpr/ai-coding-project-boilerplate. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Frontend Technical Spec work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 31, 2026. Verdict: Tested · Works. Fetched SKILL.md (HTTP 200); frontmatter has name+description, single self-contained file, no referenced scripts/files, no security smells. Trigger phrasings: SHOULD — "design the component architecture and state management for our React dashboard", "set up env var config and build verification for our Vite React app", "how should data flow between our API and React components"; should NOT — "design a Postgres schema for our orders backend", "improve the visual design and color palette of our landing page". All 5 judged correctly. For output I wrote a UserProfile design note baseline vs skill-following (both in scratchpad): following the skill fixed a real API-key-in-URL exposure (proxy instead), corrected process.env to import.meta.env.VITE_ (baseline would be undefined in a Vite client bundle), and added unknown+type-guard parsing. Corrected category from design to coding: this is technical architecture, not visual design.
- What is the Frontend Technical Spec SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install Frontend Technical Spec?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Frontend Technical Spec with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.