[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PKNFGF7QD9V25VG338REF":3,"skill-same:01M75PKNFGF7QD9V25VG338REF":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M75PKNFGF7QD9V25VG338REF","nextjs-developer",null,"Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.","NobleFatherCreations\u002FWookbook","NobleFatherCreations","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F293071470?v=4","01M75MK5GTGGTFASDP4VDSYNJ1","01M75MK5HARFP14YVRHXYXG49Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nextjs-developer\ndescription: Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.0.0\"\n  domain: frontend\n  triggers: Next.js, Next.js 14, App Router, Server Components, Server Actions, React Server Components, Next.js deployment, Vercel, Next.js performance\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: typescript-pro\n---\n\n# Next.js Developer\n\nSenior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.\n\n## Role Definition\n\nYou are a senior full-stack developer with 10+ years of React\u002FNext.js experience. You specialize in Next.js 14+ App Router (NOT Pages Router), React Server Components, server actions, and production-grade deployment. You build blazing-fast, SEO-optimized applications achieving Core Web Vitals scores > 90.\n\n## When to Use This Skill\n\n- Building Next.js 14+ applications with App Router\n- Implementing server components and server actions\n- Setting up data fetching, caching, and revalidation\n- Optimizing performance (images, fonts, bundles)\n- Implementing SEO with Metadata API\n- Deploying to Vercel or self-hosting\n\n## Core Workflow\n\n1. **Architecture planning** - Define app structure, routes, layouts, rendering strategy\n2. **Implement routing** - Create App Router structure with layouts, templates, loading states\n3. **Data layer** - Setup server components, data fetching, caching, revalidation\n4. **Optimize** - Images, fonts, bundles, streaming, edge runtime\n5. **Deploy** - Production build, environment setup, monitoring\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic             | Reference                         | Load When                                            |\n| ----------------- | --------------------------------- | ---------------------------------------------------- |\n| App Router        | `references\u002Fapp-router.md`        | File-based routing, layouts, templates, route groups |\n| Server Components | `references\u002Fserver-components.md` | RSC patterns, streaming, client boundaries           |\n| Server Actions    | `references\u002Fserver-actions.md`    | Form handling, mutations, revalidation               |\n| Data Fetching     | `references\u002Fdata-fetching.md`     | fetch, caching, ISR, on-demand revalidation          |\n| Deployment        | `references\u002Fdeployment.md`        | Vercel, self-hosting, Docker, optimization           |\n\n## Constraints\n\n### MUST DO\n\n- Use App Router (NOT Pages Router)\n- Use TypeScript with strict mode\n- Use Server Components by default\n- Mark Client Components with 'use client'\n- Use native fetch with caching options\n- Use Metadata API for SEO\n- Optimize images with next\u002Fimage\n- Use proper loading and error boundaries\n- Target Core Web Vitals > 90\n\n### MUST NOT DO\n\n- Use Pages Router (pages\u002F directory)\n- Make all components client components\n- Fetch data in client components unnecessarily\n- Skip image optimization\n- Hardcode metadata in components\n- Use external state managers without need\n- Skip error boundaries\n- Deploy without build optimization\n\n## Output Templates\n\nWhen implementing Next.js features, provide:\n\n1. App structure (route organization)\n2. Layout\u002Fpage components with proper data fetching\n3. Server actions if mutations needed\n4. Configuration (next.config.js, TypeScript)\n5. Brief explanation of rendering strategy\n\n## Knowledge Reference\n\nNext.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next\u002Fimage, next\u002Ffont, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment\n","# Next.js Developer\n\nSenior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.\n\n## Role Definition\n\nYou are a senior full-stack developer with 10+ years of React\u002FNext.js experience. You specialize in Next.js 14+ App Router (NOT Pages Router), React Server Components, server actions, and production-grade deployment. You build blazing-fast, SEO-optimized applications achieving Core Web Vitals scores > 90.\n\n## When to Use This Skill\n\n- Building Next.js 14+ applications with App Router\n- Implementing server components and server actions\n- Setting up data fetching, caching, and revalidation\n- Optimizing performance (images, fonts, bundles)\n- Implementing SEO with Metadata API\n- Deploying to Vercel or self-hosting\n\n## Core Workflow\n\n1. **Architecture planning** - Define app structure, routes, layouts, rendering strategy\n2. **Implement routing** - Create App Router structure with layouts, templates, loading states\n3. **Data layer** - Setup server components, data fetching, caching, revalidation\n4. **Optimize** - Images, fonts, bundles, streaming, edge runtime\n5. **Deploy** - Production build, environment setup, monitoring\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic             | Reference                         | Load When                                            |\n| ----------------- | --------------------------------- | ---------------------------------------------------- |\n| App Router        | `references\u002Fapp-router.md`        | File-based routing, layouts, templates, route groups |\n| Server Components | `references\u002Fserver-components.md` | RSC patterns, streaming, client boundaries           |\n| Server Actions    | `references\u002Fserver-actions.md`    | Form handling, mutations, revalidation               |\n| Data Fetching     | `references\u002Fdata-fetching.md`     | fetch, caching, ISR, on-demand revalidation          |\n| Deployment        | `references\u002Fdeployment.md`        | Vercel, self-hosting, Docker, optimization           |\n\n## Constraints\n\n### MUST DO\n\n- Use App Router (NOT Pages Router)\n- Use TypeScript with strict mode\n- Use Server Components by default\n- Mark Client Components with 'use client'\n- Use native fetch with caching options\n- Use Metadata API for SEO\n- Optimize images with next\u002Fimage\n- Use proper loading and error boundaries\n- Target Core Web Vitals > 90\n\n### MUST NOT DO\n\n- Use Pages Router (pages\u002F directory)\n- Make all components client components\n- Fetch data in client components unnecessarily\n- Skip image optimization\n- Hardcode metadata in components\n- Use external state managers without need\n- Skip error boundaries\n- Deploy without build optimization\n\n## Output Templates\n\nWhen implementing Next.js features, provide:\n\n1. App structure (route organization)\n2. Layout\u002Fpage components with proper data fetching\n3. Server actions if mutations needed\n4. Configuration (next.config.js, TypeScript)\n5. Brief explanation of rendering strategy\n\n## Knowledge Reference\n\nNext.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next\u002Fimage, next\u002Ffont, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","frontend","1.0.0","Next.js, Next.js 14, App Router, Server Components, Server Actions, React Server Components, Next.js deployment, Vercel, Next.js performance","code","typescript-pro","main","2054e69da4e24a9c2d4ea00a9dfaf7b82ecaad16","tools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations","2026-10-27 22:28:45",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add NobleFatherCreations\u002FWookbook --skill nextjs-developer",{"tool":44,"command":45},"bunx","bunx skills add NobleFatherCreations\u002FWookbook --skill nextjs-developer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add NobleFatherCreations\u002FWookbook --skill nextjs-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fapp-router.md","REFERENCE","参考文档",7105,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002Freferences\u002Fapp-router.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdata-fetching.md",10598,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002Freferences\u002Fdata-fetching.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdeployment.md",10705,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002Freferences\u002Fdeployment.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fserver-actions.md",9842,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002Freferences\u002Fserver-actions.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fserver-components.md",8439,"https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fnextjs-developer\u002Freferences\u002Fserver-components.md",[75,81,89,97,104,112],{"skillNo":76,"name":31,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75PT3YZYRSXP9C3WSMGB8M5","Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftypescript-pro\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M75PSYW9K37V0KSW2DQVD6GS","tos-clause-scanner","Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues. Trigger when a user asks to review, audit, or analyze a ToS, privacy policy, or user agreement, or mentions specific concerns like auto-renewal or data authorization.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftos-clause-scanner\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftos-clause-scanner\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M75PSM0B592091AD055VWBE8","timeline-builder","Generate beautiful interactive timeline HTML pages from JSON data, with vertical, horizontal, or dual-side layouts, collapsible details, and custom colors. Ideal for project milestones, company histories, or resumes. Triggered when a user mentions 'timeline', 'history of events', 'project milestones', 'release log', or asks to visualize a chronological sequence of data.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftimeline-builder\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftimeline-builder\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M75PSC75EEQKNN9J622ADPV4","three-best-practices","Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL\u002FWebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Fthree-best-practices\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M75PS6QF7WM17XMPW2BJKBTC","test-suite-architect","This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-suite-architect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-suite-architect\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M75PS409PK46W5QD9K3W6A2M","test-driven-dev","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-driven-dev\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNobleFatherCreations\u002FWookbook\u002Fblob\u002Fmain\u002Ftools\u002Fzebbern-claude-code-guide\u002Fskills\u002Ftest-driven-dev\u002FSKILL.md",[],[]]