[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FXB66PQJGXH631KTKMGSF5":3,"skill-same:01M6FXB66PQJGXH631KTKMGSF5":61},{"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":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6FXB66PQJGXH631KTKMGSF5","signup-flow-cro",null,"When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fsignup-flow-cro\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"flow","signup flow cro","cro","signup","user","use","friction","community","activation","registration","optimize","creation","account creation","flows","2026-11-10 10:12:30",false,"---\nname: signup-flow-cro\ndescription: \"When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \\\"signup conversions,\\\" \\\"registration friction,\\\" \\\"signup...\"\nrisk: unknown\nsource: community\n---\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\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: Always visible (not just placeholders)\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## Questions to Ask\n\nIf you need more context:\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-cro**: For optimizing what happens after signup\n- **form-cro**: For non-signup forms (lead capture, contact)\n- **page-cro**: For the landing page leading to signup\n- **ab-test-setup**: For testing signup flow changes\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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\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: Always visible (not just placeholders)\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## Questions to Ask\n\nIf you need more context:\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-cro**: For optimizing what happens after signup\n- **form-cro**: For non-signup forms (lead capture, contact)\n- **page-cro**: For the landing page leading to signup\n- **ab-test-setup**: For testing signup flow changes\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":38,"source":26,"description":7},"unknown","master","dff58085da947e81e8418c922055644bf0082b1b","other\u002Fsignup-flow-cro","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add reikiplanet\u002Fdaoskills --skill signup-flow-cro",{"tool":53,"command":54},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill signup-flow-cro",{"tool":56,"command":57},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill signup-flow-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fother\u002Fsignup-flow-cro\u002FSKILL.md",true,[],[62,88,100,114,134,157],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":33},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[69,70,71,72,73,74,26,75,76,77,78,79,80,81,82,83,84,85,86,87],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"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":33},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[95,96,86,97,98,26,76,77,78,72,99,73],"ar","vr ar","interaction","requirements","performance",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":33},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[102,107,108,109,110,111,26,24,78,112,113,72],"project scaffolding","From Scratch","tech","project","scaffolding","projects","applications",{"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":120,"publishedAt":33},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[121,122,123,124,125,26,126,127,128,129,24,130,131,132,133],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":33},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,26,78,72,149,73,150,151,152,153,154,155,156],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":33},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[164,165,166,167,168,169,170,171,154,24,172,173,174,26,175,176,177,151,178,179],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]