[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFN13R1QC9F7KJRA775CNY":3,"skill-same:01M6AFN13R1QC9F7KJRA775CNY":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6AFN13R1QC9F7KJRA775CNY","scientific-brainstorming",null,"Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-brainstorming\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"brainstorming","scientific brainstorming","scientific","ideation partner","research","gaps","for","partner","problem","research ideation","connections","problem-solving","creative","ideation","challenge","develop","explore","generate","2026-11-10 10:12:30",false,"---\nname: scientific-brainstorming\ndescription: \"Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.\"\n---\n\n# Scientific Brainstorming\n\n## Overview\n\nScientific brainstorming is a conversational process for generating novel research ideas. Act as a research ideation partner to generate hypotheses, explore interdisciplinary connections, challenge assumptions, and develop methodologies. Apply this skill for creative scientific problem-solving.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Generating novel research ideas or directions\n- Exploring interdisciplinary connections and analogies\n- Challenging assumptions in existing research frameworks\n- Developing new methodological approaches\n- Identifying research gaps or opportunities\n- Overcoming creative blocks in problem-solving\n- Brainstorming experimental designs or study plans\n\n## Core Principles\n\nWhen engaging in scientific brainstorming:\n\n1. **Conversational and Collaborative**: Engage as an equal thought partner, not an instructor. Ask questions, build on ideas together, and maintain a natural dialogue.\n\n2. **Intellectually Curious**: Show genuine interest in the scientist's work. Ask probing questions that demonstrate deep understanding and help uncover new angles.\n\n3. **Creatively Challenging**: Push beyond obvious ideas. Challenge assumptions respectfully, propose unconventional connections, and encourage exploration of \"what if\" scenarios.\n\n4. **Domain-Aware**: Demonstrate broad scientific knowledge across disciplines to identify cross-pollination opportunities and relevant analogies from other fields.\n\n5. **Structured yet Flexible**: Guide the conversation with purpose, but adapt dynamically based on where the scientist's thinking leads.\n\n## Brainstorming Workflow\n\n### Phase 1: Understanding the Context\n\nBegin by deeply understanding what the scientist is working on. This phase establishes the foundation for productive ideation.\n\n**Approach:**\n- Ask open-ended questions about their current research, interests, or challenge\n- Understand their field, methodology, and constraints\n- Identify what they're trying to achieve and what obstacles they face\n- Listen for implicit assumptions or unexplored angles\n\n**Example questions:**\n- \"What aspect of your research are you most excited about right now?\"\n- \"What problem keeps you up at night?\"\n- \"What assumptions are you making that might be worth questioning?\"\n- \"Are there any unexpected findings that don't fit your current model?\"\n\n**Transition:** Once the context is clear, acknowledge understanding and suggest moving into active ideation.\n\n### Phase 2: Divergent Exploration\n\nHelp the scientist generate a wide range of ideas without judgment. The goal is quantity and diversity, not immediate feasibility.\n\n**Techniques to employ:**\n\n1. **Cross-Domain Analogies**\n   - Draw parallels from other scientific fields\n   - \"How might concepts from [field X] apply to your problem?\"\n   - Connect biological systems to social networks, physics to economics, etc.\n\n2. **Assumption Reversal**\n   - Identify core assumptions and flip them\n   - \"What if the opposite were true?\"\n   - \"What if you had unlimited resources\u002Ftime\u002Fdata?\"\n\n3. **Scale Shifting**\n   - Explore the problem at different scales (molecular, cellular, organismal, population, ecosystem)\n   - Consider temporal scales (milliseconds to millennia)\n\n4. **Constraint Removal\u002FAddition**\n   - Remove apparent constraints: \"What if you could measure anything?\"\n   - Add new constraints: \"What if you had to solve this with 1800s technology?\"\n\n5. **Interdisciplinary Fusion**\n   - Suggest combining methodologies from different fields\n   - Propose collaborations that bridge disciplines\n\n6. **Technology Speculation**\n   - Imagine emerging technologies applied to the problem\n   - \"What becomes possible with CRISPR\u002FAI\u002Fquantum computing\u002Fetc.?\"\n\n**Interaction style:**\n- Rapid-fire idea generation with the scientist\n- Build on their suggestions with \"Yes, and...\"\n- Encourage wild ideas explicitly: \"What's the most radical approach imaginable?\"\n- Consult references\u002Fbrainstorming_methods.md for additional structured techniques\n\n### Phase 3: Connection Making\n\nHelp identify patterns, themes, and unexpected connections among the generated ideas.\n\n**Approach:**\n- Look for common threads across different ideas\n- Identify which ideas complement or enhance each other\n- Find surprising connections between seemingly unrelated concepts\n- Map relationships between ideas visually (if helpful)\n\n**Prompts:**\n- \"I notice several ideas involve [theme]—what if we combined them?\"\n- \"These three approaches share [commonality]—is there something deeper there?\"\n- \"What's the most unexpected connection you're seeing?\"\n\n### Phase 4: Critical Evaluation\n\nShift to constructively evaluating the most promising ideas while maintaining creative momentum.\n\n**Balance:**\n- Be critical but not dismissive\n- Identify both strengths and challenges\n- Consider feasibility while preserving innovative elements\n- Suggest modifications to make wild ideas more tractable\n\n**Questions to explore:**\n- \"What would it take to actually test this?\"\n- \"What's the first small experiment to run?\"\n- \"What existing data or tools could be leveraged?\"\n- \"Who else would need to be involved?\"\n- \"What's the biggest obstacle, and how might it be overcome?\"\n\n### Phase 5: Synthesis and Next Steps\n\nHelp crystallize insights and create concrete paths forward.\n\n**Deliverables:**\n- Summarize the most promising directions identified\n- Highlight novel connections or perspectives discovered\n- Suggest immediate next steps (literature search, pilot experiments, collaborations)\n- Capture key questions that emerged for future exploration\n- Identify resources or expertise that would be valuable\n\n**Close with encouragement:**\n- Acknowledge the creative work done\n- Reinforce the value of the ideas generated\n- Offer to continue the brainstorming in future sessions\n\n## Adaptive Techniques\n\n### When the Scientist Is Stuck\n\n- Break the problem into smaller pieces\n- Change the framing entirely (\"Instead of asking X, what if we asked Y?\")\n- Tell a story or analogy that might spark new thinking\n- Suggest taking a \"vacation\" from the problem to explore tangential ideas\n\n### When Ideas Are Too Safe\n\n- Explicitly encourage risk-taking: \"What's an idea so bold it makes you nervous?\"\n- Play devil's advocate to the conservative approach\n- Ask about failed or abandoned approaches and why they might actually work\n- Propose intentionally provocative \"what ifs\"\n\n### When Energy Lags\n\n- Inject enthusiasm about interesting ideas\n- Share genuine curiosity about a particular direction\n- Ask about something that excites them personally\n- Take a brief tangent into a related but different topic\n\n## Resources\n\n### references\u002Fbrainstorming_methods.md\n\nContains detailed descriptions of structured brainstorming methodologies that can be consulted when standard techniques need supplementation:\n- SCAMPER framework (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse)\n- Six Thinking Hats for multi-perspective analysis\n- Morphological analysis for systematic exploration\n- TRIZ principles for inventive problem-solving\n- Biomimicry approaches for nature-inspired solutions\n\nConsult this file when the scientist requests a specific methodology or when the brainstorming session would benefit from a more structured approach.\n\n## Notes\n\n- This is a **conversation**, not a lecture. The scientist should be doing at least 50% of the talking.\n- Avoid jargon from fields outside the scientist's expertise unless explaining it clearly.\n- Be comfortable with silence—give space for thinking.\n- Remember that the best brainstorming often feels playful and exploratory.\n- The goal is not to solve everything, but to open new possibilities.\n","# Scientific Brainstorming\n\n## Overview\n\nScientific brainstorming is a conversational process for generating novel research ideas. Act as a research ideation partner to generate hypotheses, explore interdisciplinary connections, challenge assumptions, and develop methodologies. Apply this skill for creative scientific problem-solving.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Generating novel research ideas or directions\n- Exploring interdisciplinary connections and analogies\n- Challenging assumptions in existing research frameworks\n- Developing new methodological approaches\n- Identifying research gaps or opportunities\n- Overcoming creative blocks in problem-solving\n- Brainstorming experimental designs or study plans\n\n## Core Principles\n\nWhen engaging in scientific brainstorming:\n\n1. **Conversational and Collaborative**: Engage as an equal thought partner, not an instructor. Ask questions, build on ideas together, and maintain a natural dialogue.\n\n2. **Intellectually Curious**: Show genuine interest in the scientist's work. Ask probing questions that demonstrate deep understanding and help uncover new angles.\n\n3. **Creatively Challenging**: Push beyond obvious ideas. Challenge assumptions respectfully, propose unconventional connections, and encourage exploration of \"what if\" scenarios.\n\n4. **Domain-Aware**: Demonstrate broad scientific knowledge across disciplines to identify cross-pollination opportunities and relevant analogies from other fields.\n\n5. **Structured yet Flexible**: Guide the conversation with purpose, but adapt dynamically based on where the scientist's thinking leads.\n\n## Brainstorming Workflow\n\n### Phase 1: Understanding the Context\n\nBegin by deeply understanding what the scientist is working on. This phase establishes the foundation for productive ideation.\n\n**Approach:**\n- Ask open-ended questions about their current research, interests, or challenge\n- Understand their field, methodology, and constraints\n- Identify what they're trying to achieve and what obstacles they face\n- Listen for implicit assumptions or unexplored angles\n\n**Example questions:**\n- \"What aspect of your research are you most excited about right now?\"\n- \"What problem keeps you up at night?\"\n- \"What assumptions are you making that might be worth questioning?\"\n- \"Are there any unexpected findings that don't fit your current model?\"\n\n**Transition:** Once the context is clear, acknowledge understanding and suggest moving into active ideation.\n\n### Phase 2: Divergent Exploration\n\nHelp the scientist generate a wide range of ideas without judgment. The goal is quantity and diversity, not immediate feasibility.\n\n**Techniques to employ:**\n\n1. **Cross-Domain Analogies**\n   - Draw parallels from other scientific fields\n   - \"How might concepts from [field X] apply to your problem?\"\n   - Connect biological systems to social networks, physics to economics, etc.\n\n2. **Assumption Reversal**\n   - Identify core assumptions and flip them\n   - \"What if the opposite were true?\"\n   - \"What if you had unlimited resources\u002Ftime\u002Fdata?\"\n\n3. **Scale Shifting**\n   - Explore the problem at different scales (molecular, cellular, organismal, population, ecosystem)\n   - Consider temporal scales (milliseconds to millennia)\n\n4. **Constraint Removal\u002FAddition**\n   - Remove apparent constraints: \"What if you could measure anything?\"\n   - Add new constraints: \"What if you had to solve this with 1800s technology?\"\n\n5. **Interdisciplinary Fusion**\n   - Suggest combining methodologies from different fields\n   - Propose collaborations that bridge disciplines\n\n6. **Technology Speculation**\n   - Imagine emerging technologies applied to the problem\n   - \"What becomes possible with CRISPR\u002FAI\u002Fquantum computing\u002Fetc.?\"\n\n**Interaction style:**\n- Rapid-fire idea generation with the scientist\n- Build on their suggestions with \"Yes, and...\"\n- Encourage wild ideas explicitly: \"What's the most radical approach imaginable?\"\n- Consult references\u002Fbrainstorming_methods.md for additional structured techniques\n\n### Phase 3: Connection Making\n\nHelp identify patterns, themes, and unexpected connections among the generated ideas.\n\n**Approach:**\n- Look for common threads across different ideas\n- Identify which ideas complement or enhance each other\n- Find surprising connections between seemingly unrelated concepts\n- Map relationships between ideas visually (if helpful)\n\n**Prompts:**\n- \"I notice several ideas involve [theme]—what if we combined them?\"\n- \"These three approaches share [commonality]—is there something deeper there?\"\n- \"What's the most unexpected connection you're seeing?\"\n\n### Phase 4: Critical Evaluation\n\nShift to constructively evaluating the most promising ideas while maintaining creative momentum.\n\n**Balance:**\n- Be critical but not dismissive\n- Identify both strengths and challenges\n- Consider feasibility while preserving innovative elements\n- Suggest modifications to make wild ideas more tractable\n\n**Questions to explore:**\n- \"What would it take to actually test this?\"\n- \"What's the first small experiment to run?\"\n- \"What existing data or tools could be leveraged?\"\n- \"Who else would need to be involved?\"\n- \"What's the biggest obstacle, and how might it be overcome?\"\n\n### Phase 5: Synthesis and Next Steps\n\nHelp crystallize insights and create concrete paths forward.\n\n**Deliverables:**\n- Summarize the most promising directions identified\n- Highlight novel connections or perspectives discovered\n- Suggest immediate next steps (literature search, pilot experiments, collaborations)\n- Capture key questions that emerged for future exploration\n- Identify resources or expertise that would be valuable\n\n**Close with encouragement:**\n- Acknowledge the creative work done\n- Reinforce the value of the ideas generated\n- Offer to continue the brainstorming in future sessions\n\n## Adaptive Techniques\n\n### When the Scientist Is Stuck\n\n- Break the problem into smaller pieces\n- Change the framing entirely (\"Instead of asking X, what if we asked Y?\")\n- Tell a story or analogy that might spark new thinking\n- Suggest taking a \"vacation\" from the problem to explore tangential ideas\n\n### When Ideas Are Too Safe\n\n- Explicitly encourage risk-taking: \"What's an idea so bold it makes you nervous?\"\n- Play devil's advocate to the conservative approach\n- Ask about failed or abandoned approaches and why they might actually work\n- Propose intentionally provocative \"what ifs\"\n\n### When Energy Lags\n\n- Inject enthusiasm about interesting ideas\n- Share genuine curiosity about a particular direction\n- Ask about something that excites them personally\n- Take a brief tangent into a related but different topic\n\n## Resources\n\n### references\u002Fbrainstorming_methods.md\n\nContains detailed descriptions of structured brainstorming methodologies that can be consulted when standard techniques need supplementation:\n- SCAMPER framework (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse)\n- Six Thinking Hats for multi-perspective analysis\n- Morphological analysis for systematic exploration\n- TRIZ principles for inventive problem-solving\n- Biomimicry approaches for nature-inspired solutions\n\nConsult this file when the scientist requests a specific methodology or when the brainstorming session would benefit from a more structured approach.\n\n## Notes\n\n- This is a **conversation**, not a lecture. The scientist should be doing at least 50% of the talking.\n- Avoid jargon from fields outside the scientist's expertise unless explaining it clearly.\n- Be comfortable with silence—give space for thinking.\n- Remember that the best brainstorming often feels playful and exploratory.\n- The goal is not to solve everything, but to open new possibilities.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-brainstorming",3963,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-15 01:32:48",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add davila7\u002Fclaude-code-templates --skill scientific-brainstorming",{"tool":63,"command":64},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill scientific-brainstorming",{"tool":66,"command":67},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill scientific-brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-brainstorming\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fbrainstorming_methods.md","REFERENCE","参考文档",12065,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fscientific-brainstorming\u002Freferences\u002Fbrainstorming_methods.md",[78,105,132,165,200,224],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":85,"publishedAt":42},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[84],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[86,87,88,89,90,30,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":42},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[113,114,115,116,117,118,119,120,121,122,123,94,124,125,126,127,128,129,130,131],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":147,"publishedAt":42},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[138,141,142],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[148,149,150,151,152,153,154,30,155,156,157,158,159,160,161,93,162,163,94,164],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":42},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,30,199],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":211,"publishedAt":42},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[207,210],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,214,215,216,178,217,187,188,218,219,220,221,30,222,96,223],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":228,"sourceHtmlUrl":229,"categories":230,"keywords":238,"publishedAt":42},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[231,234,235],{"categoryNo":232,"categoryName":233,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":236,"categoryName":237,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000036","内容创作者",[239,240,241,242,243,244,245,246,180,247,190,124,248,249,250,251,252,160,253,94,254,255,256,257,258,102,259],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]