client-side-routing

How to add routes without remounting the app shell. Use when adding a new route, fixing agent sidebar reloads on navigation, or choosing between `root.tsx` layout and pathless `_app.tsx` layout patterns.

Quality

92%

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

100%

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

A tight, well-structured skill that leads with rules and concrete code patterns, includes a labeled anti-pattern, and gives crisp per-pattern guidance for adding routes. It respects Claude's competence and requires no external references.

Dimension	Reasoning	Score
Conciseness	Lean and domain-focused — the Rule, Hard Rule, and code blocks carry the load with no generic padding about what React Router or SPAs are; the brief "Why" and mechanistic note ("React sees a different component at the outlet position... and unmounts the entire subtree") earn their place as non-obvious domain knowledge. Not a 2 because there is no unnecessary explanation of concepts Claude already knows.	3 / 3
Actionability	Gives concrete, executable guidance: the `app/root.tsx` AppLayout-around-Outlet snippet, an explicit file-tree naming convention for pathless routes (`_app.tsx`, `_app.<segment>.tsx`, bare `<segment>.tsx`), and a labeled anti-pattern — copy-paste ready and specific. Not a 2 because the examples are real code and concrete file names rather than pseudocode.	3 / 3
Workflow Clarity	The "Adding a New Route" section gives unambiguous decision guidance mapped to each pattern (Pattern #1 → render page content only; Pattern #2 → `_app.<segment>.tsx` vs bare `<segment>.tsx`), and the task is a single decision rather than a multi-step destructive operation, so validation checkpoints are not applicable. Not a 2 because the single action is clearly sequenced by pattern with no ambiguity.	3 / 3
Progressive Disclosure	Self-contained with well-organized sections (Rule, Why, Hard Rule, Two Correct Patterns, Anti-Pattern, Chat-First Routes, Adding a New Route, Related Skills) and no need for external bundle files; cross-skill navigation is signaled via Related Skills. No bundle files exist in references/scripts/assets, and the body has no nested or dangling references.	3 / 3
	Total	12 / 12 Passed

Description

85%

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 with explicit what-and-when triggers and a clear niche. Its only weakness is the third trigger clause leaning on technical jargon (pathless `_app.tsx` layout patterns) that users are unlikely to voice naturally.

Suggestions

Reword the third trigger in plainer user-sayable terms, e.g. "Use when adding a new route, fixing the sidebar reloading on navigation, or deciding where to put the app layout."

Add a common-variation keyword or two that users actually say (e.g. "layout flicker on navigation", "app shell unmounts") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "add routes without remounting the app shell", "adding a new route", "fixing agent sidebar reloads on navigation", "choosing between `root.tsx` layout and pathless `_app.tsx` layout patterns" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("How to add routes without remounting the app shell") and when ("Use when adding a new route, fixing agent sidebar reloads on navigation, or choosing between...") with an explicit Use-when clause, matching the top anchor.	3 / 3
Trigger Term Quality	Includes natural triggers like "adding a new route" and "sidebar reloads on navigation", but "choosing between `root.tsx` layout and pathless `_app.tsx` layout patterns" is technical jargon a user would rarely say verbatim, so common-variation coverage is incomplete. Not a 3 because the jargon-heavy third trigger lacks natural phrasing; not a 1 because several terms are genuinely user-sayable.	2 / 3
Distinctiveness Conflict Risk	Highly specific to client-side routing and app-shell remount behavior, with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/client-side-routing/SKILL.md
Commit: c1ee18b

Reviewed: 5 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.