Communitygithub.com

BIGboss248/nextjs-wordpress

독립적인 서브 에이전트를 생성하여 편향 없는 코드 리뷰를 수행하고, 적대적 엣지 케이스 테스트([ComponentName].edge.test.tsx)를 주입하는 워크플로우입니다.

nextjs-wordpress란 무엇인가요?

이 스킬은 Next.js 컴포넌트 개발 시 작성자 확증 편향을 제거하기 위해 설계된 전문 워크플로우입니다. 주 에이전트가 작성한 컴포넌트의 엣지 케이스를 스스로 검증하는 것을 금지하고, 대신 `invoke_subagent`를 통해 독립적인 적대적 감사 서브 에이전트를 생성하여 코드 리뷰와 엣지 케이스 테스트를 수행하도록 합니다. 서브 에이전트는 `[ComponentName].edge.test.tsx` 파일을 생성하며, 여기에는 개발자들이 자주 놓치는 경계값, 누락된 prop 조합, 네트워크 오류 상태, 접근성 및 모션 선호도 관련 테스트 등이 포함됩니다. 이 스킬의 핵심 원칙은 생성된 적대적 테스트를 절대 수정하거나 약화시키지 않고, 테스트가 실패할 경우 컴포넌트 코드를 수정하여 모든 테스트를 통과시키는 것입니다. 이 워크플로우는 Claude Code, Cursor, Codex 등 `invoke_subagent`를 지원하는 모든 AI 에이전트 플랫폼에서 사용할 수 있습니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-adversarial-qa
원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

Next.js 적대적 QA 및 엣지 케이스 주입 (nextjs-adversarial-qa)

작성자 확증 편향을 제거하기 위해 코드 리뷰와 엣지 케이스 테스트를 독립적인 적대적 감사 서브 에이전트에 위임하는 특화 워크플로우입니다.

[!TIP] 참고 문서:

아키텍처 규칙 및 표준

1. 편향 없는 감사자 원칙

  • 컴포넌트를 작성한 주 에이전트는 엣지 케이스를 자체 인증해서는 안 됩니다.
  • 반드시 invoke_subagent를 사용하여 독립적인 서브 에이전트를 생성하고, 코드를 감사하며 적대적 어서션을 주입하도록 해야 합니다.

2. 적대적 엣지 케이스 범위 ([ComponentName].edge.test.tsx)

서브 에이전트는 개발자들이 자주 간과하는 시나리오를 대상으로 [ComponentName].edge.test.tsx를 작성해야 합니다:

  • 경계값: 빈 문자열, null/undefined 입력, 매우 긴 문자열, 유니코드 및 페르시아어 RTL 글리프 ("سلام دنیا").
  • Prop 순열: 선택적 플래그의 처리되지 않은 조합.
  • 네트워크 및 오류 상태: 비동기 거부, 잘못된 형식의 페이로드, 느린 스트림.
  • 심층 접근성 및 모션: 키보드 탐색 (Enter, Space, Tab, Escape), aria-expanded, aria-busy, aria-live, 포커스 트래핑 및 prefers-reduced-motion.
  • 스트레스 및 생명주기: 빠른 재렌더링, 언마운트 정리, 타이머 해제.

3. 불변 적대적 테스트 원칙

  • 테스트 수정 또는 약화는 엄격히 금지됩니다: 개발자는 [ComponentName].edge.test.tsx의 어서션을 삭제하거나 약화시킬 수 없습니다.
  • 테스트를 수정하지 말고 코드를 수정하세요: 적대적 테스트가 실패하면 엣지 케이스를 적절히 처리하도록 컴포넌트([ComponentName].tsx) 또는 스토리([ComponentName].stories.tsx)를 수정하세요.

워크플로우 단계

  • 1단계: 적대적 감사 서브 에이전트 생성

    • 다음 매개변수로 invoke_subagent를 호출하세요:
      • TypeName: "self"
      • Role: "Adversarial Code & QA Auditor"
      • Model: "inherit"
      • Prompt: 감사자에게 [ComponentName].tsx, [ComponentName]Skeleton.tsx, [ComponentName].test.tsx, [ComponentName].stories.tsx를 검사하고 컴포넌트 디렉토리에 [ComponentName].edge.test.tsx를 생성하도록 지시합니다.

  • 2단계: 감사자가 [ComponentName].edge.test.tsx 주입

    • 감사자가 엣지 케이스 어서션을 작성하고 리뷰를 완료합니다.

  • 3단계: 적대적 테스트 실행 및 자동 복구

    • 엣지 케이스 테스트 스위트를 실행합니다: 
      pnpm test -- <target_component_dir>/[ComponentName].edge.test.tsx
    • 테스트가 실패하면 모든 엣지 테스트가 오류 없이 통과할 때까지 컴포넌트 구현을 패치합니다.

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

관련 스킬

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community