Communitygithub.com

BIGboss248/nextjs-wordpress

用於製作同目錄下 Storybook CSF3 故事([ComponentName].stories.tsx)的工作流程與工程標準,包含互動控制項、動作間諜與四種標準主題變體。

nextjs-wordpress 是什麼?

此技能(`nextjs-storybook-story`)為 Next.js 專案中的 Storybook CSF3 故事生成與更新提供一套標準化工作流程。它強制要求故事檔案與元件遵循同目錄慣例,使用 `[ComponentName].stories.tsx` 命名格式。技能的核心價值在於確保故事具備互動控制項(透過 `argTypes` 對應 TypeScript props)、動作間諜(使用 `fn()` 收集回調記錄)以及結構化的文件說明(透過 `parameters.docs`)。此外,它強制匯出四種標準故事變體:淺色模式、深色模式、淺色骨架與深色骨架,且所有顏色都必須使用語意化主題 Token(如 `bg-background`),禁止任何寫死的色碼。此技能支援透過 PowerShell 或 Bash 腳本進行驗證,確保故事正確生成與運作,適用於重視一致元件測試與展示的 Next.js + Storybook 專案。

相容平台~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)

專門用於生成與更新同目錄下 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 props 對應至互動控制項(text、select、boolean、number)。
  • 在 args 中提供實際的預設 prop 值。

3. 動作間諜(使用 'storybook/test' 的 fn())

  • 對於所有回調與突變 props(例如 onClick、onToggle、onSubmit),在預設 args 中綁定來自 'storybook/test' 的 fn(),以便使用者互動能乾淨地記錄在 Storybook Actions 面板中。

4. 結構化文件(parameters.docs)

  • 在 meta.parameters.docs.description.component 中撰寫全面的 Markdown:
    • 概述與目的: 元件的用途與存在理由。
    • 架構與邊界: RSC 與葉客戶端元件("use client")、hook、快取。
    • 關鍵互動: 點擊處理器、狀態切換與動畫。
    • 無障礙與動態效果: 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 bg-background text-foreground border-border 卡片中,配置 { themes: { themeOverride: "light" }, backgrounds: { default: "light" } }。
    2. Dark:在標題為 "深色模式" 的 .dark bg-background text-foreground border-border 卡片中,配置 { themes: { themeOverride: "dark" }, backgrounds: { default: "dark" } }。
    3. SkeletonLight:在標題為 "骨架(淺色)" 的 .light bg-background text-foreground border-border 卡片中,使用 render: () => <[ComponentName]Skeleton />。
    4. SkeletonDark:在標題為 "骨架(深色)" 的 .dark bg-background text-foreground border-border 卡片中,使用 render: () => <[ComponentName]Skeleton />。

工作流程步驟

  • 步驟 1:檢查元件合約與 Props

    • 讀取 [ComponentName].tsx,並解析所有匯出的 props、回調處理器與視覺狀態。
  • 步驟 2:生成同目錄故事([ComponentName].stories.tsx)

    • 將 [ComponentName].stories.tsx 直接放置在 [ComponentName].tsx 旁邊。
    • 實作 CSF3 元資料、argTypes、fn() 動作間諜、Markdown 文件與四種標準故事變體。
  • 步驟 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...

相關技能