next-js-guidance
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: next-js-guidance
description: Baseline guidance for App Router apps. Use when this capability is needed. Use this for broad Ap…
category: other
runtime: no special runtime
---
# next-js-guidance output preview
## PART A: Task fit
- Use case: Baseline guidance for App Router apps. Use when this capability is needed. Use this for broad App Router orientation. Use app-local Next skills for version-specific guidance. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Use When / Do / Do Not” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Baseline guidance for App Router apps. Use when this capability is needed. Use this for broad App Router orientation. Use app-local Next skills for version-specific guidance. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Use When / Do / Do Not” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Use When / Do / Do Not”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: next-js-guidance
description: Baseline guidance for App Router apps. Use when this capability is needed. Use this for broad Ap…
category: other
source: tomevault-io/skills-registry
---
# next-js-guidance
## When to use
- Baseline guidance for App Router apps. Use when this capability is needed. Use this for broad App Router orientation.…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Use When / Do / Do Not” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "next-js-guidance" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Use When / Do / Do Not
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Use When
Use this for broad App Router orientation.
Do
- Put route pages under
src/app. - Keep page components server-rendered unless interactivity requires client components.
- Read the app package before assuming framework behavior.
Do Not
- Mix conventions between sibling apps just because both use Next.js.
- Add client components for static merchandising or dashboard content.
Example
apps/admin/src/app/settings/page.tsx and apps/storefront/src/app/promotions/page.tsx are both App Router pages, but they target different Next majors.
See Also
Use app-local Next skills for version-specific guidance.
Source: atheory-ai/skillex-demo — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review