CtrlK
BlogDocsLog inGet started
Tessl Logo

laravel-inertia-react-structure

Frontend structure conventions for Laravel Inertia React applications based on Spatie's production practices. Use when creating, scaffolding, or reviewing frontend code in a Laravel Inertia React project. Triggers on creating React components, pages, modules, organizing frontend directories, setting up Inertia pages, structuring a React frontend within Laravel, or when the user asks about frontend file organization in an Inertia app.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An excellent, lean conventions reference with concrete executable examples and clear decision rules. The only gap is progressive disclosure: it is a single inlined file with no external references where advanced topics could be split out.

Suggestions

Consider extracting advanced topics (Multi-Zone Applications, shadcn/ui Usage) into separate reference files linked from the body, signaling them as one-level-deep references to improve progressive disclosure.

Optionally add a short 'Quick start' overview section at the top so the core conventions surface before the detailed directory trees.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding; it does not explain what React, Laravel, Inertia, or Tailwind are, and every section (directory trees, code blocks, terse rules) earns its place.

5 / 5

Actionability

Fully executable guidance: concrete directory trees, correct-vs-wrong code blocks for components/imports, a props interface example, and specific naming rules with examples covering the common cases.

5 / 5

Workflow Clarity

A single-purpose conventions skill with an unambiguous action and clear decision rules (e.g. 'Does it relate to a domain? -> modules'); no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and no bundle files, but all content is inlined in one file with no clearly-signaled external references, and some advanced topics (multi-zone, shadcn) could be split out.

4 / 5

Total

19

/

20

Passed

Description

83%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.

A strong, specific description that clearly answers both 'what' and 'when' with a concrete 'Use when...' trigger clause. The main room for improvement is adding synonyms/file extensions to broaden natural trigger coverage.

Suggestions

Add natural synonyms and file extensions (e.g., 'Inertia.js', '.tsx', '.jsx', React component files) to broaden trigger-term coverage.

Enumerate a few more concrete actions (e.g., 'reviewing Inertia page structure', 'auditing directory organization') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names several concrete actions (creating, scaffolding, reviewing frontend code; creating components, pages, modules; organizing directories; setting up Inertia pages), with only minor gaps versus a fully enumerated list.

4 / 5

Completeness

Explicitly states what it does (frontend structure conventions for Laravel Inertia React based on Spatie's practices) and provides an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('React components, pages, modules', 'organizing frontend directories', 'frontend file organization in an Inertia app'), though it lacks synonyms and file extensions needed for a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Laravel Inertia React structure conventions) with distinct triggers and minimal conflict risk, though it can overlap slightly with general React/frontend structure skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
freekmurze/dotfiles
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.