Communitygithub.com

BIGboss248/nextjs-wordpress

为 Next.js 组件生成并更新 co-located Storybook CSF3 故事文件的专用工作流,支持交互式控件、操作间谍和四种规范主题变体。

nextjs-wordpress 是什么?

此技能为 Next.js 开发者提供一套标准化的 Storybook CSF3 故事生成与更新流程。它强制遵循架构规则:仅为主组件创建故事,排除内部微叶子客户端;使用 CSF3 格式(`Meta` 和 `StoryObj`),并自动将 TypeScript 属性映射为交互式控件;通过 `fn()` 间谍函数捕获回调事件,输出到 Actions 面板。更重要的是,它要求生成四种强制故事变体(Light、Dark、SkeletonLight、SkeletonDark),且严格禁止使用硬编码颜色,必须使用 `app/globals.css` 中的语义主题 Token(如 `bg-background`)。支持 Windows (PowerShell) 和 Linux/macOS (Bash) 验证脚本,确保故事文件正确存在并能通过冒烟测试。适用于使用 Storybook 进行组件开发和文档化的 Next.js 项目。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-storybook-story

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

Next.js Storybook CSF3 故事生成 (nextjs-storybook-story)

用于生成和更新 co-located Storybook 故事文件 ([ComponentName].stories.tsx) 的专用工作流,遵循 Component Story Format 3 (CSF3) 规范。

[!TIP] 模块化资源:


架构规则与标准

1. 仅限主组件范围(排除微叶子客户端)

  • 交互式客户端逻辑应下放到小型叶子客户端组件(例如切换按钮、点击监听器)。
  • 不要为内部微叶子客户端辅助函数创建故事。
  • 仅主组件(主要功能区块或复合 UI 块)需要 Storybook 故事。

2. CSF3 结构与交互式控件

  • 使用 Component Story Format 3 (CSF3),包含 Meta<typeof ComponentName> 和 StoryObj<typeof ComponentName>。
  • 包含标签:tags: ["autodocs", "ai-generated"]。
  • 在 meta.argTypes 中将 TypeScript 属性映射为交互式控件(text、select、boolean、number)。
  • 在 args 中提供逼真的默认属性值。

3. 操作间谍 (fn() 来自 'storybook/test')

  • 对于所有回调属性和变更属性(例如 onClick、onToggle、onSubmit),在默认 args 中绑定来自 'storybook/test' 的 fn(),以便用户交互清晰地记录到 Storybook Actions 面板中。

4. 结构化文档 (parameters.docs)

  • 在 meta.parameters.docs.description.component 中编写全面的 markdown 文档:
    • 概述与目的: 组件是什么以及它为何存在。
    • 架构与边界: RSC 与叶子客户端组件 ("use client")、hooks、缓存。
    • 关键交互: 点击处理器、状态切换和动画。
    • 无障碍与动效: ARIA 角色/标签和 prefers-reduced-motion。
  • 使用 parameters.docs.description.story 为单个故事添加注释。

5. 四种规范故事变体与生产 Token(强制)

  • 零硬编码颜色: 在任何情况下都不得使用任意十六进制值(#FAFAFA、#050505)或非 Token 调色板颜色(border-zinc-200、text-zinc-500)。
  • 语义化生产 Token: 只能使用来自 app/globals.css 的语义化主题 Token(bg-background、text-foreground、border-border、text-muted-foreground)。
  • 严格导出四个故事变体,并包裹在具有作用域 .light 和 .dark 类的语义化容器卡片中:
    1. Light:在标记为 "Light Mode" 的 .light bg-background text-foreground border-border 卡片中,配置为 { themes: { themeOverride: "light" }, backgrounds: { default: "light" } }。
    2. Dark:在标记为 "Dark Mode" 的 .dark bg-background text-foreground border-border 卡片中,配置为 { themes: { themeOverride: "dark" }, backgrounds: { default: "dark" } }。
    3. SkeletonLight:在标记为 "Skeleton (Light)" 的 .light bg-background text-foreground border-border 卡片中,使用 render: () => <[ComponentName]Skeleton />。
    4. SkeletonDark:在标记为 "Skeleton (Dark)" 的 .dark bg-background text-foreground border-border 卡片中,使用 render: () => <[ComponentName]Skeleton />。

工作流步骤

  • 步骤 1:检查组件契约与属性

    • 读取 [ComponentName].tsx 并解析所有导出的属性、回调处理器和视觉状态。
  • 步骤 2:生成 Co-Located 故事 ([ComponentName].stories.tsx)

    • 将 [ComponentName].stories.tsx 直接放在 [ComponentName].tsx 旁边。
    • 实现 CSF3 元数据、argTypes、fn() 操作间谍、markdown 文档以及 4 个规范故事变体。
  • 步骤 3:验证与冒烟测试执行

    • 运行验证脚本检查故事是否存在并执行 Storybook 冒烟测试:
      • Windows (PowerShell):
        pwsh .agents/skills/nextjs-storybook-story/scripts/verify-storybook.ps1 -ComponentPath <target_component_dir>
        
      • Linux / macOS (Bash):
        bash .agents/skills/nextjs-storybook-story/scripts/verify-storybook.sh <target_component_dir>
        
    • 修复任何语法冲突或缺少导出的错误。

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

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

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

相关技能