flags — for Claude Code PokeMMO-Compendium, community, for Claude Code, ide skills, gemini, tailwindcss, typescript, config-shared.ts, config-schema.ts, app-page.ts

v1.0.0

Sobre este Skill

Cenario recomendado: Ideal for AI agents that need use this skill when adding or changing framework feature flags in next.js internals. Resumo localizado: # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers gemini, react, tailwindcss workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Recursos

Use this skill when adding or changing framework feature flags in Next.js internals.
Where the Flag Is Consumed
For runtime flags, also add the field to the NextConfigRuntime Pick type in config-shared.ts.
Runtime-Bundle Model
Runtime bundles are built by next-runtime.webpack-config.js (rspack) via taskfile.js bundle tasks.

# Core Topics

SolaneHub SolaneHub
[0]
[1]
Updated: 3/22/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
33
Canonical Locale
en
Detected Body Locale
en

Cenario recomendado: Ideal for AI agents that need use this skill when adding or changing framework feature flags in next.js internals. Resumo localizado: # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers gemini, react, tailwindcss workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Por que usar essa habilidade

Recomendacao: flags helps agents use this skill when adding or changing framework feature flags in next.js internals. Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals.

Melhor para

Cenario recomendado: Ideal for AI agents that need use this skill when adding or changing framework feature flags in next.js internals.

Casos de Uso Práticos for flags

Caso de uso: Applying Use this skill when adding or changing framework feature flags in Next.js internals
Caso de uso: Applying Where the Flag Is Consumed
Caso de uso: Applying For runtime flags, also add the field to the NextConfigRuntime Pick type in config-shared.ts

! Segurança e Limitações

  • Limitacao: $dce-edge - DCE-safe require patterns and edge constraints
  • Limitacao: Required Wiring All flags need: config-shared.ts (type) → config-schema.ts (zod)
  • Limitacao: Runtime-only flags consumed exclusively in pre-compiled bundles can skip define-env.ts

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is flags?

Cenario recomendado: Ideal for AI agents that need use this skill when adding or changing framework feature flags in next.js internals. Resumo localizado: # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers gemini, react, tailwindcss workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install flags?

Run the command: npx killer-skills add SolaneHub/PokeMMO-Compendium/flags. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for flags?

Key use cases include: Caso de uso: Applying Use this skill when adding or changing framework feature flags in Next.js internals, Caso de uso: Applying Where the Flag Is Consumed, Caso de uso: Applying For runtime flags, also add the field to the NextConfigRuntime Pick type in config-shared.ts.

Which IDEs are compatible with flags?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for flags?

Limitacao: $dce-edge - DCE-safe require patterns and edge constraints. Limitacao: Required Wiring All flags need: config-shared.ts (type) → config-schema.ts (zod). Limitacao: Runtime-only flags consumed exclusively in pre-compiled bundles can skip define-env.ts.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add SolaneHub/PokeMMO-Compendium/flags. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use flags immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

flags

Install flags, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Feature Flags

Use this skill when adding or changing framework feature flags in Next.js internals.

Required Wiring

All flags need: config-shared.ts (type) → config-schema.ts (zod). If the flag is consumed in user-bundled code (client components, edge routes, app-page.ts template), also add it to define-env.ts for build-time injection. Runtime-only flags consumed exclusively in pre-compiled bundles can skip define-env.ts.

Where the Flag Is Consumed

Client/bundled code only (e.g. __NEXT_PPR in client components): define-env.ts is sufficient. Webpack/Turbopack replaces process.env.X at the user's build time.

Pre-compiled runtime bundles (e.g. code in app-render.tsx): The flag must also be set as a real process.env var at runtime, because app-render.tsx runs from pre-compiled bundles where define-env.ts doesn't reach. Two approaches:

  • Runtime env var: Set in next-server.ts + export/worker.ts. Both code paths stay in one bundle. Simple but increases bundle size.
  • Separate bundle variant: Add DefinePlugin entry in next-runtime.webpack-config.js (scoped to bundleType === 'app'), new taskfile tasks, update module.compiled.js selector, and still set env var in next-server.ts + export/worker.ts for bundle selection. Eliminates dead code but adds build complexity.

For runtime flags, also add the field to the NextConfigRuntime Pick type in config-shared.ts.

Runtime-Bundle Model

  • Runtime bundles are built by next-runtime.webpack-config.js (rspack) via taskfile.js bundle tasks.
  • Bundle selection occurs at runtime in src/server/route-modules/app-page/module.compiled.js based on process.env vars.
  • Variants: {turbo/webpack} × {experimental/stable/nodestreams/experimental-nodestreams} × {dev/prod} = up to 16 bundles per route type.
  • define-env.ts affects user bundling, not pre-compiled runtime internals.
  • process.env.X checks in app-render.tsx are either replaced by DefinePlugin at runtime-bundle-build time, or read as actual env vars at server startup. They are NOT affected by the user's defines from define-env.ts.
  • Gotcha: DefinePlugin entries in next-runtime.webpack-config.js must be scoped to the correct bundleType (e.g. app only, not server) to avoid replacing assignment targets in next-server.ts.
  • $dce-edge - DCE-safe require patterns and edge constraints
  • $react-vendoring - entry-base boundaries and vendored React
  • $runtime-debug - reproduction and verification workflow

Habilidades Relacionadas

Looking for an alternative to flags or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

widget-generator

Logo of f
f

Gerar plugins de widgets personalizáveis para o sistema de feed do prompts.chat

flags

Logo of vercel
vercel

O Framework React

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Desenvolvedor