nextjs-app-router-patterns
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill nextjs-app-router-patterns85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Next.js 14+ App Router), lists specific capabilities (streaming, parallel routes, Server Components), and provides explicit trigger conditions. The description uses proper third-person voice and includes version-specific terminology that helps distinguish it from general React or older Next.js patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Server Components, streaming, parallel routes, and advanced data fetching' along with 'implementing SSR/SSG, or optimizing React Server Components'. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Server Components, streaming, parallel routes, and advanced data fetching') and when ('Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Next.js', 'App Router', 'Server Components', 'SSR/SSG', 'React Server Components', 'streaming', 'parallel routes'. Good coverage of terms developers actually use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Next.js 14+ App Router paradigm with distinct triggers like 'parallel routes', 'React Server Components', and version-specific features. Unlikely to conflict with general React or older Next.js skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples covering the full range of Next.js App Router patterns. The main weaknesses are verbosity (could be 30-40% shorter by removing explanations Claude already knows) and lack of validation workflows for complex operations. The monolithic structure works but could benefit from progressive disclosure to separate files.
Suggestions
Remove explanatory text like 'Server Components - Server only - Data fetching, heavy computation, secrets' since Claude knows these concepts; keep only the pattern examples
Add validation checkpoints to Server Actions pattern (e.g., 'Verify revalidation worked by checking the updated data')
Split advanced patterns (Parallel Routes, Intercepting Routes) into separate reference files and link from main skill
Remove the 'When to Use This Skill' section - this belongs in frontmatter description, not body content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude would know (e.g., explaining what Server Components are for, basic file conventions). The tables and lists are efficient, but the overall length could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all patterns include complete, copy-paste ready TypeScript code with proper imports, types, and realistic implementations. The caching strategies section provides concrete fetch options. | 3 / 3 |
Workflow Clarity | While patterns are well-organized, there's no explicit validation workflow or error recovery steps. For complex operations like Server Actions with database mutations, there's no guidance on verifying success or handling rollbacks. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's monolithic - all patterns are inline rather than split into separate reference files. The external links at the end are helpful but the main content could benefit from splitting advanced patterns into separate files. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (544 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.