This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.
The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory
Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
Reviewed on 2026-04-17 against Next.js workflow fit, installation clarity, operator handoff, and full-stack delivery usefulness. This page is now positioned as an install-first Next.js entry point instead of a broad framework roundup.
We prioritize this page because Next.js-intent users usually need a shortlist they can install, validate, and carry into real full-stack release loops quickly.
Trust Signals
- Entries are chosen for practical Next.js workflow value such as shipping routes, content updates, review loops, and release guardrails.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable product delivery, not for vague framework keyword coverage or generic repository popularity.
Grouping Logic
- Lead with tools that can enter a Next.js-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering shipping, review, content, and release support.
- Use installation as the bridge from Next.js discovery into validated daily execution.
Maintenance & Review
Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or Next.js workflow relevance changes upstream; otherwise review monthly.
Maintained By
Killer-Skills editorial review within the recovery-focused authority queue.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples
How These Skills Work Together In Practice
Install one Next.js workflow tool first
Use this page when you want one Next.js companion that can enter a real product loop without turning evaluation into another endless framework-tool comparison.
1. Open the installation docs before opening more Next.js-related repositories.
2. Choose one tool that best supports shipping, review, release, or content operations.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider full-stack workflow.
Stabilize a Next.js release loop
Treat the collection as an editorial filter when you need Next.js-adjacent tools that improve release quality without overcomplicating the stack.
1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more routes, services, or teammates.
4. Document the chosen Next.js workflow baseline after the first clean rollout.
The component-refactoring skill simplifies high-complexity React components, improving code quality and reducing maintenance efforts for developers. It utilizes patterns and workflows to refactor components, making them more efficient and easier to understand.
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Guide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
This skill should be used when the user asks to update documentation for my changes, check docs for this PR, what docs need updating, sync docs with code, scaffold docs for this feature, document this feature, review docs completeness, add docs for this change, what documentation is affected, docs impact, or mentions docs/, docs/01-app, docs/02-pages, MDX, documentation update, API reference, .mdx files. Provides guided workflow for updating Next.js documentation based on code changes.
Write detailed user stories from implementation plans and post to GitHub. Use after planning with zoonk-issue-planning. Acts as a product owner, providing context and acceptance criteria while leaving room for implementation decisions.
Optimize content and websites for AI search engines (ChatGPT, Perplexity, Google AI Overviews) using GEO principles, content chunking, structured data, and brand visibility strategies. Use when working on SEO, AI visibility, content optimization, GEO, getting brand mentioned in AI, or implementing technical SEO for LLM search.
If This Page Is Close, Keep Narrowing With Adjacent Authority Pages
Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.
Use These Additional Paths If You Need One More Step To Narrow The Decision
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
