.claude/skills/fec-nextjs-project-standardRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use when creating or reviewing Next.js 14+ App Router projects, file routes, layouts, server/client component boundaries, SSR/SSG/ISR, streaming, metadata, middleware, server actions, or Next-specific data fetching. For generic client React component architecture, apply the project's React conventio
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/fec-nextjs-project-standardRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/fec-nextjs-project-standardRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/fec-nextjs-project-standardRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @bovinphang/fec-nextjs-project-standardclawhub inspect @bovinphang/fec-nextjs-project-standard --version 2.9.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:f7acfdd95b4c84d9d5ff684908efa6ce66ab5daf252ffbea667b0a821bb12c6eLICENSEmetadata.jsonpackage.jsonREADME.mdskill-card.mdSKILL.md- English translation of skill documentation for broader accessibility. - Added requirements for evidence-driven review, including collecting build, trace, headers, or routing evidence before asserting route behavior or rendering mode. - Clarified cache policies and mandates explanation and verification when dynamic reads change route behavior. - Added constraints against making unsubstantiated claims about caching or dynamism without supporting evidence. - Expanded middleware rules: restrict to lightweight logic, explicitly prohibit heavy business logic. - Added a new review process step focused on evaluating caching, data acquisition, RSC serialization, and bundle boundaries.