nextjs-boilerplate

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Automates dependency upkeep for this repo: triages open Dependabot PRs and merges the safe ones, investigates and fixes red CI on dependency PRs, and prunes/reconciles the security lists in pnpm-workspace.yaml (overrides, minimumReleaseAgeExclude, trustPolicyExclude, allowBuilds). Use this whenever the user mentions Dependabot, dependency PRs, dependency updates, bumping or merging deps, "dependency maintenance", a red/failing dependency PR, or cleaning up / pruning pnpm-workspace.yaml — even if they don't name the skill.

Pull structural and infrastructure changes from the upstream nextjs_boilerplate into a project forked from it. Use this whenever the user wants to sync, update, pull, catch up on, or merge boilerplate/upstream/template infra changes into a fork — including CI, configs, tooling, dependencies, shared libs, and app scaffolding. Use it even if the user just says "update from the boilerplate" or "what changed upstream" without naming this skill.

Contribute a fork's infrastructure and structural improvements back UP to the upstream nextjs_boilerplate by opening a pull request. Use this whenever the user wants to upstream, contribute, push back, send, or PR fork changes to the boilerplate/template/upstream — e.g. "open a PR with my CI improvements to the boilerplate", "contribute my eslint changes upstream", "send my infra changes back to the template". This is the opposite direction of sync-from-boilerplate.

Audit feature code against convention rules, reporting violations with file:line references