agentsclimarketplace

Nextjs app

Skill aneebbaig/app-starter-skills/plugins/app-starter/skills/nextjs-app

Bootstrap skills for Next.js, Flutter, and FastAPI apps. Current packages, no deprecated APIs, consistent structure. Claude Code plugin + AGENTS.md.

Install
npx -y skills add aneebbaig/app-starter-skills --skill nextjs-app

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Bootstrap a new Next.js (App Router, TypeScript) web app, or audit and retrofit an existing one, with current packages and no deprecated APIs. Use when the user wants to start, scaffold, or set up a new Next.js project, a React web app, a SaaS or dashboard or landing page on Next.js, or asks to "create a new nextjs app". ALSO use on an existing Next.js or React codebase when the user asks to audit, review, fix, clean up, refactor, modernize, upgrade, harden, or "bring up to standard" the app, remove deprecated APIs, improve the structure, or apply house rules. Handles private, open-source, and private-plus-open-source variants, Prisma and Postgres, better-auth, Tailwind, and shadcn or Mantine.

SKILL.md

4.7 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

nextjs-app

Build or fix a Next.js web app the way this owner builds them: App Router, TypeScript strict, current stable packages, no deprecated APIs, a clean feature structure, and the house git and CI workflow.

First read these shared rules (they override anything you remember): ../shared/house-rules.md, ../shared/intake.md, ../shared/no-ai-attribution.md, ../shared/git-and-ci.md, ../shared/docs-and-context.md, ../shared/hardening.md, and (for public repos) ../shared/open-source-docs.md.

Step 0. Detect the mode, run the intake (hard stop)

Follow ../shared/intake.md exactly: detect new-app vs existing-app mode from the directory and the user's words, then ask the matching intake batch. Do not run any scaffolding or editing command until it is answered.

Existing-app mode: skip to ../shared/existing-app.md and follow it, using this skill's references/ as the standard to audit against. Steps 1-5 below are for new-app mode only.

New-app mode: the intake covers brief, app type, visibility, scale, and deploy target. The only stack variants left to settle, each with a default the app type usually decides (ask ONLY the ones the answers leave ambiguous, in the same batch):

  1. Data layer: Prisma + Postgres (default), a different DB, or none yet.
  2. Auth: better-auth (default); Clerk or none only if the user says so.
  3. UI kit: shadcn/ui + Tailwind (default), Mantine, or plain Tailwind.
  4. Package manager: pnpm (default) or npm.
  5. Visibility variants (private / open-source / both): references/variants.md.

If the user already answered something in their prompt, do not re-ask.

Step 1. Verify environment and current versions

  • Check Node (node -v, want the current LTS or newer) and the package manager.
  • Run scripts/check-latest.sh to get live stable versions from npm. Pin those, not versions from memory. See ../shared/house-rules.md rule 2.
  • Pull current Next.js docs before writing framework code (../shared/docs-and-context.md). Recent Next.js ships docs in node_modules/next/dist/docs/; read the relevant guide and obey deprecation notices.

Step 2. Scaffold with the official CLI

Use the official generator so you inherit its current defaults:

pnpm create next-app@latest <name> --typescript --app --eslint --tailwind --src-dir --import-alias "@/*"

Adjust flags to the answers. Let the CLI pick the current Next major; do not force a version you remember. After it runs, read references/stack.md for the exact dependency set to add and references/structure.md for the folder layout.

Step 3. Apply house structure and conventions

  • Folder layout, data layer, auth, and server-action patterns: references/structure.md.
  • Dependency set and why each is chosen: references/stack.md.
  • Variant-specific setup (LICENSE, README tone, monorepo split, secret handling): references/variants.md.
  • Production hardening so the shipped app does not leak secrets or internals: ../shared/hardening.md.
  • The no-god-code rule and layer separation: ../shared/house-rules.md rule 8.

Step 4. Git, CI, docs, security

  • Initialize git, set the branch model, and wire CI and auto-merge per ../shared/git-and-ci.md.
  • Write the CI workflow and quality gates from references/quality-gates.md.
  • Add docs/ and README per ../shared/docs-and-context.md.
  • For a public repo, ship the full open-source docs set (LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue and PR templates, CHANGELOG via release-please) per ../shared/open-source-docs.md, and run the open-source hard gate in ../shared/no-ai-attribution.md before the first push.
  • Gitignore .env*, add .env.example. Never commit secrets.

Step 5. Verify before declaring done

Run the quality gates in references/quality-gates.md (typecheck, lint, production build, and a dev-server smoke check), then run the done gate in ../shared/house-rules.md rule 10 and echo each answer. Report real results. If a build fails, fix it or say so with the output. Do not claim done on an unbuilt app.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.