Communitygithub.com

nextjs-healthcheck

Configure endpoints de monitoramento de saúde de produção (/api/health), sondas Docker Compose e métricas de runtime em aplicações Next.js App Router. Use quando for solicitado a 'configurar health check', 'adicionar health endpoint', 'docker compose healthcheck nextjs', 'configurar monitor de saúde' ou '/nextjs-healthcheck'.

O que é nextjs-healthcheck?

Esta skill fornece um fluxo de trabalho modular e pronto para produção para criar e manter endpoints de health check (/api/health), sondas de saúde Docker Compose sem dependências externas e métricas de runtime do Node.js em aplicações Next.js App Router. Ela escaneia o projeto em busca de bancos de dados (Prisma, Drizzle, Supabase, Mongoose, PostgreSQL, Redis) e arquivos Docker Compose, gera o roteador de health check apropriado com ou sem conexão ao banco de dados, injeta blocos de health check nos serviços Next.js identificados nos arquivos compose e fornece etapas de verificação e validação. A skill é particularmente útil para desenvolvedores que precisam implementar monitoramento de saúde em produção sem dependências adicionais, evitando armadilhas comuns como respostas em cache, conexões de banco de dados penduradas e dependências de ferramentas externas em containers. Ela suporta Next.js App Router e fluxos de trabalho de desenvolvimento baseados em Docker Compose.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-healthcheck

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Habilidade de Health Check e Observabilidade para Next.js (nextjs-healthcheck)

Um fluxo de trabalho modular e pronto para produção para criar e manter endpoints de health check (/api/health), sondas de saúde Docker Compose sem dependências externas e métricas de runtime do Node.js em aplicações Next.js App Router.


Visão Geral do Fluxo de Trabalho

flowchart TD
    A["1. Escanear Projeto<br/>(Banco de Dados & Docker Compose)"] --> B["2. Gerar /api/health<br/>(Modelos com Métricas)"]
    B --> C["3. Injetar Sondas Docker<br/>(docker-compose.yml)"]
    C --> D["4. Verificar & Validar<br/>(curl & docker compose ps)"]

Manual de Execução Passo a Passo

Siga esta lista de verificação sequencialmente para implementar e verificar o monitoramento de saúde da aplicação:

1. Descoberta do Projeto e Inspeção de Dependências

  • Localizar Caminho do Manipulador de Rota: Determine se o projeto usa app/ ou src/app/ (alvo: app/api/health/route.ts ou src/app/api/health/route.ts).
  • Detectar Banco de Dados / Armazenamentos Externos: Escaneie package.json em busca de ORMs e clientes (Prisma, Drizzle, Supabase, Mongoose, PostgreSQL, Redis). Consulte database-probes.md.
  • Localizar Arquivos Docker Compose: Descubra docker-compose.yml, docker-compose.prod.yml ou outras stacks do compose. Consulte docker-compose-probes.md.

2. Implementar Manipulador de Rota de Health Check

  • Selecionar Modelo de Rota:
  • Forçar Execução Dinâmica: Garanta que export const dynamic = "force-dynamic"; e cabeçalhos Cache-Control: no-store, no-cache, must-revalidate estejam presentes.
  • Configurar Métricas Não Bloqueantes: Colete saturação do heap V8, atraso do loop de eventos (lag $p99$ via perf_hooks) e tempo de atividade do processo. Consulte status-and-metrics.md.
  • Aplicar Disciplina de Código de Status HTTP: Retorne 200 OK para healthy/degraded e 503 Service Unavailable para unhealthy.

3. Configurar Sondas de Saúde Docker Compose

  • Identificar Serviços Next.js: Inspecione arquivos compose detectados em busca de blocos de serviço Next.js (nextjs-app, web, app).
  • Injetar Bloco de Healthcheck: Adicione a sonda de saúde Node.js fetch sem dependências externas de docker-compose.healthcheck.template.yml.

4. Verificação e Testes

  • Teste de API Local:
    curl -i http://localhost:3000/api/health
    
    Verifique a resposta HTTP 200 com payload JSON válido (status, timestamp, uptimeSeconds, checks).
  • Verificação de Status de Saúde do Compose:
    docker compose ps
    
    Verifique se o estado do serviço transita para (healthy) após o período inicial de inicialização.

Casos Extremos e Armadilhas Conhecidas de IA

[!WARNING]

  • force-dynamic Ausente: O Next.js App Router pode avaliar estaticamente ou armazenar em cache respostas de rota se export const dynamic = "force-dynamic" for omitido, causando timestamps desatualizados e métricas de tempo de atividade congeladas.
  • Conexões de Banco de Dados Penduradas: Nunca consulte bancos de dados externos sem um limite de tempo de espera (máx. 2000ms). A latência de rede não tratada pode causar exaustão do pool de requisições.
  • Dependências de Ferramentas Externas em Containers: Não confie em curl ou wget em health checks Docker; imagens mínimas de produção (ex.: node:alpine ou distroless) frequentemente não as possuem. Use o fetch nativo do Node.js via node -e.
  • Vazamento de Segredos: Nunca imprima URLs de conexão de banco de dados, senhas ou rastros de erro interno brutos no payload de resposta pública de /api/health.

Esquema de Resumo de Saída

Ao concluir a configuração do health check, forneça um relatório de resumo conciso:

### Configuração de Monitoramento de Saúde Concluída

- **Manipulador de Rota**: `[app/api/health/route.ts](file:///...)`
- **Sondas de Banco de Dados**: [Configurado: Prisma / Drizzle / Nenhum] (Timeout: 2000ms)
- **Métricas de Runtime**: Saturação do Heap V8 e Atraso do Loop de Eventos (p99)
- **Stacks Docker Compose Atualizados**: `docker-compose.yml`, `docker-compose.prod.yml`
- **Status de Verificação**: APROVADO (HTTP 200 / Container Saudável)

Guias de Referência e Modelos

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

BIGboss248/nextjs-wordpress

Create, configure, manage, and validate Google Antigravity customizations including skills, rules, MCP servers, lifecycle hooks, plugins, and custom JSON configs. Use when adding new capabilities to Antigravity, configuring MCP servers, writing rules, creating skills, setting up hooks, or modernizing legacy workflows.

BIGboss248/nextjs-wordpress

Spawn multiple agents into a shared conversation where they debate, disagree, and converge on a solution via a shared chat.json file. Use for architecture decisions, code review debates, design trade-offs, or any problem that benefits from adversarial reasoning. Triggers on "chatroom", "agent debate", "have agents discuss", "agent chatroom", "debate this", or /agent-chatrooms. Also triggers on phrases like "have 3 agents argue about", "multi-agent discussion", or "let them debate".

BIGboss248/nextjs-wordpress

Always-active code intelligence, search, and navigation skill utilizing the codebase-memory MCP server. Enforces an index-first protocol (verifying and refreshing the knowledge graph via index_repository or index_status before searching, required because background auto_watch is disabled to eliminate editor stutter and system lag), followed by graph-first exploration (search_graph, trace_path, get_code_snippet, query_graph, get_architecture, detect_changes) instead of naive text grep or full-file reads. Always activate before searching the codebase, inspecting unknown architecture, finding symbols, or tracing callers/callees.

BIGboss248/nextjs-wordpress

>- Discover, interview, and craft comprehensive UX/UI design specifications (design-spec.md) and design tokens for web components. Triggers on "/component-design", "design component", "design section", "design UI", "wireframe component", or "create design spec".

BIGboss248/nextjs-wordpress

>- Configure and query WooCommerce APIs including WPGraphQL, WooGraphQL, and JWT auth for headless frontends. Use when connecting Next.js to WooCommerce or fetching store catalog data.

BIGboss248/nextjs-wordpress

Orchestrate parallel browser automation using multiple Chrome DevTools MCP instances. Use when a task requires doing the same browser action across many targets simultaneously (e.g., submitting contact forms, filling applications, scraping pages that need JS rendering). Spin up 1-5 parallel Chrome agents.

BIGboss248/nextjs-wordpress

Workflow for spawning an independent subagent to conduct unbiased code reviews and inject adversarial edge-case tests ([ComponentName].edge.test.tsx).

BIGboss248/nextjs-wordpress

>- Build Next.js App Router React components with Suspense skeletons, semantic OKLCH tokens, Jest + RTL unit tests, Playwright visual/hydration checks, and Tailwind logical styling. Triggers on "/nextjs-component-dev", "create component", "new component", "build component", or "develop component".

BIGboss248/nextjs-wordpress

>- Bootstrap, configure, and verify the complete Next.js App Router development environment, developer tooling, testing suites, MCP servers, Docker containerization, and CI/CD. Triggers on "/nextjs-dev-setup", "setup nextjs dev environment", "start a nextjs project", or "containerize nextjs app".

BIGboss248/nextjs-wordpress

Bootstrap, configure, and verify next-intl App Router internationalization (proxy.ts/middleware.ts, next/root-params, [locale] layout, routing). Triggers on "/nextjs-i18n-setup", "setup i18n", "install next-intl", "configure next-intl", "add internationalization", "setup locale routing", "migrate to [locale]".

BIGboss248/nextjs-wordpress

Read/write translation dictionaries (messages/[locale].json), next-intl hooks (getTranslations/useTranslations), providers (Storybook/tests/subtrees), and BiDi styling. Triggers on "/nextjs-i18n-usage", "i18n dictionary", "use translations", "read dictionary", "i18n provider", "next-intl hooks", "storybook i18n", "test i18n", "add translation keys", "localize component", "create a component", "update a component".

BIGboss248/nextjs-wordpress

>- Configure, test, and verify OpenTelemetry (OTel) observability in Next.js App Router applications. Triggers on "/nextjs-otel", "setup otel", "configure opentelemetry", "test otel", or "verify opentelemetry".

BIGboss248/nextjs-wordpress

Step-by-step workflow for designing and building Next.js App Router pages (RSC page.tsx, loading skeleton, metadata, JSON-LD schema, and dynamic static params). Triggers on "/nextjs-page-dev", "create page", "new page", "develop page", "build route", or "implement page".

BIGboss248/nextjs-wordpress

>- Orchestrate end-to-end planning for Next.js App Router projects, generating canonical specifications, design systems, and a 7-phase modular implementation roadmap in docs/plan/. Triggers on "/nextjs-plan", "plan a nextjs project", "plan nextjs app", "create nextjs project plan", "outline nextjs architecture", or "generate plan".

BIGboss248/nextjs-wordpress

Workflow and engineering standards for crafting co-located Storybook CSF3 stories ([ComponentName].stories.tsx) with interactive controls, action spies, and 4 canonical theme variants.

BIGboss248/nextjs-wordpress

>- Build Next.js e-commerce frontends backed by WooCommerce APIs, handling ISR catalogs, cart sessions, and JWT authentication. Use when building or querying Next.js stores with WooCommerce.

BIGboss248/nextjs-wordpress

Self-correcting rules engine and feedback loop that learns from user corrections, mistakes, and project-specific constraints by maintaining a persistent autofix ruleset. Scans learned rules before starting any task, resolves conflicts, and automatically appends new rules upon corrections. Triggers on user corrections ("no, do it this way", "never do X", "always use Y"), /learn, "self repair", "add rule", "update rules", or when diagnosing assumptions and bugs. CRITICAL ALWAYS-ACTIVE LIFECYCLE SKILL. Must always be kept in context, loaded at session start, and consulted before starting ANY task to read and apply active constraints from autofix.json. MUST ALWAYS be triggered immediately whenever the user provides ANY correction, preference, criticism, rejection of an approach, or adjustment ("no", "don't do X", "use Y", "remember", "prefer"), or when any mistake/bug is identified. Automatically and immediately formulates and appends the new imperative rule to the project's autofix.json ruleset file.

BIGboss248/nextjs-wordpress

Setup, automate, and execute SEO audits, CI/CD pre-push/pre-deploy checks, and ranking optimizations using the seo CLI and MCP server.

BIGboss248/nextjs-wordpress

End-to-end repository onboarding and development environment setup skill. Scans repository structure, configures project metadata (docs/project.json), sets up the codebase-memory-mcp code intelligence knowledge graph server (in workspace mcp.json and globally for AGY only), configures git hooks with Husky and Commitlint, establishes multi-stage production Docker containerization, and automates credit-optimized Release Please CI/CD with multi-arch (AMD64 & ARM64) GHCR package deployment. Triggers on "/setup-repository", "setup repository", "setup repo", "initialize repository", "new repo setup", or when preparing any repository for development and AI agent workflows.

BIGboss248/nextjs-wordpress

AI screen scaffolding, layout generation, and variant exploration workflow powered by Google Stitch (StitchMCP). Consumes a component design specification (docs/design/components/[page name]/[component name]/design-spec.md), verifies and reuses the central Stitch project in docs/project.json (or creates/persists one if absent), seeds the project's design system into Stitch, synthesizes layout prompts to generate a screen and create one variant of the given design spec file, downloads and saves Stitch JPG screenshots and HTML code files directly into docs/design/components/[page name]/[component name]/stitch/ using binary-safe PowerShell Invoke-WebRequest, outputs image prompts to the user if visual assets are needed (without calling generate_image to conserve tokens), updates design-spec.md with Stitch layout benchmarks, and audits asset download integrity with an independent subagent. Triggers on "/stitch-design", "generate stitch screen", "create stitch variant", "scaffold screen with stitch", or "stitch...

Habilidades Relacionadas