[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JBYF2P3CFZAVQ7CFVQZXKF":3,"skill-same:01M6JBYF2P3CFZAVQ7CFVQZXKF":70},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JBYF2P3CFZAVQ7CFVQZXKF","productized-service-business",null,"Validate, launch, and deliver productized service businesses, service-first SaaS wedges, managed marketplaces, and audit\u002Fretainer offers. Use when the user asks which business idea is worth doing, wants competitor or Dutch\u002FNL market validation, wants a monetization ladder, wants to validate a service before building software, or wants delivery SOPs\u002Ftemplates for a first paid client offer such as Review-to-Revenue \u002F Customer Voice Conversion Audits.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fclient\u002Fproductized-service-business\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"service","productized service business","business","as","customer","for","which","sops","nl","revenue","customer voice","software","saas","review","delivery","idea","conversion","use","audit","before building","2026-11-10 10:12:30",false,"---\nname: productized-service-business\ndescription: Validate, launch, and deliver productized service businesses, service-first SaaS wedges, managed marketplaces, and audit\u002Fretainer offers. Use when the user asks which business idea is worth doing, wants competitor or Dutch\u002FNL market validation, wants a monetization ladder, wants to validate a service before building software, or wants delivery SOPs\u002Ftemplates for a first paid client offer such as Review-to-Revenue \u002F Customer Voice Conversion Audits.\n---\n\n# Productized Service Business\n\nUse this class-level skill to move from raw idea → market verdict → first paid offer → repeatable delivery. Prefer service-first validation over building SaaS until paid demand is proven.\n\n## Default workflow\n\n1. **Define the paid proposition before researching**\n   - Who pays?\n   - What painful job gets removed or improved?\n   - What exact deliverable is produced?\n   - What outcome is promised?\n   - What is the narrow first wedge?\n\n2. **Research competitors by category, not just exact names**\n   - Direct exact competitors.\n   - Adjacent service providers.\n   - Software\u002Ftools that solve part of the problem.\n   - Agencies\u002Fconsultants with broader overlap.\n   - Blogs\u002Fcontent that describe the method but do not sell it.\n   - Enterprise versions that are too heavy for the target customer.\n\n3. **Compare overlap with a fixed grid**\n   For each found party, check whether it uses the same primary input, targets the same buyer, delivers the same artifact, promises the same outcome, has similar pricing\u002Fproductization, and can expand into the wedge quickly.\n\n4. **Score attackability 1-10**\n   Judge pain intensity, buyer ability to pay, ease of first sale, competitor density, clarity of ROI, delivery simplicity, ability to productize into retainer\u002FMRR, and copy risk from tools\u002Fagencies.\n\n5. **Finish with the operator answer**\n   Always include: hard verdict, sharp positioning sentence, first paid offer, free entry wedge, upsell\u002Fretainer path, biggest risk, and next 3 actions.\n\n## Research lane\n\nLoad `exa-plus` for deep search when useful. If Exa fails because `EXA_API_KEY` is missing, continue with `web_search` + `web_extract` and mention the fallback. For Dutch checks, search both Dutch and English:\n\n- `Nederland [problem] automatisering [buyer]`\n- `site:.nl \"[exact phrase]\" \"[industry]\"`\n- `\"[method]\" \"webshop\" \"Nederland\"`\n- `\"[problem]\" \"AI\" \"conversie\" \"Nederland\"`\n- `[global competitor category] Netherlands [industry]`\n\nAbsence of exact keywords is not proof of uniqueness; adjacent categories count.\n\n## Service-first \u002F managed-marketplace pattern\n\nWhen the user asks for Airbnb\u002FUber-like ideas or simple people-to-people\u002Fservice marketplaces, use a concierge MVP rather than recommending broad marketplaces.\n\n- Avoid generic “Werkspot but with AI,” “Temper but better,” or broad leadgen\u002Fofferte sites.\n- Look for narrow wedges where AI\u002Fautomation improves intake, matching, trust, scheduling, pricing, payments, evidence photos, backup coverage, and follow-up.\n- Start with landing page + Tally\u002FTypeform + WhatsApp Business + Google Sheets\u002FAirtable + Mollie\u002FStripe\u002FTikkie.\n- Validate paid transactions manually before building software.\n- Prefer recurring\u002Fhigh-frequency demand: short-stay turnovers, VvE maintenance, landlord repairs, office services, event staffing, practical care relief, subscriptions\u002Fmemberships.\n- Use `references\u002Fservice-marketplace-ai-ideas-nl.md` for Dutch marketplace gaps, crowded categories, MVP stack, and current best bet.\n\n## Productized audit\u002Fretainer pattern\n\nWhen a validated wedge becomes client delivery, switch from research to SOP execution:\n\n1. **Intake only what is needed**: URL, data source links\u002Fexports, priority pages or assets, business priority.\n2. **Start with public data when safe**; do not block on perfect access if a free quick-win or sample audit can be produced.\n3. **Turn evidence into exact artifacts**: page copy, FAQ answers, trust blocks, priority fixes, scorecards, checklists, or implementation-ready recommendations.\n4. **Reject vague advice**. Replace “improve trust” \u002F “optimize copy” \u002F “make clearer” with exact text, exact placement, evidence, and expected impact.\n5. **Sell a ladder**: free quick win → paid audit → done-for-you fix → managed retainer.\n\n## Review-to-Revenue \u002F Customer Voice Conversion Audits\n\nUse this subsection when the business is Harry's Review-to-Revenue wedge or any client task that turns reviews\u002Fcustomer feedback into conversion fixes.\n\n### Positioning\n\nDo not position it as generic AI, CRO, review management, or a chatbot. Position as:\n\n> We turn customer reviews into concrete websitecopy, FAQ answers, trust blocks, and page fixes that reduce buyer doubt and improve conversion.\n\nBest first niche: Dutch webshops with 100+ reviews, products above roughly €30, visible product\u002Fcategory pages, and repeated doubt around sizing, quality, delivery, installation, compatibility, returns, or trust.\n\n### Delivery ladder\n\n1. **Free entry: 3 Review Revenue Leaks** — public review scan, 3 concrete leaks, each with review evidence → page problem → exact fix text.\n2. **Paid entry: Review-to-Revenue Audit** — analyze 100-300 reviews and key pages; deliver top buying reasons, objections, complaints, return risks, 10 website fixes, 5 copy blocks, 5 FAQ answers, 3 trust snippets, and a priority plan.\n3. **Upsell: Audit + Copy Fix** — implementation-ready copy for homepage, PDP, category, FAQ, checkout, return\u002Fshipping trust copy.\n4. **Retainer: Managed Customer Voice Agent** — monthly review monitoring, new complaint\u002Fcompetitor patterns, and copy\u002FFAQ update recommendations.\n\n### Review source order\n\n1. Client CSV\u002Fexport from review platform.\n2. Public review pages, copied or semi-automated.\n3. Official API\u002Ffeed if client provides access.\n4. Browser\u002Fscraping only if allowed and necessary.\n\nPlatform notes: Trustpilot public reviews\u002Fexport; WebwinkelKeur API ratings\u002Fproduct-review endpoints with client credentials; Kiyoh XML\u002FAPI\u002Ffeed with client access; Shopify\u002FJudge.me\u002FLoox exports through client admin\u002Fapp; Google Business official access is cleanest, public samples are enough for quick wins.\n\n### Labeling and page comparison\n\nTag meaningful reviews as buying reason, doubt\u002Fobjection, complaint\u002Ffriction, return risk, trust signal, missing product info, delivery\u002Fservice, sizing\u002Ffit\u002Fcompatibility, emotional trigger, competitor advantage, and FAQ candidate.\n\nCompare at minimum homepage hero\u002FUSP, main category page, 3-5 product pages, FAQ\u002Fhelp, shipping\u002Freturns, and cart\u002Fcheckout trust messaging if visible.\n\n### Bundled resources\n\n- `references\u002Freview-to-revenue-netherlands.md` — Dutch competitor-map and positioning notes.\n- `references\u002Freview-to-revenue-delivery-kit.md` — SOP notes, platform blockers, delivery standards.\n- `templates\u002Fquick-wins-template.md` — copyable 3 Review Revenue Leaks template.\n- `templates\u002Fpaid-audit-template.md` — copyable paid audit report structure.\n- `templates\u002Fclient-intake-message.md` — message to request client inputs.\n- `scripts\u002Freview_csv_helper.py` — local CSV preprocessing helper for review text.\n\n## Harry output style\n\nFor Harry, keep it caveman concise and direct: no academic report tone, no 20 vague options, use clear scores, say when a market is crowded, say when an idea only works with a narrower wedge, and prefer founder-led service validation over building SaaS first.\n\n## Common pitfalls\n\n- Do not confuse “nobody uses our name” with “no competition.” Category competitors matter.\n- Do not recommend broad automation bots as a first wedge unless the buyer pain is already narrow and paid.\n- Do not sell AI as the headline when the buyer cares about money, time, risk, or conversion.\n- Do not let a service become “we optimize everything for everyone.” Narrow the beachhead.\n- Do not overbuild. First sell an audit, pilot, or fixed-scope service; automate after proof.\n- Do not wait for perfect data exports. Public data is enough for quick wins and proof-of-work.\n","# Productized Service Business\n\nUse this class-level skill to move from raw idea → market verdict → first paid offer → repeatable delivery. Prefer service-first validation over building SaaS until paid demand is proven.\n\n## Default workflow\n\n1. **Define the paid proposition before researching**\n   - Who pays?\n   - What painful job gets removed or improved?\n   - What exact deliverable is produced?\n   - What outcome is promised?\n   - What is the narrow first wedge?\n\n2. **Research competitors by category, not just exact names**\n   - Direct exact competitors.\n   - Adjacent service providers.\n   - Software\u002Ftools that solve part of the problem.\n   - Agencies\u002Fconsultants with broader overlap.\n   - Blogs\u002Fcontent that describe the method but do not sell it.\n   - Enterprise versions that are too heavy for the target customer.\n\n3. **Compare overlap with a fixed grid**\n   For each found party, check whether it uses the same primary input, targets the same buyer, delivers the same artifact, promises the same outcome, has similar pricing\u002Fproductization, and can expand into the wedge quickly.\n\n4. **Score attackability 1-10**\n   Judge pain intensity, buyer ability to pay, ease of first sale, competitor density, clarity of ROI, delivery simplicity, ability to productize into retainer\u002FMRR, and copy risk from tools\u002Fagencies.\n\n5. **Finish with the operator answer**\n   Always include: hard verdict, sharp positioning sentence, first paid offer, free entry wedge, upsell\u002Fretainer path, biggest risk, and next 3 actions.\n\n## Research lane\n\nLoad `exa-plus` for deep search when useful. If Exa fails because `EXA_API_KEY` is missing, continue with `web_search` + `web_extract` and mention the fallback. For Dutch checks, search both Dutch and English:\n\n- `Nederland [problem] automatisering [buyer]`\n- `site:.nl \"[exact phrase]\" \"[industry]\"`\n- `\"[method]\" \"webshop\" \"Nederland\"`\n- `\"[problem]\" \"AI\" \"conversie\" \"Nederland\"`\n- `[global competitor category] Netherlands [industry]`\n\nAbsence of exact keywords is not proof of uniqueness; adjacent categories count.\n\n## Service-first \u002F managed-marketplace pattern\n\nWhen the user asks for Airbnb\u002FUber-like ideas or simple people-to-people\u002Fservice marketplaces, use a concierge MVP rather than recommending broad marketplaces.\n\n- Avoid generic “Werkspot but with AI,” “Temper but better,” or broad leadgen\u002Fofferte sites.\n- Look for narrow wedges where AI\u002Fautomation improves intake, matching, trust, scheduling, pricing, payments, evidence photos, backup coverage, and follow-up.\n- Start with landing page + Tally\u002FTypeform + WhatsApp Business + Google Sheets\u002FAirtable + Mollie\u002FStripe\u002FTikkie.\n- Validate paid transactions manually before building software.\n- Prefer recurring\u002Fhigh-frequency demand: short-stay turnovers, VvE maintenance, landlord repairs, office services, event staffing, practical care relief, subscriptions\u002Fmemberships.\n- Use `references\u002Fservice-marketplace-ai-ideas-nl.md` for Dutch marketplace gaps, crowded categories, MVP stack, and current best bet.\n\n## Productized audit\u002Fretainer pattern\n\nWhen a validated wedge becomes client delivery, switch from research to SOP execution:\n\n1. **Intake only what is needed**: URL, data source links\u002Fexports, priority pages or assets, business priority.\n2. **Start with public data when safe**; do not block on perfect access if a free quick-win or sample audit can be produced.\n3. **Turn evidence into exact artifacts**: page copy, FAQ answers, trust blocks, priority fixes, scorecards, checklists, or implementation-ready recommendations.\n4. **Reject vague advice**. Replace “improve trust” \u002F “optimize copy” \u002F “make clearer” with exact text, exact placement, evidence, and expected impact.\n5. **Sell a ladder**: free quick win → paid audit → done-for-you fix → managed retainer.\n\n## Review-to-Revenue \u002F Customer Voice Conversion Audits\n\nUse this subsection when the business is Harry's Review-to-Revenue wedge or any client task that turns reviews\u002Fcustomer feedback into conversion fixes.\n\n### Positioning\n\nDo not position it as generic AI, CRO, review management, or a chatbot. Position as:\n\n> We turn customer reviews into concrete websitecopy, FAQ answers, trust blocks, and page fixes that reduce buyer doubt and improve conversion.\n\nBest first niche: Dutch webshops with 100+ reviews, products above roughly €30, visible product\u002Fcategory pages, and repeated doubt around sizing, quality, delivery, installation, compatibility, returns, or trust.\n\n### Delivery ladder\n\n1. **Free entry: 3 Review Revenue Leaks** — public review scan, 3 concrete leaks, each with review evidence → page problem → exact fix text.\n2. **Paid entry: Review-to-Revenue Audit** — analyze 100-300 reviews and key pages; deliver top buying reasons, objections, complaints, return risks, 10 website fixes, 5 copy blocks, 5 FAQ answers, 3 trust snippets, and a priority plan.\n3. **Upsell: Audit + Copy Fix** — implementation-ready copy for homepage, PDP, category, FAQ, checkout, return\u002Fshipping trust copy.\n4. **Retainer: Managed Customer Voice Agent** — monthly review monitoring, new complaint\u002Fcompetitor patterns, and copy\u002FFAQ update recommendations.\n\n### Review source order\n\n1. Client CSV\u002Fexport from review platform.\n2. Public review pages, copied or semi-automated.\n3. Official API\u002Ffeed if client provides access.\n4. Browser\u002Fscraping only if allowed and necessary.\n\nPlatform notes: Trustpilot public reviews\u002Fexport; WebwinkelKeur API ratings\u002Fproduct-review endpoints with client credentials; Kiyoh XML\u002FAPI\u002Ffeed with client access; Shopify\u002FJudge.me\u002FLoox exports through client admin\u002Fapp; Google Business official access is cleanest, public samples are enough for quick wins.\n\n### Labeling and page comparison\n\nTag meaningful reviews as buying reason, doubt\u002Fobjection, complaint\u002Ffriction, return risk, trust signal, missing product info, delivery\u002Fservice, sizing\u002Ffit\u002Fcompatibility, emotional trigger, competitor advantage, and FAQ candidate.\n\nCompare at minimum homepage hero\u002FUSP, main category page, 3-5 product pages, FAQ\u002Fhelp, shipping\u002Freturns, and cart\u002Fcheckout trust messaging if visible.\n\n### Bundled resources\n\n- `references\u002Freview-to-revenue-netherlands.md` — Dutch competitor-map and positioning notes.\n- `references\u002Freview-to-revenue-delivery-kit.md` — SOP notes, platform blockers, delivery standards.\n- `templates\u002Fquick-wins-template.md` — copyable 3 Review Revenue Leaks template.\n- `templates\u002Fpaid-audit-template.md` — copyable paid audit report structure.\n- `templates\u002Fclient-intake-message.md` — message to request client inputs.\n- `scripts\u002Freview_csv_helper.py` — local CSV preprocessing helper for review text.\n\n## Harry output style\n\nFor Harry, keep it caveman concise and direct: no academic report tone, no 20 vague options, use clear scores, say when a market is crowded, say when an idea only works with a narrower wedge, and prefer founder-led service validation over building SaaS first.\n\n## Common pitfalls\n\n- Do not confuse “nobody uses our name” with “no competition.” Category competitors matter.\n- Do not recommend broad automation bots as a first wedge unless the buyer pain is already narrow and paid.\n- Do not sell AI as the headline when the buyer cares about money, time, risk, or conversion.\n- Do not let a service become “we optimize everything for everyone.” Narrow the beachhead.\n- Do not overbuild. First sell an audit, pilot, or fixed-scope service; automate after proof.\n- Do not wait for perfect data exports. Public data is enough for quick wins and proof-of-work.\n",{"name":5,"description":7},"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fclient\u002Fproductized-service-business",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add S3YED\u002Fappie-kit --skill productized-service-business",{"tool":62,"command":63},"bunx","bunx skills add S3YED\u002Fappie-kit --skill productized-service-business",{"tool":65,"command":66},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill productized-service-business","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fclient\u002Fproductized-service-business\u002FSKILL.md",true,[],[71,103,138,164,195,217],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":84,"publishedAt":43},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[77,80,83],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":81,"categoryName":82,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":117,"publishedAt":43},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":146,"publishedAt":43},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[144,145],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[119,147,123,148,149,150,125,151,152,153,154,155,156,157,158,159,160,161,162,163],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":174,"publishedAt":43},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[170,173],{"categoryNo":171,"categoryName":172,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":43},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[201],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[203,204,34,205,36,206,207,208,209,210,211,212,213,214,215,216,28],"workflows","quality","software quality workflows","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":230,"publishedAt":43},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[223,226,229],{"categoryNo":224,"categoryName":225,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":227,"categoryName":228,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[231,232,233,234,235,236,237,238,178,239,240,125,241,181,242,210,243,244,245,246],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]