react-project-starter
Scaffold a React 19 + Vite project with TypeScript strict mode, Tailwind CSS v4, React Router v7, and ESLint flat config using a feature-based folder structure.
72
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/react-project-starter/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at technical specificity with precise version numbers and configuration details, making it highly distinctive. However, it critically lacks any 'Use when...' guidance, which is essential for Claude to know when to select this skill. The trigger terms are technical but miss common user phrasings for project creation.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'create new React project', 'start a new app', 'bootstrap React application', or 'initialize frontend project'
Include natural user language variations such as 'set up', 'new project', 'starter template', or 'boilerplate' alongside the technical terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete technologies and configurations: React 19, Vite, TypeScript strict mode, Tailwind CSS v4, React Router v7, ESLint flat config, and feature-based folder structure. | 3 / 3 |
Completeness | Describes WHAT it does (scaffold a specific tech stack) but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes good technical keywords (React, Vite, TypeScript, Tailwind, ESLint) but missing natural user phrases like 'create new project', 'start a new app', 'bootstrap', or 'initialize'. Users might say 'set up a React app' rather than 'scaffold'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific tech stack with exact version numbers (React 19, Tailwind v4, Router v7) creates a clear niche that is unlikely to conflict with other project scaffolding skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with excellent executable code examples and clear workflow for scaffolding a React project. The main weakness is that it's quite long for a SKILL.md file - the extensive pattern examples (full component, hook, context implementations) could be split into separate reference files. The path alias configuration appearing in multiple places adds minor redundancy.
Suggestions
Split detailed code patterns (Component Structure, Custom Hook, Context Provider, Router) into a separate PATTERNS.md file, keeping only the scaffold command and project structure in SKILL.md
Remove duplicate path alias configuration - it appears in both 'Path Alias Config' and 'TypeScript Config' sections
Consider moving 'Integration Notes' to a separate INTEGRATIONS.md file since these are optional additions rather than core scaffold content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (path alias config appears twice in slightly different forms) and could be tightened. The extensive code examples are valuable but some patterns (like the full LoginForm component) may be more detailed than necessary for a scaffold skill. | 2 / 3 |
Actionability | Excellent actionability with fully executable code throughout - complete scaffold commands, copy-paste ready config files, working component examples, and specific npm commands. Every section provides concrete, runnable code rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | Clear sequential workflow from scaffold command through project structure to first steps. The 'First Steps After Scaffold' section provides explicit numbered steps with verification (checking localhost:5173, running tsc --noEmit). Common commands section provides clear reference for ongoing development. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file that could benefit from splitting. The extensive code patterns (component structure, hooks, context, router) could be in separate reference files, with SKILL.md providing just the scaffold command and project structure overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.