Communitygithub.com

Next.js Pruebas de Calidad Adversarial e Inyección de Casos Ext…

Flujo de trabajo especializado que elimina el sesgo de confirmación del autor al delegar la revisión de código y las pruebas de casos extremos a un subagente auditor adversario independiente.

¿Qué es Next.js Pruebas de Calidad Adversarial e Inyección de Casos Ext…?

Esta skill proporciona un flujo de trabajo para generar pruebas de calidad adversarial en proyectos Next.js, combatiendo el sesgo de confirmación del desarrollador. Cuando el agente principal escribe un componente, esta skill lo obliga a invocar un subagente independiente (mediante `invoke_subagent`) que audita el código e inyecta pruebas de casos extremos en un archivo `[ComponentName].edge.test.tsx`. Las pruebas cubren valores límite, permutaciones de props, estados de error, accesibilidad profunda y estrés/ciclo de vida. Una característica clave es la regla inmutable: nunca se permite modificar o eliminar estas pruebas adversariales; si fallan, se debe arreglar el componente, no los tests. La skill está diseñada para plataformas que soporten subagentes (como Claude Code, Cursor, Codex) y su SKILL.md detalla los pasos: invocar el subagente auditor, inyectar el archivo de pruebas, ejecutar la suite con `pnpm test` y auto-reparar el componente hasta que todas las pruebas pasen.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-adversarial-qa

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Next.js Pruebas de Calidad Adversarial e Inyección de Casos Extremos (nextjs-edge-qa)

Flujo de trabajo especializado para eliminar el sesgo de confirmación del autor, delegando la revisión de código y las pruebas de casos extremos a un subagente auditor adversario independiente.

[!TIP] Documento de referencia:


Reglas y estándares arquitectónicos

1. El principio del auditor imparcial

  • El agente principal que escribió el componente NO debe auto-certificar los casos extremos.
  • DEBES invocar un subagente independiente usando invoke_subagent para auditar el código e inyectar afirmaciones adversariales.

2. Alcance de casos extremos adversariales ([ComponentName].edge.test.tsx)

El subagente DEBE escribir [ComponentName].edge.test.tsx enfocándose en escenarios que los desarrolladores pasan por alto con frecuencia:

  • Valores límite: Cadenas vacías, entradas nulas/indefinidas, cadenas extremadamente largas, glifos Unicode y RTL persa ("سلام دنیا").
  • Permutaciones de props: Combinaciones no manejadas de banderas opcionales.
  • Estados de red y error: Rechazo asíncrono, cargas malformadas, flujos lentos.
  • Accesibilidad y movimiento profundos: Navegación por teclado (Enter, Space, Tab, Escape), aria-expanded, aria-busy, aria-live, captura de foco y prefers-reduced-motion.
  • Estrés y ciclo de vida: Re-renderizados rápidos, limpieza al desmontar, finalización de temporizadores.

3. El principio de pruebas adversariales inmutables

  • Está ESTRICTAMENTE PROHIBIDO modificar o suavizar las pruebas: El desarrollador NO tiene permitido eliminar o debilitar las afirmaciones en [ComponentName].edge.test.tsx.
  • Arregla el código, no los tests: Si una prueba adversarial falla, modifica el componente ([ComponentName].tsx) o la historia ([ComponentName].stories.tsx) para manejar correctamente el caso extremo.

Pasos del flujo de trabajo

  • Paso 1: Invocar subagente auditor adversario

    • Llama a invoke_subagent con:
      • TypeName: "self"
      • Role: "Auditor de código y QA adversario"
      • Model: "inherit"
      • Prompt: Instruye al auditor para que inspeccione [ComponentName].tsx, [ComponentName]Skeleton.tsx, [ComponentName].test.tsx y [ComponentName].stories.tsx, luego genere [ComponentName].edge.test.tsx en el directorio del componente.
  • Paso 2: El auditor inyecta [ComponentName].edge.test.tsx

    • El auditor escribe las afirmaciones de casos extremos y completa la revisión.
  • Paso 3: Ejecutar pruebas adversariales y auto-reparar

    • Ejecuta la suite de pruebas de casos extremos:
      pnpm test -- <target_component_dir>/[ComponentName].edge.test.tsx
      
    • Si alguna prueba falla, corrige la implementación del componente hasta que todas las pruebas pasen con 0 errores.

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

>- 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

>- Configure production health monitoring endpoints (/api/health), Docker Compose probes, and runtime metrics in Next.js App Router applications. Use when asked to "setup health check", "add health endpoint", "docker compose healthcheck nextjs", "configure health monitor", or "/nextjs-healthcheck".

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...

Skills relacionados