[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E21PC34MTPW3VDZM737QY3":3,"skill-same:01M6E21PC34MTPW3VDZM737QY3":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6E21PC34MTPW3VDZM737QY3","copywriting",null,"When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says \"write copy for,\" \"improve this copy,\" \"rewrite this page,\" \"marketing copy,\" \"headline help,\" \"CTA copy,\" \"value proposition,\" \"tagline,\" \"subheadline,\" \"hero section copy,\" \"above the fold,\" \"this copy is weak,\" \"make this more compelling,\" or \"help me describe my product.\" Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.","ByeongminLee\u002Fnextjs-claude-code","ByeongminLee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71276006?v=4","01M6E1S467E7GC0NE144SWHC0V","Byeongmin Lee","01M6E1S4AV3W0B08Z2YBK26VG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fcopywriting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"page","rewrite","pages","feature","me","Fold","use","landing","write","editing","pricing","text","convert","cro","marketing","improve","email","website","product","2026-11-10 10:12:30",false,"---\nname: copywriting\ndescription: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says \"write copy for,\" \"improve this copy,\" \"rewrite this page,\" \"marketing copy,\" \"headline help,\" \"CTA copy,\" \"value proposition,\" \"tagline,\" \"subheadline,\" \"hero section copy,\" \"above the fold,\" \"this copy is weak,\" \"make this more compelling,\" or \"help me describe my product.\" Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.\nmetadata:\n  version: 1.1.0\n---\n\n# Copywriting\n\nYou are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing-context.md` exists (or `.claude\u002Fproduct-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Page Purpose\n- What type of page? (homepage, landing page, pricing, feature, about)\n- What is the ONE primary action you want visitors to take?\n\n### 2. Audience\n- Who is the ideal customer?\n- What problem are they trying to solve?\n- What objections or hesitations do they have?\n- What language do they use to describe their problem?\n\n### 3. Product\u002FOffer\n- What are you selling or offering?\n- What makes it different from alternatives?\n- What's the key transformation or outcome?\n- Any proof points (numbers, testimonials, case studies)?\n\n### 4. Context\n- Where is traffic coming from? (ads, organic, email)\n- What do visitors already know before arriving?\n\n---\n\n## Copywriting Principles\n\n### Clarity Over Cleverness\nIf you have to choose between clear and creative, choose clear.\n\n### Benefits Over Features\nFeatures: What it does. Benefits: What that means for the customer.\n\n### Specificity Over Vagueness\n- Vague: \"Save time on your workflow\"\n- Specific: \"Cut your weekly reporting from 4 hours to 15 minutes\"\n\n### Customer Language Over Company Language\nUse words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.\n\n### One Idea Per Section\nEach section should advance one argument. Build a logical flow down the page.\n\n---\n\n## Writing Style Rules\n\n### Core Principles\n\n1. **Simple over complex** — \"Use\" not \"utilize,\" \"help\" not \"facilitate\"\n2. **Specific over vague** — Avoid \"streamline,\" \"optimize,\" \"innovative\"\n3. **Active over passive** — \"We generate reports\" not \"Reports are generated\"\n4. **Confident over qualified** — Remove \"almost,\" \"very,\" \"really\"\n5. **Show over tell** — Describe the outcome instead of using adverbs\n6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability\n\n### Quick Quality Check\n\n- Jargon that could confuse outsiders?\n- Sentences trying to do too much?\n- Passive voice constructions?\n- Exclamation points? (remove them)\n- Marketing buzzwords without substance?\n\nFor thorough line-by-line review, use the **copy-editing** skill after your draft.\n\n---\n\n## Best Practices\n\n### Be Direct\nGet to the point. Don't bury the value in qualifications.\n\n❌ Slack lets you share files instantly, from documents to images, directly in your conversations\n\n✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.\n\n### Use Rhetorical Questions\nQuestions engage readers and make them think about their own situation.\n- \"Hate returning stuff to Amazon?\"\n- \"Tired of chasing approvals?\"\n\n### Use Analogies When Helpful\nAnalogies make abstract concepts concrete and memorable.\n\n### Pepper in Humor (When Appropriate)\nPuns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.\n\n---\n\n## Page Structure Framework\n\n### Above the Fold\n\n**Headline**\n- Your single most important message\n- Communicate core value proposition\n- Specific > generic\n\n**Example formulas:**\n- \"{Achieve outcome} without {pain point}\"\n- \"The {category} for {audience}\"\n- \"Never {unpleasant event} again\"\n- \"{Question highlighting main pain point}\"\n\n**For comprehensive headline formulas**: See [references\u002Fcopy-frameworks.md](references\u002Fcopy-frameworks.md)\n\n**For natural transition phrases**: See [references\u002Fnatural-transitions.md](references\u002Fnatural-transitions.md)\n\n**Subheadline**\n- Expands on headline\n- Adds specificity\n- 1-2 sentences max\n\n**Primary CTA**\n- Action-oriented button text\n- Communicate what they get: \"Start Free Trial\" > \"Sign Up\"\n\n### Core Sections\n\n| Section | Purpose |\n|---------|---------|\n| Social Proof | Build credibility (logos, stats, testimonials) |\n| Problem\u002FPain | Show you understand their situation |\n| Solution\u002FBenefits | Connect to outcomes (3-5 key benefits) |\n| How It Works | Reduce perceived complexity (3-4 steps) |\n| Objection Handling | FAQ, comparisons, guarantees |\n| Final CTA | Recap value, repeat CTA, risk reversal |\n\n**For detailed section types and page templates**: See [references\u002Fcopy-frameworks.md](references\u002Fcopy-frameworks.md)\n\n---\n\n## CTA Copy Guidelines\n\n**Weak CTAs (avoid):**\n- Submit, Sign Up, Learn More, Click Here, Get Started\n\n**Strong CTAs (use):**\n- Start Free Trial\n- Get [Specific Thing]\n- See [Product] in Action\n- Create Your First [Thing]\n- Download the Guide\n\n**Formula:** [Action Verb] + [What They Get] + [Qualifier if needed]\n\nExamples:\n- \"Start My Free Trial\"\n- \"Get the Complete Checklist\"\n- \"See Pricing for My Team\"\n\n---\n\n## Page-Specific Guidance\n\n### Homepage\n- Serve multiple audiences without being generic\n- Lead with broadest value proposition\n- Provide clear paths for different visitor intents\n\n### Landing Page\n- Single message, single CTA\n- Match headline to ad\u002Ftraffic source\n- Complete argument on one page\n\n### Pricing Page\n- Help visitors choose the right plan\n- Address \"which is right for me?\" anxiety\n- Make recommended plan obvious\n\n### Feature Page\n- Connect feature → benefit → outcome\n- Show use cases and examples\n- Clear path to try or buy\n\n### About Page\n- Tell the story of why you exist\n- Connect mission to customer benefit\n- Still include a CTA\n\n---\n\n## Voice and Tone\n\nBefore writing, establish:\n\n**Formality level:**\n- Casual\u002Fconversational\n- Professional but friendly\n- Formal\u002Fenterprise\n\n**Brand personality:**\n- Playful or serious?\n- Bold or understated?\n- Technical or accessible?\n\nMaintain consistency, but adjust intensity:\n- Headlines can be bolder\n- Body copy should be clearer\n- CTAs should be action-oriented\n\n---\n\n## Output Format\n\nWhen writing copy, provide:\n\n### Page Copy\nOrganized by section:\n- Headline, Subheadline, CTA\n- Section headers and body copy\n- Secondary CTAs\n\n### Annotations\nFor key elements, explain:\n- Why you made this choice\n- What principle it applies\n\n### Alternatives\nFor headlines and CTAs, provide 2-3 options:\n- Option A: [copy] — [rationale]\n- Option B: [copy] — [rationale]\n\n### Meta Content (if relevant)\n- Page title (for SEO)\n- Meta description\n\n---\n\n## Related Skills\n\n- **copy-editing**: For polishing existing copy (use after your draft)\n- **page-cro**: If page structure\u002Fstrategy needs work, not just copy\n- **email-sequence**: For email copywriting\n- **popup-cro**: For popup and modal copy\n- **ab-test-setup**: To test copy variations\n","# Copywriting\n\nYou are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing-context.md` exists (or `.claude\u002Fproduct-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Page Purpose\n- What type of page? (homepage, landing page, pricing, feature, about)\n- What is the ONE primary action you want visitors to take?\n\n### 2. Audience\n- Who is the ideal customer?\n- What problem are they trying to solve?\n- What objections or hesitations do they have?\n- What language do they use to describe their problem?\n\n### 3. Product\u002FOffer\n- What are you selling or offering?\n- What makes it different from alternatives?\n- What's the key transformation or outcome?\n- Any proof points (numbers, testimonials, case studies)?\n\n### 4. Context\n- Where is traffic coming from? (ads, organic, email)\n- What do visitors already know before arriving?\n\n---\n\n## Copywriting Principles\n\n### Clarity Over Cleverness\nIf you have to choose between clear and creative, choose clear.\n\n### Benefits Over Features\nFeatures: What it does. Benefits: What that means for the customer.\n\n### Specificity Over Vagueness\n- Vague: \"Save time on your workflow\"\n- Specific: \"Cut your weekly reporting from 4 hours to 15 minutes\"\n\n### Customer Language Over Company Language\nUse words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.\n\n### One Idea Per Section\nEach section should advance one argument. Build a logical flow down the page.\n\n---\n\n## Writing Style Rules\n\n### Core Principles\n\n1. **Simple over complex** — \"Use\" not \"utilize,\" \"help\" not \"facilitate\"\n2. **Specific over vague** — Avoid \"streamline,\" \"optimize,\" \"innovative\"\n3. **Active over passive** — \"We generate reports\" not \"Reports are generated\"\n4. **Confident over qualified** — Remove \"almost,\" \"very,\" \"really\"\n5. **Show over tell** — Describe the outcome instead of using adverbs\n6. **Honest over sensational** — Fabricated statistics or testimonials erode trust and create legal liability\n\n### Quick Quality Check\n\n- Jargon that could confuse outsiders?\n- Sentences trying to do too much?\n- Passive voice constructions?\n- Exclamation points? (remove them)\n- Marketing buzzwords without substance?\n\nFor thorough line-by-line review, use the **copy-editing** skill after your draft.\n\n---\n\n## Best Practices\n\n### Be Direct\nGet to the point. Don't bury the value in qualifications.\n\n❌ Slack lets you share files instantly, from documents to images, directly in your conversations\n\n✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.\n\n### Use Rhetorical Questions\nQuestions engage readers and make them think about their own situation.\n- \"Hate returning stuff to Amazon?\"\n- \"Tired of chasing approvals?\"\n\n### Use Analogies When Helpful\nAnalogies make abstract concepts concrete and memorable.\n\n### Pepper in Humor (When Appropriate)\nPuns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.\n\n---\n\n## Page Structure Framework\n\n### Above the Fold\n\n**Headline**\n- Your single most important message\n- Communicate core value proposition\n- Specific > generic\n\n**Example formulas:**\n- \"{Achieve outcome} without {pain point}\"\n- \"The {category} for {audience}\"\n- \"Never {unpleasant event} again\"\n- \"{Question highlighting main pain point}\"\n\n**For comprehensive headline formulas**: See [references\u002Fcopy-frameworks.md](references\u002Fcopy-frameworks.md)\n\n**For natural transition phrases**: See [references\u002Fnatural-transitions.md](references\u002Fnatural-transitions.md)\n\n**Subheadline**\n- Expands on headline\n- Adds specificity\n- 1-2 sentences max\n\n**Primary CTA**\n- Action-oriented button text\n- Communicate what they get: \"Start Free Trial\" > \"Sign Up\"\n\n### Core Sections\n\n| Section | Purpose |\n|---------|---------|\n| Social Proof | Build credibility (logos, stats, testimonials) |\n| Problem\u002FPain | Show you understand their situation |\n| Solution\u002FBenefits | Connect to outcomes (3-5 key benefits) |\n| How It Works | Reduce perceived complexity (3-4 steps) |\n| Objection Handling | FAQ, comparisons, guarantees |\n| Final CTA | Recap value, repeat CTA, risk reversal |\n\n**For detailed section types and page templates**: See [references\u002Fcopy-frameworks.md](references\u002Fcopy-frameworks.md)\n\n---\n\n## CTA Copy Guidelines\n\n**Weak CTAs (avoid):**\n- Submit, Sign Up, Learn More, Click Here, Get Started\n\n**Strong CTAs (use):**\n- Start Free Trial\n- Get [Specific Thing]\n- See [Product] in Action\n- Create Your First [Thing]\n- Download the Guide\n\n**Formula:** [Action Verb] + [What They Get] + [Qualifier if needed]\n\nExamples:\n- \"Start My Free Trial\"\n- \"Get the Complete Checklist\"\n- \"See Pricing for My Team\"\n\n---\n\n## Page-Specific Guidance\n\n### Homepage\n- Serve multiple audiences without being generic\n- Lead with broadest value proposition\n- Provide clear paths for different visitor intents\n\n### Landing Page\n- Single message, single CTA\n- Match headline to ad\u002Ftraffic source\n- Complete argument on one page\n\n### Pricing Page\n- Help visitors choose the right plan\n- Address \"which is right for me?\" anxiety\n- Make recommended plan obvious\n\n### Feature Page\n- Connect feature → benefit → outcome\n- Show use cases and examples\n- Clear path to try or buy\n\n### About Page\n- Tell the story of why you exist\n- Connect mission to customer benefit\n- Still include a CTA\n\n---\n\n## Voice and Tone\n\nBefore writing, establish:\n\n**Formality level:**\n- Casual\u002Fconversational\n- Professional but friendly\n- Formal\u002Fenterprise\n\n**Brand personality:**\n- Playful or serious?\n- Bold or understated?\n- Technical or accessible?\n\nMaintain consistency, but adjust intensity:\n- Headlines can be bolder\n- Body copy should be clearer\n- CTAs should be action-oriented\n\n---\n\n## Output Format\n\nWhen writing copy, provide:\n\n### Page Copy\nOrganized by section:\n- Headline, Subheadline, CTA\n- Section headers and body copy\n- Secondary CTAs\n\n### Annotations\nFor key elements, explain:\n- Why you made this choice\n- What principle it applies\n\n### Alternatives\nFor headlines and CTAs, provide 2-3 options:\n- Option A: [copy] — [rationale]\n- Option B: [copy] — [rationale]\n\n### Meta Content (if relevant)\n- Page title (for SEO)\n- Meta description\n\n---\n\n## Related Skills\n\n- **copy-editing**: For polishing existing copy (use after your draft)\n- **page-cro**: If page structure\u002Fstrategy needs work, not just copy\n- **email-sequence**: For email copywriting\n- **popup-cro**: For popup and modal copy\n- **ab-test-setup**: To test copy variations\n",{"name":5,"metadata":48,"description":7},{"version":49},"1.1.0","main","330a71e3d12264515ce3477e446d29fd34a88a9d","template\u002Fskills-archive\u002Fcopywriting",1,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code","https:\u002F\u002Fbyeongminlee.github.io\u002Fnextjs-claude-code\u002F","https:\u002F\u002Fgithub.com\u002FByeongminLee","byeongmin.dev","2026-03-27 12:45:44",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add ByeongminLee\u002Fnextjs-claude-code --skill copywriting",{"tool":65,"command":66},"bunx","bunx skills add ByeongminLee\u002Fnextjs-claude-code --skill copywriting",{"tool":68,"command":69},"pnpm","pnpm dlx skills add ByeongminLee\u002Fnextjs-claude-code --skill copywriting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fcopywriting\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Fevals.json","REFERENCE","参考文档",8158,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fcopywriting\u002Fevals\u002Fevals.json",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcopy-frameworks.md",7887,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fcopywriting\u002Freferences\u002Fcopy-frameworks.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fnatural-transitions.md",5684,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fcopywriting\u002Freferences\u002Fnatural-transitions.md",[88,106,114,144,173,211],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":43},"01M6E263DRDCZ5AX01N6MDYC6Z","zustand","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fzustand\u002FSKILL.md",[],[90,95,96,97,98,30,99,100,101,102,103,104,105],"triggers","state management","zustand state","implementation","guide","management","src","actions","state","code","development",{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":43},"01M6E260QFP3ZMXY2Y6KTGZYXS","web-vitals","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fweb-vitals\u002FSKILL.md",[],[112,113],"web vitals","web",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":43},"01M6E25QEKXHH092S5RB0GKM0K","vercel-storage","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-storage\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"vercel","vercel storage","storage","supabase","api","mongodb","SET","nextjs","database","auth","migrate","click","app","neon","prisma","postgres","expert","up","auto","configure",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":156,"publishedAt":43},"01M6E25EC9YM4QM0KBQ2W5R1SC","vercel-functions","Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",[150,151],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[157,124,158,159,160,161,162,163,136,137,164,165,166,167,168,169,170,171,172,140],"functions","vercel functions","local","shared","project","time","apps","express","vercel ai sdk","router","loop","server","logs","streaming","delete","create",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":194,"publishedAt":43},"01M6E25873YRYP96MSQK7E2D9X","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fui-ux-pro-max\u002FSKILL.md",[179,182,185,188,191],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":189,"categoryName":190,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":192,"categoryName":193,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000033","数据分析师",[195,196,197,198,199,200,201,202,136,203,204,205,206,207,39,208,209,102,210,172],"ui ux pro max","ui","ux","max","css","MCP","design","react","card","chart","fix","projects","plan","Tailwind","Animation","search",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":43},"01M6E251G3FJSRB9019V20QK9X","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturborepo\u002FSKILL.md",[],[213,218,30,219,220,163,95,221,222,141,223,224,225,226,227,228,104,229,230,231],"cli","filter","environment variables","caching","structure","environment","monorepo","system","canary","Optimization","ci","packages","tasks","workflows"]