Fetches nextjs-dynamic-routes-params from wsimmonds/claude-nextjs-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/nextjs-dynamic-routes-params
Restart Cursor to activate nextjs-dynamic-routes-params. Access via /nextjs-dynamic-routes-params in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Accessing URL pathname parameters in Server or Client Components
Building pages that fetch data based on route parameters
Implementing catch-all or optional catch-all routes
Working with the params prop in page.tsx, layout.tsx, or route.ts
⚠️ RECOGNIZING WHEN YOU NEED DYNAMIC ROUTES
Look for requirements that tie data to the URL path.
Create a dynamic segment ([param]) whenever the UI depends on part of the pathname. Typical signals include:
Details pages that reference “the item’s ID/slug from the URL”
Copy that calls out path segments (e.g., /products/{id}, /blog/{slug})
Requirements to fetch data “based on whichever resource is being visited”
Navigation flows where one page links to /something/{identifier}
✅ Dynamic route response
Requirement: display product information based on whichever ID appears in the URL
Implementation: app/[id]/page.tsx
Access parameter with: const { id } = await params;
Key Principle: The folder structure IS the route structure.
Route Structure Decision Tree
CRITICAL RULE: Do NOT infer route structure from resource type names!
Just because you're fetching a "product" or "user" doesn't mean you need /products/[id] or /users/[id]. Unless explicitly told otherwise, prefer the simplest structure.
When deciding on route structure:
Top-level dynamic route (app/[id]/page.tsx)
DEFAULT CHOICE - Use this unless specifically told otherwise
Use when the resource IS the primary entity
Use when only ID-based routing is needed
Examples: /123 for any resource, /abc-def for slugs
Pattern: The ID/slug is the only identifier needed
When in doubt, choose this!
Nested dynamic route (app/category/[id]/page.tsx)
ONLY use when explicitly required by the URL structure
Use when you're told "create a /products/[id] route"
// ❌ WRONG - Treating params as synchronous object (Next.js 15+)exportdefaultasyncfunctionProductPage({ params,}:{ params:{ id:string};// Missing Promise wrapper}){const product =awaitfetch(`https://api.example.com/products/${params.id}`);// This will fail because params is a Promise!}
You CANNOT access params directly in Client Components. Instead:
Use useParams() hook:
'use client';import{ useParams }from'next/navigation';exportfunctionProductClient(){const params =useParams<{ id:string}>();const id = params.id;// Use the id...}
Pass params from Server Component:
// app/products/[id]/page.tsx (Server Component)exportdefaultasyncfunctionProductPage({ params,}:{ params:Promise<{ id:string}>;}){const{ id }=await params;return<ProductClient productId={id}/>;}// components/ProductClient.tsx'use client';exportfunctionProductClient({ productId }:{ productId:string}){// Use productId...}
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
