Buzzform
buildnbuzz/buzzform
A skill your agent uses when working with BuzzForm schema-driven forms, @buildnbuzz/form-core, @buildnbuzz/form-react, or any related APIs like defineSchema, InferType, FormProvider, useDataField…
Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route…
Install Opinionated Nextjs Patterns
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .claude/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .claude/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .agents/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .agents/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .cursor/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .cursor/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/opinionated-nextjs-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .gemini/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .gemini/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .github/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .github/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills opinionated-nextjs-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/opinionated-nextjs-patterns .opencode/skills/opinionated-nextjs-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "opinionated-nextjs-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/opinionated-nextjs-patterns into .opencode/skills/opinionated-nextjs-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opinionated-nextjs-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
opinionated-nextjs-patterns- GitHub stars
- 214
- Token cost
- ~3k tokens
- SKILL.md length
- 921 words
- Files
- 55 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route…
- Works in 8 steps: Authorization & Data-Layer Access… → Multi-Tenancy (CRITICAL — optional, SaaS… → Request Boundary: Proxy (HIGH) → …
- Refactoring Next.js 16 code
- SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Opinionated Nextjs Patterns is an agent skill from pproenca/dot-skills. Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route handlers, client/server boundaries ('use client' at leaves + TanStack Query), forms with RHF + Zod, UI via shadcn/ui + Tailwind + Base UI + next-intl, request handling in proxy.ts (Next.js 16's renamed middleware), and a Turbo monorepo of @app/ packages confining the backend behind one data-access package. Examples use…
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 57 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).
It sits in Development, covering Forms and validation, Monorepo tooling and Backend development. It works with Next.js, TanStack, Zod and Supabase. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Refactoring Next.js 16 code
- RSC vs use client placement
- Monorepo package layout — even when the user doesnt say patterns
Example prompts
- “use client”
- “t say”
- “best practices”
- “/opinionated-nextjs-patterns”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Opinionated Nextjs Patterns loads about 3k tokens when it runs, and up to ~59k if it reads all its reference files. Until then it costs about 217 tokens; SKILL.md has 921 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 921 words, ~3,037 tokens.
Download SKILL.mdSave it as
.claude/skills/opinionated-nextjs-patterns/SKILL.md (or your agent's skills folder). This skill also uses 54 other files; get the full folder from GitHub.- name
- opinionated-nextjs-patterns
- description
- Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route handlers, client/server boundaries ('use client' at leaves + TanStack Query), forms with RHF + Zod, UI via shadcn/ui + Tailwind + Base UI + next-intl, request handling in proxy.ts (Next.js 16's renamed middleware), and a Turbo monorepo of @app/* packages confining the backend behind one data-access package. Examples use Supabase but every rule states the transferable principle. Use when writing, reviewing, or refactoring Next.js 16 code. Trigger on server actions, route handlers, RSC vs 'use client' placement, TanStack Query, RHF/Zod, proxy.ts, or monorepo package layout — even when the user doesn't say 'patterns' or 'best practices'.
Opinionated Next.js 16 Patterns
Implementation-pattern reference for Next.js 16 (App Router) codebases that want a single, opinionated architecture. Contains 50 rules across 8 categories, prioritised by execution-lifecycle cascade impact — authorization and (optional) tenant modeling first, then the request boundary, server fetching, mutations, client boundaries, architecture, and UI conventions.
The rules are backend-agnostic in principle but use Supabase as the concrete example. Each rule teaches the transferable idea (e.g. "authorize at the data layer", "read through a typed repository"); where the backend genuinely matters, a *Transferable:* note explains the pattern for other stores (Drizzle, Prisma). The structure is a Turbo monorepo with @app/* packages you own — built on canonical libraries (next-safe-action, @supabase/ssr, @tanstack/react-query, react-hook-form + zod, shadcn/ui, next-intl, pino), not a vendored starter kit.
When to Apply
Reach for these rules when:
- Writing new code — pages, layouts, server actions, route handlers,
proxy.ts, feature packages, client components, hooks, the data-access package, SQL/migrations, forms. - Reviewing a PR — authorization slips (privileged client without a guard, missing
'server-only'), waterfalls (sequential awaits, client-fetching server data), drift (hand-edited generated types, deep package imports, hardcoded i18n strings). - Refactoring — moving code between
apps/webandpackages/*, splitting actions and services, lifting'use client'boundaries, replacing raw queries with a typed data-access factory, swapping a backend behind the data-access package. - Designing a feature — choosing the right client (request-scoped vs privileged vs browser), deciding action vs route handler, planning the form/server-action contract, scoping a tenant (if multi-tenant).
- Onboarding — understanding why the codebase looks the way it does, with concrete, transferable examples.
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Authorization & Data-Layer Access | CRITICAL | auth- |
| 2 | Multi-Tenancy (optional, SaaS only) | CRITICAL | tenant- |
| 3 | Request Boundary (Proxy) | HIGH | proxy- |
| 4 | Server-Side Data Loading | HIGH | server- |
| 5 | Mutations: Actions & Route Handlers | HIGH | mutate- |
| 6 | Client/Server Boundaries | MEDIUM-HIGH | client- |
| 7 | Architecture & Services | MEDIUM | arch- |
| 8 | Forms & UI Conventions | MEDIUM | ui- |
Quick Reference
1. Authorization & Data-Layer Access (CRITICAL)
auth-use-standard-server-client— Use the request-scoped, auth-bound client; never default to the privileged one.auth-gate-admin-client— Authorize before constructing the service-role client.auth-trust-rls-no-duplicate-checks— Authorize once at the data layer; don't re-check in app code.auth-use-sql-policy-helpers— Centralize scoping predicates in reusable SQL policy helpers.auth-use-require-user— Centralize the auth gate in onerequireUser()helper.auth-server-only-imports— Mark privileged modules withimport 'server-only'.auth-mfa-in-middleware— Enforce MFA at theproxy.tsboundary, not per-page.
2. Multi-Tenancy (CRITICAL — optional, SaaS only)
tenant-accounts-as-tenant-root— One tenant-root table both personal and team workspaces reference.tenant-account-id-on-product-tables— Tenant key + index + scoping policy on every product table.tenant-slug-in-team-urls— Use a human-readable slug in team URLs, not the UUID.tenant-storage-paths-include-account-id— Namespace object-storage paths by tenant id.tenant-never-edit-generated-types— Treat generated DB types as build output; regenerate, never hand-edit.
3. Request Boundary: Proxy (HIGH)
proxy-single-pipeline— Compose the whole request pipeline in oneproxy.ts.proxy-redirect-auth-at-boundary— Perform auth redirects at the proxy, not in pages.proxy-url-pattern-matching— Match proxy routes withURLPattern, not string comparisons.proxy-set-correlation-id— Set a correlation ID at the request boundary.proxy-secure-headers-flagged— Apply strict CSP headers behind an environment flag.
4. Server-Side Data Loading (HIGH)
server-cache-workspace-loaders— Wrap per-request loaders withcache()from React.server-promise-all-parallel-loads— Load independent data in parallel withPromise.all.server-use-feature-api-factories— Read through a typed data-access factory, not rawfrom('table').server-redirect-on-missing-workspace— Redirect from the loader when workspace state is invalid.server-fetch-in-server-components— Fetch initial data in server components, not on the client.server-use-tables-generic-for-types— Use generated row types, not hand-written interfaces.server-services-receive-client— Services receive the data client as a constructor argument.
Show full SKILL.md (369 more words)Show less
5. Mutations: Actions & Route Handlers (HIGH)
mutate-use-safe-action-clients— Route mutations through a typed action client you build on next-safe-action.mutate-zod-schema-separate-file— Put Zod schemas in their own*.schema.tsshared by client and server.mutate-thin-action-service-holds-logic— Keep the action thin; put business logic in a service.mutate-use-getlogger-not-console— Log through a structured logger you own, notconsole.log.mutate-revalidate-path-after-write— CallrevalidatePath()after a successful write.mutate-enhance-route-handler— Wrap route handlers in a typed handler that owns auth and validation.mutate-webhook-verify-signature— Webhook routes skip user-auth and verify the provider signature.
6. Client/Server Boundaries (MEDIUM-HIGH)
client-use-client-at-leaves— Mark'use client'at leaf components, not page roots.client-pass-server-data-as-props— Pass server data to client components as props, don't refetch.client-use-supabase-with-react-query— Pair a memoized browser client with TanStack Query for client reads.client-realtime-cleanup-subscription— Tear down any subscription or event source in theuseEffectreturn.client-use-action-hook— Call server actions withuseActionfromnext-safe-action/hooks.client-stable-query-keys— Use stable, hierarchical query keys.
7. Architecture & Services (MEDIUM)
arch-app-vs-packages-boundary— Reusable capabilities inpackages/, product-specific code inapps/web.arch-data-access-adapter— Confine the backend to one data-access package with a stable surface.arch-feature-package-layout— Feature packages follow acomponents / hooks / schema / serverlayout.arch-import-via-package-exports— Import via the packageexportsmap, never deep internal paths.arch-provider-gateway-pattern— Hide vendor SDKs behind a gateway interface.arch-policy-engine-for-business-rules— Model business rules in a policy layer you own, not inline conditionals.arch-config-driven-navigation— Define routes and navigation inconfig/, not hardcoded in components.
8. Forms & UI Conventions (MEDIUM)
ui-rhf-zod-no-generics— LetzodResolverinfer form types; don't adduseFormgenerics.ui-form-message-per-field— IncludeFormMessagefor every field.ui-kit-ui-package-imports— Import UI from your@app/uidesign-system surface, never internal paths.ui-semantic-tailwind-tokens— Use semantic Tailwind tokens, not hardcoded colors.ui-base-ui-render-not-aschild— Use Base UIrenderprop, not RadixasChild.ui-trans-for-display-text— Render display text through<Trans>oruseTranslations.
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions — Category structure, impact levels, lifecycle rationale.
- Rule template — Template for adding new rules.
- AGENTS.md — Auto-generated TOC for fast navigation.
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering by lifecycle impact |
| assets/templates/_template.md | Template for adding new rules |
| metadata.json | Version, organization, references |
Related Skills
base-ui-migrator— bulk-migrate RadixasChildpatterns to Base UIrenderprops.tailwind-refactor— refactor hardcoded colors to semantic tokens.react-optimise— performance optimisations for React components.nextjs-bundle-optimizer— bundle analysis and reduction for Next.js apps.
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 54 other files (references, assets) in skills/.experimental/opinionated-nextjs-patterns of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/arch-app-vs-packages-boundary.md
- references/arch-config-driven-navigation.md
- references/arch-data-access-adapter.md
- references/arch-feature-package-layout.md
- references/arch-import-via-package-exports.md
- references/arch-policy-engine-for-business-rules.md
- references/arch-provider-gateway-pattern.md
- references/auth-gate-admin-client.md
- references/auth-mfa-in-middleware.md
- references/auth-server-only-imports.md
- references/auth-trust-rls-no-duplicate-checks.md
- references/auth-use-require-user.md
- references/auth-use-sql-policy-helpers.md
- … and 37 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Opinionated Nextjs Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Opinionated Nextjs Patterns this skillpproenca/dot-skills | 214 | — | ~3k | Automated safety check: Pass | MIT | |
| Buzzformbuildnbuzz/buzzform | 101 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Frontend Developmentavibebuilder/claude-prime | 120 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Documentation LookupKaimingWan/oh-my-kiro | 107 | — | ~616 | Automated safety check: Pass | MIT | |
| Web Frontendlatitude-dev/latitude-llm | 4.7k | — | ~5.2k | Automated safety check: Pass | MIT | |
| Shadcn UIjh941213/my-cc-harness | 126 | 4 repos | ~9.7k | Automated safety check: Notes | MIT |
Similar skills
Frontend Development
avibebuilder/claude-prime
A skill your agent uses for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer.
Documentation Lookup
KaimingWan/oh-my-kiro
Fetch current library/framework documentation via Context7. An agent skill from KaimingWan/oh-my-kiro.
Web Frontend
latitude-dev/latitude-llm
apps/web UI — routes, @repo/ui, TanStack Start server functions and collections, navigation (Link vs useNavigate), forms (useForm + createFormSubmitHandler + fieldErrorsAsStrings for Zod field…
Shadcn UI
jh941213/my-cc-harness
Complete shadcn/ui component library guide including installation, configuration, and implementation of accessible React components.
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Questions about Opinionated Nextjs Patterns
What does Opinionated Nextjs Patterns do?
Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route…. Opinionated Nextjs Patterns is an agent skill from pproenca/dot-skills.js 16's renamed middleware), and a Turbo monorepo of @app/ packages confining the backend behind one data-access package.
When should I use Opinionated Nextjs Patterns?
Opinionated Nextjs Patterns fits situations like: refactoring Next.js 16 code; RSC vs use client placement; monorepo package layout — even when the user doesnt say patterns.
How do I install Opinionated Nextjs Patterns in Claude Code?
Run `npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a claude-code`. Or copy the skill folder (skills/.experimental/opinionated-nextjs-patterns in pproenca/dot-skills) into .claude/skills/opinionated-nextjs-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Opinionated Nextjs Patterns in Codex?
Run `npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a codex`. Or copy the skill folder (skills/.experimental/opinionated-nextjs-patterns in pproenca/dot-skills) into .agents/skills/opinionated-nextjs-patterns in your project. Codex loads it when a task matches its description.
Can I use Opinionated Nextjs Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill opinionated-nextjs-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opinionated-nextjs-patterns, .gemini/skills/opinionated-nextjs-patterns, .github/skills/opinionated-nextjs-patterns and .opencode/skills/opinionated-nextjs-patterns in your project.
What does Opinionated Nextjs Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Opinionated Nextjs Patterns is instructions for the agent only.
Does Opinionated Nextjs Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Opinionated Nextjs Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Opinionated Nextjs Patterns use?
Opinionated Nextjs Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Opinionated Nextjs Patterns use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 56k tokens, read only when the agent opens those files.
What are the alternatives to Opinionated Nextjs Patterns?
Skills that share tags, products or a category with Opinionated Nextjs Patterns: Buzzform (buildnbuzz/buzzform, 101 stars), Frontend Development (avibebuilder/claude-prime, 120 stars), Documentation Lookup (KaimingWan/oh-my-kiro, 107 stars) and Web Frontend (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Opinionated Nextjs Patterns?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.