[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NZMF5XRCM3MEX54YNRYNN":3,"skill-same:01M71NZMF5XRCM3MEX54YNRYNN":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M71NZMF5XRCM3MEX54YNRYNN","signup-flow-cro",null,"Use when optimizing signup, registration, account creation or trial activation flows to raise completion rates. Covers field minimization, value before commitment, social auth, step design and friction audits. For post-signup activation use onboarding-cro; for marketing pages use page-cro.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignup-flow-cro\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignup-flow-cro\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"signup","cro","signup flow cro","flow","use","pages","page","for","registration","value","activation","marketing","product","when","design","social","flows","auth","creation","account creation","2026-11-10 10:56:23",false,"---\nname: signup-flow-cro\ndescription: \"Use when optimizing signup, registration, account creation or trial activation flows to raise completion rates. Covers field minimization, value before commitment, social auth, step design and friction audits. For post-signup activation use onboarding-cro; for marketing pages use page-cro.\"\ntags: [\"marketing\",\"product\",\"design\",\"cro\",\"growth\"]\ntools: [\"monodesign_detect\"]\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Fsignup\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Signup Flow CRO\n\nYou are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, 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\nBefore providing recommendations, understand:\n\n1. **Flow Type**\n   - Free trial signup\n   - Freemium account creation\n   - Paid account creation\n   - Waitlist\u002Fearly access signup\n   - B2B vs B2C\n\n2. **Current State**\n   - How many steps\u002Fscreens?\n   - What fields are required?\n   - What's the current completion rate?\n   - Where do users drop off?\n\n3. **Business Constraints**\n   - What data is genuinely needed at signup?\n   - Are there compliance requirements?\n   - What happens immediately after signup?\n\n---\n\n## Core Principles\n\n### 1. Minimize Required Fields\nEvery field reduces conversion. For each field, ask:\n- Do we absolutely need this before they can use the product?\n- Can we collect this later through progressive profiling?\n- Can we infer this from other data?\n\n**Typical field priority:**\n- Essential: Email (or phone), Password\n- Often needed: Name\n- Usually deferrable: Company, Role, Team size, Phone, Address\n\n### 2. Show Value Before Asking for Commitment\n- What can you show\u002Fgive before requiring signup?\n- Can they experience the product before creating an account?\n- Reverse the order: value first, signup second\n\n### 3. Reduce Perceived Effort\n- Show progress if multi-step\n- Group related fields\n- Use smart defaults\n- Pre-fill when possible\n\n### 4. Remove Uncertainty\n- Clear expectations (\"Takes 30 seconds\")\n- Show what happens after signup\n- No surprises (hidden requirements, unexpected steps)\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field (no email confirmation field)\n- Inline validation for format\n- Check for common typos (gmial.com → gmail.com)\n- Clear error messages\n\n### Password Field\n- Show password toggle (eye icon)\n- Show requirements upfront, not after failure\n- Consider passphrase hints for strength\n- Update requirement indicators in real-time\n\n**Better password UX:**\n- Allow paste (don't disable)\n- Show strength meter instead of rigid rules\n- Consider passwordless options\n\n### Name Field\n- Single \"Full name\" field vs. First\u002FLast split (test this)\n- Only require if immediately used (personalization)\n- Consider making optional\n\n### Social Auth Options\n- Place prominently (often higher conversion than email)\n- Show most relevant options for your audience\n  - B2C: Google, Apple, Facebook\n  - B2B: Google, Microsoft, SSO\n- Clear visual separation from email signup\n- Consider \"Sign up with Google\" as primary\n\n### Phone Number\n- Defer unless essential (SMS verification, calling leads)\n- If required, explain why\n- Use proper input type with country code handling\n- Format as they type\n\n### Company\u002FOrganization\n- Defer if possible\n- Auto-suggest as they type\n- Infer from email domain when possible\n\n### Use Case \u002F Role Questions\n- Defer to onboarding if possible\n- If needed at signup, keep to one question\n- Use progressive disclosure (don't show all options at once)\n\n---\n\n## Single-Step vs. Multi-Step\n\n### Single-Step Works When:\n- 3 or fewer fields\n- Simple B2C products\n- High-intent visitors (from ads, waitlist)\n\n### Multi-Step Works When:\n- More than 3-4 fields needed\n- Complex B2B products needing segmentation\n- You need to collect different types of info\n\n### Multi-Step Best Practices\n- Show progress indicator\n- Lead with easy questions (name, email)\n- Put harder questions later (after psychological commitment)\n- Each step should feel completable in seconds\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n\n**Progressive commitment pattern:**\n1. Email only (lowest barrier)\n2. Password + name\n3. Customization questions (optional)\n\n---\n\n## Trust and Friction Reduction\n\n### At the Form Level\n- \"No credit card required\" (if true)\n- \"Free forever\" or \"14-day free trial\"\n- Privacy note: \"We'll never share your email\"\n- Security badges if relevant\n- Testimonial near signup form\n\n### Error Handling\n- Inline validation (not just on submit)\n- Specific error messages (\"Email already registered\" + recovery path)\n- Don't clear the form on error\n- Focus on the problem field\n\n### Microcopy\n- Placeholder text: Use for examples, not labels\n- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in\n- Help text: Only when needed, placed close to field\n\n---\n\n## Mobile Signup Optimization\n\n- Larger touch targets (44px+ height)\n- Appropriate keyboard types (email, tel, etc.)\n- Autofill support\n- Reduce typing (social auth, pre-fill)\n- Single column layout\n- Sticky CTA button\n- Test with actual devices\n\n---\n\n## Post-Submit Experience\n\n### Success State\n- Clear confirmation\n- Immediate next step\n- If email verification required:\n  - Explain what to do\n  - Easy resend option\n  - Check spam reminder\n  - Option to change email if wrong\n\n### Verification Flows\n- Consider delaying verification until necessary\n- Magic link as alternative to password\n- Let users explore while awaiting verification\n- Clear re-engagement if verification stalls\n\n---\n\n## Measurement\n\n### Key Metrics\n- Form start rate (landed → started filling)\n- Form completion rate (started → submitted)\n- Field-level drop-off (which fields lose people)\n- Time to complete\n- Error rate by field\n- Mobile vs. desktop completion\n\n### What to Track\n- Each field interaction (focus, blur, error)\n- Step progression in multi-step\n- Social auth vs. email signup ratio\n- Time between steps\n\n---\n\n## Output Format\n\n### Audit Findings\nFor each issue found:\n- **Issue**: What's wrong\n- **Impact**: Why it matters (with estimated impact if possible)\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Changes\nOrganized by:\n1. Quick wins (same-day fixes)\n2. High-impact changes (week-level effort)\n3. Test hypotheses (things to A\u002FB test)\n\n### Form Redesign (if requested)\n- Recommended field set with rationale\n- Field order\n- Copy for labels, placeholders, buttons, errors\n- Visual layout suggestions\n\n---\n\n## Common Signup Flow Patterns\n\n### B2B SaaS Trial\n1. Email + Password (or Google auth)\n2. Name + Company (optional: role)\n3. → Onboarding flow\n\n### B2C App\n1. Google\u002FApple auth OR Email\n2. → Product experience\n3. Profile completion later\n\n### Waitlist\u002FEarly Access\n1. Email only\n2. Optional: Role\u002Fuse case question\n3. → Waitlist confirmation\n\n### E-commerce Account\n1. Guest checkout as default\n2. Account creation optional post-purchase\n3. OR Social auth with single click\n\n---\n\n## Experiment Ideas\n\n### Form Design Experiments\n\n**Layout & Structure**\n- Single-step vs. multi-step signup flow\n- Multi-step with progress bar vs. without\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate signup page\n- Horizontal vs. vertical field alignment\n\n**Field Optimization**\n- Reduce to minimum fields (email + password only)\n- Add or remove phone number field\n- Single \"Name\" field vs. \"First\u002FLast\" split\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n\n**Authentication Options**\n- Add SSO options (Google, Microsoft, GitHub, LinkedIn)\n- SSO prominent vs. email form prominent\n- Test which SSO options resonate (varies by audience)\n- SSO-only vs. SSO + email option\n\n**Visual Design**\n- Test button colors and sizes for CTA prominence\n- Plain background vs. product-related visuals\n- Test form container styling (card vs. minimal)\n- Mobile-optimized layout testing\n\n---\n\n### Copy & Messaging Experiments\n\n**Headlines & CTAs**\n- Test headline variations above signup form\n- CTA button text: \"Create Account\" vs. \"Start Free Trial\" vs. \"Get Started\"\n- Add clarity around trial length in CTA\n- Test value proposition emphasis in form header\n\n**Microcopy**\n- Field labels: minimal vs. descriptive\n- Placeholder text optimization\n- Error message clarity and tone\n- Password requirement display (upfront vs. on error)\n\n**Trust Elements**\n- Add social proof next to signup form\n- Test trust badges near form (security, compliance)\n- Add \"No credit card required\" messaging\n- Include privacy assurance copy\n\n---\n\n### Trial & Commitment Experiments\n\n**Free Trial Variations**\n- Credit card required vs. not required for trial\n- Test trial length impact (7 vs. 14 vs. 30 days)\n- Freemium vs. free trial model\n- Trial with limited features vs. full access\n\n**Friction Points**\n- Email verification required vs. delayed vs. removed\n- Test CAPTCHA impact on completion\n- Terms acceptance checkbox vs. implicit acceptance\n- Phone verification for high-value accounts\n\n---\n\n### Post-Submit Experiments\n\n- Clear next steps messaging after signup\n- Instant product access vs. email confirmation first\n- Personalized welcome message based on signup data\n- Auto-login after signup vs. require login\n\n---\n\n## Task-Specific Questions\n\n1. What's your current signup completion rate?\n2. Do you have field-level analytics on drop-off?\n3. What data is absolutely required before they can use the product?\n4. Are there compliance or verification requirements?\n5. What happens immediately after signup?\n\n---\n\n## Related Skills\n\n- **onboarding**: For optimizing what happens after signup\n- **cro**: For non-signup forms (lead capture, contact)\n- **cro**: For the landing page leading to signup\n- **ab-testing**: For testing signup flow changes\n","# Signup Flow CRO\n\nYou are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, 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\nBefore providing recommendations, understand:\n\n1. **Flow Type**\n   - Free trial signup\n   - Freemium account creation\n   - Paid account creation\n   - Waitlist\u002Fearly access signup\n   - B2B vs B2C\n\n2. **Current State**\n   - How many steps\u002Fscreens?\n   - What fields are required?\n   - What's the current completion rate?\n   - Where do users drop off?\n\n3. **Business Constraints**\n   - What data is genuinely needed at signup?\n   - Are there compliance requirements?\n   - What happens immediately after signup?\n\n---\n\n## Core Principles\n\n### 1. Minimize Required Fields\nEvery field reduces conversion. For each field, ask:\n- Do we absolutely need this before they can use the product?\n- Can we collect this later through progressive profiling?\n- Can we infer this from other data?\n\n**Typical field priority:**\n- Essential: Email (or phone), Password\n- Often needed: Name\n- Usually deferrable: Company, Role, Team size, Phone, Address\n\n### 2. Show Value Before Asking for Commitment\n- What can you show\u002Fgive before requiring signup?\n- Can they experience the product before creating an account?\n- Reverse the order: value first, signup second\n\n### 3. Reduce Perceived Effort\n- Show progress if multi-step\n- Group related fields\n- Use smart defaults\n- Pre-fill when possible\n\n### 4. Remove Uncertainty\n- Clear expectations (\"Takes 30 seconds\")\n- Show what happens after signup\n- No surprises (hidden requirements, unexpected steps)\n\n---\n\n## Field-by-Field Optimization\n\n### Email Field\n- Single field (no email confirmation field)\n- Inline validation for format\n- Check for common typos (gmial.com → gmail.com)\n- Clear error messages\n\n### Password Field\n- Show password toggle (eye icon)\n- Show requirements upfront, not after failure\n- Consider passphrase hints for strength\n- Update requirement indicators in real-time\n\n**Better password UX:**\n- Allow paste (don't disable)\n- Show strength meter instead of rigid rules\n- Consider passwordless options\n\n### Name Field\n- Single \"Full name\" field vs. First\u002FLast split (test this)\n- Only require if immediately used (personalization)\n- Consider making optional\n\n### Social Auth Options\n- Place prominently (often higher conversion than email)\n- Show most relevant options for your audience\n  - B2C: Google, Apple, Facebook\n  - B2B: Google, Microsoft, SSO\n- Clear visual separation from email signup\n- Consider \"Sign up with Google\" as primary\n\n### Phone Number\n- Defer unless essential (SMS verification, calling leads)\n- If required, explain why\n- Use proper input type with country code handling\n- Format as they type\n\n### Company\u002FOrganization\n- Defer if possible\n- Auto-suggest as they type\n- Infer from email domain when possible\n\n### Use Case \u002F Role Questions\n- Defer to onboarding if possible\n- If needed at signup, keep to one question\n- Use progressive disclosure (don't show all options at once)\n\n---\n\n## Single-Step vs. Multi-Step\n\n### Single-Step Works When:\n- 3 or fewer fields\n- Simple B2C products\n- High-intent visitors (from ads, waitlist)\n\n### Multi-Step Works When:\n- More than 3-4 fields needed\n- Complex B2B products needing segmentation\n- You need to collect different types of info\n\n### Multi-Step Best Practices\n- Show progress indicator\n- Lead with easy questions (name, email)\n- Put harder questions later (after psychological commitment)\n- Each step should feel completable in seconds\n- Allow back navigation\n- Save progress (don't lose data on refresh)\n\n**Progressive commitment pattern:**\n1. Email only (lowest barrier)\n2. Password + name\n3. Customization questions (optional)\n\n---\n\n## Trust and Friction Reduction\n\n### At the Form Level\n- \"No credit card required\" (if true)\n- \"Free forever\" or \"14-day free trial\"\n- Privacy note: \"We'll never share your email\"\n- Security badges if relevant\n- Testimonial near signup form\n\n### Error Handling\n- Inline validation (not just on submit)\n- Specific error messages (\"Email already registered\" + recovery path)\n- Don't clear the form on error\n- Focus on the problem field\n\n### Microcopy\n- Placeholder text: Use for examples, not labels\n- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in\n- Help text: Only when needed, placed close to field\n\n---\n\n## Mobile Signup Optimization\n\n- Larger touch targets (44px+ height)\n- Appropriate keyboard types (email, tel, etc.)\n- Autofill support\n- Reduce typing (social auth, pre-fill)\n- Single column layout\n- Sticky CTA button\n- Test with actual devices\n\n---\n\n## Post-Submit Experience\n\n### Success State\n- Clear confirmation\n- Immediate next step\n- If email verification required:\n  - Explain what to do\n  - Easy resend option\n  - Check spam reminder\n  - Option to change email if wrong\n\n### Verification Flows\n- Consider delaying verification until necessary\n- Magic link as alternative to password\n- Let users explore while awaiting verification\n- Clear re-engagement if verification stalls\n\n---\n\n## Measurement\n\n### Key Metrics\n- Form start rate (landed → started filling)\n- Form completion rate (started → submitted)\n- Field-level drop-off (which fields lose people)\n- Time to complete\n- Error rate by field\n- Mobile vs. desktop completion\n\n### What to Track\n- Each field interaction (focus, blur, error)\n- Step progression in multi-step\n- Social auth vs. email signup ratio\n- Time between steps\n\n---\n\n## Output Format\n\n### Audit Findings\nFor each issue found:\n- **Issue**: What's wrong\n- **Impact**: Why it matters (with estimated impact if possible)\n- **Fix**: Specific recommendation\n- **Priority**: High\u002FMedium\u002FLow\n\n### Recommended Changes\nOrganized by:\n1. Quick wins (same-day fixes)\n2. High-impact changes (week-level effort)\n3. Test hypotheses (things to A\u002FB test)\n\n### Form Redesign (if requested)\n- Recommended field set with rationale\n- Field order\n- Copy for labels, placeholders, buttons, errors\n- Visual layout suggestions\n\n---\n\n## Common Signup Flow Patterns\n\n### B2B SaaS Trial\n1. Email + Password (or Google auth)\n2. Name + Company (optional: role)\n3. → Onboarding flow\n\n### B2C App\n1. Google\u002FApple auth OR Email\n2. → Product experience\n3. Profile completion later\n\n### Waitlist\u002FEarly Access\n1. Email only\n2. Optional: Role\u002Fuse case question\n3. → Waitlist confirmation\n\n### E-commerce Account\n1. Guest checkout as default\n2. Account creation optional post-purchase\n3. OR Social auth with single click\n\n---\n\n## Experiment Ideas\n\n### Form Design Experiments\n\n**Layout & Structure**\n- Single-step vs. multi-step signup flow\n- Multi-step with progress bar vs. without\n- 1-column vs. 2-column field layout\n- Form embedded on page vs. separate signup page\n- Horizontal vs. vertical field alignment\n\n**Field Optimization**\n- Reduce to minimum fields (email + password only)\n- Add or remove phone number field\n- Single \"Name\" field vs. \"First\u002FLast\" split\n- Add or remove company\u002Forganization field\n- Test required vs. optional field balance\n\n**Authentication Options**\n- Add SSO options (Google, Microsoft, GitHub, LinkedIn)\n- SSO prominent vs. email form prominent\n- Test which SSO options resonate (varies by audience)\n- SSO-only vs. SSO + email option\n\n**Visual Design**\n- Test button colors and sizes for CTA prominence\n- Plain background vs. product-related visuals\n- Test form container styling (card vs. minimal)\n- Mobile-optimized layout testing\n\n---\n\n### Copy & Messaging Experiments\n\n**Headlines & CTAs**\n- Test headline variations above signup form\n- CTA button text: \"Create Account\" vs. \"Start Free Trial\" vs. \"Get Started\"\n- Add clarity around trial length in CTA\n- Test value proposition emphasis in form header\n\n**Microcopy**\n- Field labels: minimal vs. descriptive\n- Placeholder text optimization\n- Error message clarity and tone\n- Password requirement display (upfront vs. on error)\n\n**Trust Elements**\n- Add social proof next to signup form\n- Test trust badges near form (security, compliance)\n- Add \"No credit card required\" messaging\n- Include privacy assurance copy\n\n---\n\n### Trial & Commitment Experiments\n\n**Free Trial Variations**\n- Credit card required vs. not required for trial\n- Test trial length impact (7 vs. 14 vs. 30 days)\n- Freemium vs. free trial model\n- Trial with limited features vs. full access\n\n**Friction Points**\n- Email verification required vs. delayed vs. removed\n- Test CAPTCHA impact on completion\n- Terms acceptance checkbox vs. implicit acceptance\n- Phone verification for high-value accounts\n\n---\n\n### Post-Submit Experiments\n\n- Clear next steps messaging after signup\n- Instant product access vs. email confirmation first\n- Personalized welcome message based on signup data\n- Auto-login after signup vs. require login\n\n---\n\n## Task-Specific Questions\n\n1. What's your current signup completion rate?\n2. Do you have field-level analytics on drop-off?\n3. What data is absolutely required before they can use the product?\n4. Are there compliance or verification requirements?\n5. What happens immediately after signup?\n\n---\n\n## Related Skills\n\n- **onboarding**: For optimizing what happens after signup\n- **cro**: For non-signup forms (lead capture, contact)\n- **cro**: For the landing page leading to signup\n- **ab-testing**: For testing signup flow changes\n",{"name":5,"tags":60,"tools":62,"source":64,"license":14,"description":7,"source_path":65,"source_commit":66},[46,47,49,36,61],"growth",[63],"monodesign_detect","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Fsignup","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignup-flow-cro",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add monoes\u002Fmonomind --skill signup-flow-cro",{"tool":82,"command":83},"bunx","bunx skills add monoes\u002Fmonomind --skill signup-flow-cro",{"tool":85,"command":86},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill signup-flow-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignup-flow-cro\u002FSKILL.md",true,[90],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,[96,124,154,180,204,231],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":123},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[104,105,106,107,108,109,49,110,111,112,113,114,115,116,117,118,119,120,121,122],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":137,"publishedAt":123},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":135,"categoryName":136,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[138,139,140,108,141,142,48,143,112,144,145,146,47,147,148,149,150,151,152,153],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":123},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理",[147,165,166,167,168,110,169,48,170,171,172,47,173,174,175,176,177,178,39,179],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":190,"publishedAt":123},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[187],{"categoryNo":188,"categoryName":189,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[112,147,191,192,42,193,110,39,48,194,195,196,197,172,198,199,200,201,202,203],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":216,"publishedAt":123},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[210,213],{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[217,218,219,220,42,221,222,223,224,111,225,226,227,112,115,198,228,229,230,200],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":123},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[237],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},[219,239,240,241,242,243,244,42,245,246,144,247,248,249,115,198,250,251,200,252],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]