[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6VBWN9GGXX7A4CPRXD75J6T":3,"skill-same:01M6VBWN9GGXX7A4CPRXD75J6T":77},{"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":25,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6VBWN9GGXX7A4CPRXD75J6T","search-first",null,"Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fsearch-first\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"search","first","search first","writing","research","workflow","libraries","code","Tools","coding","researcher","patterns","coding workflow","for","Existing","custom","2026-11-10 10:12:30",false,"---\nversion: 1.0.0\nname: brainstorming\ndescription: Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.\nallowed-tools: Read, Glob, Grep\n---\n\n# Brainstorming & Communication Protocol\n\n> **MANDATORY:** Use for complex\u002Fvague requests, new features, updates.\n\n---\n\n## ? SOCRATIC GATE (ENFORCEMENT)\n\n### When to Trigger\n\n| Pattern | Action |\n|---------|--------|\n| \"Build\u002FCreate\u002FMake [thing]\" without details | ? ASK 3 questions |\n| Complex feature or architecture | ? Clarify before implementing |\n| Update\u002Fchange request | ? Confirm scope |\n| Vague requirements | ? Ask purpose, users, constraints |\n\n### ? MANDATORY: 3 Questions Before Implementation\n\n1. **STOP** - Do NOT start coding\n2. **ASK** - Minimum 3 questions:\n   - ? Purpose: What problem are you solving?\n   - ? Users: Who will use this?\n   - ? Scope: Must-have vs nice-to-have?\n3. **WAIT** - Get response before proceeding\n\n---\n\n## ? Dynamic Question Generation\n\n**⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles.\n\n### Core Principles\n\n| Principle | Meaning |\n|-----------|---------|\n| **Questions Reveal Consequences** | Each question connects to an architectural decision |\n| **Context Before Content** | Understand greenfield\u002Ffeature\u002Frefactor\u002Fdebug context first |\n| **Minimum Viable Questions** | Each question must eliminate implementation paths |\n| **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs |\n\n### Question Generation Process\n\n```\n1. Parse request → Extract domain, features, scale indicators\n2. Identify decision points → Blocking vs. deferable\n3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)\n4. Format with trade-offs → What, Why, Options, Default\n```\n\n### Question Format (MANDATORY)\n\n```markdown\n### [PRIORITY] **[DECISION POINT]**\n\n**Question:** [Clear question]\n\n**Why This Matters:**\n- [Architectural consequence]\n- [Affects: cost\u002Fcomplexity\u002Ftimeline\u002Fscale]\n\n**Options:**\n| Option | Pros | Cons | Best For |\n|--------|------|------|----------|\n| A | [+] | [-] | [Use case] |\n\n**If Not Specified:** [Default + rationale]\n```\n\n**For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md`\n\n---\n\n## Progress Reporting (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Transparency builds trust. Status must be visible and actionable.\n\n### Status Board Format\n\n| Agent | Status | Current Task | Progress |\n|-------|--------|--------------|----------|\n| [Agent Name] | ✅?⏳❌⚠️ | [Task description] | [% or count] |\n\n### Status Icons\n\n| Icon | Meaning | Usage |\n|------|---------|-------|\n| ✅ | Completed | Task finished successfully |\n| ? | Running | Currently executing |\n| ⏳ | Waiting | Blocked, waiting for dependency |\n| ❌ | Error | Failed, needs attention |\n| ⚠️ | Warning | Potential issue, not blocking |\n\n---\n\n## Error Handling (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Errors are opportunities for clear communication.\n\n### Error Response Pattern\n\n```\n1. Acknowledge the error\n2. Explain what happened (user-friendly)\n3. Offer specific solutions with trade-offs\n4. Ask user to choose or provide alternative\n```\n\n### Error Categories\n\n| Category | Response Strategy |\n|----------|-------------------|\n| **Port Conflict** | Offer alternative port or close existing |\n| **Dependency Missing** | Auto-install or ask permission |\n| **Build Failure** | Show specific error + suggested fix |\n| **Unclear Error** | Ask for specifics: screenshot, console output |\n\n---\n\n## Completion Message (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Celebrate success, guide next steps.\n\n### Completion Structure\n\n```\n1. Success confirmation (celebrate briefly)\n2. Summary of what was done (concrete)\n3. How to verify\u002Ftest (actionable)\n4. Next steps suggestion (proactive)\n```\n\n---\n\n## Communication Principles\n\n| Principle | Implementation |\n|-----------|----------------|\n| **Concise** | No unnecessary details, get to point |\n| **Visual** | Use emojis (✅?⏳❌) for quick scanning |\n| **Specific** | \"~2 minutes\" not \"wait a bit\" |\n| **Alternatives** | Offer multiple paths when stuck |\n| **Proactive** | Suggest next step after completion |\n\n---\n\n## Anti-Patterns (AVOID)\n\n| Anti-Pattern | Why |\n|--------------|-----|\n| Jumping to solutions before understanding | Wastes time on wrong problem |\n| Assuming requirements without asking | Creates wrong output |\n| Over-engineering first version | Delays value delivery |\n| Ignoring constraints | Creates unusable solutions |\n| \"I think\" phrases | Uncertainty → Ask instead |\n\n---\n","# Brainstorming & Communication Protocol\n\n> **MANDATORY:** Use for complex\u002Fvague requests, new features, updates.\n\n---\n\n## ? SOCRATIC GATE (ENFORCEMENT)\n\n### When to Trigger\n\n| Pattern | Action |\n|---------|--------|\n| \"Build\u002FCreate\u002FMake [thing]\" without details | ? ASK 3 questions |\n| Complex feature or architecture | ? Clarify before implementing |\n| Update\u002Fchange request | ? Confirm scope |\n| Vague requirements | ? Ask purpose, users, constraints |\n\n### ? MANDATORY: 3 Questions Before Implementation\n\n1. **STOP** - Do NOT start coding\n2. **ASK** - Minimum 3 questions:\n   - ? Purpose: What problem are you solving?\n   - ? Users: Who will use this?\n   - ? Scope: Must-have vs nice-to-have?\n3. **WAIT** - Get response before proceeding\n\n---\n\n## ? Dynamic Question Generation\n\n**⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles.\n\n### Core Principles\n\n| Principle | Meaning |\n|-----------|---------|\n| **Questions Reveal Consequences** | Each question connects to an architectural decision |\n| **Context Before Content** | Understand greenfield\u002Ffeature\u002Frefactor\u002Fdebug context first |\n| **Minimum Viable Questions** | Each question must eliminate implementation paths |\n| **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs |\n\n### Question Generation Process\n\n```\n1. Parse request → Extract domain, features, scale indicators\n2. Identify decision points → Blocking vs. deferable\n3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)\n4. Format with trade-offs → What, Why, Options, Default\n```\n\n### Question Format (MANDATORY)\n\n```markdown\n### [PRIORITY] **[DECISION POINT]**\n\n**Question:** [Clear question]\n\n**Why This Matters:**\n- [Architectural consequence]\n- [Affects: cost\u002Fcomplexity\u002Ftimeline\u002Fscale]\n\n**Options:**\n| Option | Pros | Cons | Best For |\n|--------|------|------|----------|\n| A | [+] | [-] | [Use case] |\n\n**If Not Specified:** [Default + rationale]\n```\n\n**For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md`\n\n---\n\n## Progress Reporting (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Transparency builds trust. Status must be visible and actionable.\n\n### Status Board Format\n\n| Agent | Status | Current Task | Progress |\n|-------|--------|--------------|----------|\n| [Agent Name] | ✅?⏳❌⚠️ | [Task description] | [% or count] |\n\n### Status Icons\n\n| Icon | Meaning | Usage |\n|------|---------|-------|\n| ✅ | Completed | Task finished successfully |\n| ? | Running | Currently executing |\n| ⏳ | Waiting | Blocked, waiting for dependency |\n| ❌ | Error | Failed, needs attention |\n| ⚠️ | Warning | Potential issue, not blocking |\n\n---\n\n## Error Handling (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Errors are opportunities for clear communication.\n\n### Error Response Pattern\n\n```\n1. Acknowledge the error\n2. Explain what happened (user-friendly)\n3. Offer specific solutions with trade-offs\n4. Ask user to choose or provide alternative\n```\n\n### Error Categories\n\n| Category | Response Strategy |\n|----------|-------------------|\n| **Port Conflict** | Offer alternative port or close existing |\n| **Dependency Missing** | Auto-install or ask permission |\n| **Build Failure** | Show specific error + suggested fix |\n| **Unclear Error** | Ask for specifics: screenshot, console output |\n\n---\n\n## Completion Message (PRINCIPLE-BASED)\n\n**PRINCIPLE:** Celebrate success, guide next steps.\n\n### Completion Structure\n\n```\n1. Success confirmation (celebrate briefly)\n2. Summary of what was done (concrete)\n3. How to verify\u002Ftest (actionable)\n4. Next steps suggestion (proactive)\n```\n\n---\n\n## Communication Principles\n\n| Principle | Implementation |\n|-----------|----------------|\n| **Concise** | No unnecessary details, get to point |\n| **Visual** | Use emojis (✅?⏳❌) for quick scanning |\n| **Specific** | \"~2 minutes\" not \"wait a bit\" |\n| **Alternatives** | Offer multiple paths when stuck |\n| **Proactive** | Suggest next step after completion |\n\n---\n\n## Anti-Patterns (AVOID)\n\n| Anti-Pattern | Why |\n|--------------|-----|\n| Jumping to solutions before understanding | Wastes time on wrong problem |\n| Assuming requirements without asking | Creates wrong output |\n| Over-engineering first version | Delays value delivery |\n| Ignoring constraints | Creates unusable solutions |\n| \"I think\" phrases | Uncertainty → Ask instead |\n\n---\n",{"name":47,"version":48,"description":49,"allowed-tools":50},"brainstorming","1.0.0","Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.","Read, Glob, Grep","main","faeb6bdc81708c17c61365f976c221d9bb89928a",".claude\u002Fskills\u002Fecc\u002Fsearch-first","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":47,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill brainstorming",{"tool":63,"command":64},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill brainstorming",{"tool":66,"command":67},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fsearch-first\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"dynamic-questioning.md","REFERENCE","参考文档",11619,"https:\u002F\u002Fgithub.com\u002Fjonnathan-ls\u002Fai-context-kit\u002Fblob\u002Fmain\u002Fskills\u002Fbrainstorming\u002Fdynamic-questioning.md",[78,110,118,137,154,182],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":90,"publishedAt":42},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[84,87],{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,39],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":42},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[116,117],"hotcook recipes","recipes",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":132,"publishedAt":42},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[124,127],{"categoryNo":125,"categoryName":126,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[133,134,33,135,136],"code helper","helper","code review","review",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":42},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[143,144],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[146,30,147,148,149,26,150,151,152,153],"research assistant","assistant","MCP","web","brave search","web research","brave","web research assistant",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":42},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},[165,166,167,168,169,170,39,171,172,173,174,175,37,176,177,178,179,180,26,181],"x api","api","with","when","limits","rate","threads","reading","native","posting","platform","api integration","twitter","use","auth","analytics","OAuth",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":42},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[188],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[190,191,192,193,148,194,195,33,196,197,198,199,178,200,201,202,203,173,204,168],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]