react-feature-sliced-design

Enforces Feature-Sliced Design (FSD) architecture in React/TypeScript projects by scaffolding compliant folder structures, validating layer boundaries and import directions, detecting and fixing layer violations, and teaching FSD conventions during code generation and review. Use when asked to 'create a page', 'add an entity', 'build a widget', 'scaffold FSD structure', 'refactor to FSD', 'where should I put this code', 'what layer does X go in', 'organize my React code', 'fix layer violation', or 'review my FSD structure'. Triggers on any React/TypeScript task involving FSD layers, slices, segments, cross-layer imports, or public API boundaries.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable FSD guide with a clear validated workflow and excellent progressive disclosure through verified one-level references. It loses a little on conciseness (a promotional 'Why FSD' section) and on actionability/workflow clarity (one inline example, no inline retry loop).

Suggestions

Trim or repurpose the 'Why FSD' rationale section — assume Claude's competence and keep only the FSD-specific mechanics (Grey Box/public API) that it would not already know.

Add brief inline copy-paste examples for a feature and a widget slice alongside the entity example, so common cases don't require opening a reference file.

Turn the slice-creation workflow's verify checklist into an explicit validate→fix→retry loop (e.g., 'if any check fails, fix the import and re-run step 6') to close the validation gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense tables and a code example, but the 'Why FSD' section is rationale/marketing that assumes Claude needs convincing and could be trimmed; not 5 because of that minor over-explanation, not 3 because the bulk is tight and well-compressed.	4 / 5
Actionability	Concrete folder/naming rules and one copy-paste-ready TypeScript entity-slice example give mostly executable guidance; minor gaps remain because feature/widget/page examples are deferred to references rather than shown inline, keeping it just below the fully-comprehensive anchor.	4 / 5
Workflow Clarity	The 'Adding a New Slice' workflow has a clear 6-step sequence with validation (step 4) and a verify checklist (step 6), but the error-recovery path lives in a separate violations table rather than an inline validate→fix→retry loop, a minor validation gap below the top anchor.	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with a 'Deep Dives' Need→Read table pointing to four verified one-level-deep reference files (layers.md, segments.md, claude-md-template.md, slice-examples.md); content is appropriately split and easy to navigate, matching the top anchor.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 is exemplary: it states concrete capabilities, gives a thorough set of natural trigger phrases, and explicitly covers both what the skill does and when to use it within a clearly distinct FSD niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'scaffolding compliant folder structures, validating layer boundaries and import directions, detecting and fixing layer violations, and teaching FSD conventions' — giving comprehensive coverage rather than just several with minor gaps.	5 / 5
Completeness	Explicitly answers both 'what' (enforces/scaffolds/validates/fixes/teaches FSD) and 'when' ('Use when asked to...', 'Triggers on...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ('create a page', 'add an entity', 'build a widget', 'where should I put this code', 'organize my React code', 'fix layer violation') plus synonyms and FSD-specific terms; matches the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Clear FSD-in-React/TypeScript niche with distinct, domain-specific triggers and minimal overlap risk with generic skills; fits the 'clear niche, minimal conflict' anchor.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: provectus/awos-recruitment
Path: registry/skills/react-feature-sliced-design/SKILL.md
Commit: 298fce7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.