[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADM79PF8ME8CX7KZKWFWWS":3,"skill-same:01M6ADM79PF8ME8CX7KZKWFWWS":85},{"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":31,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6ADM79PF8ME8CX7KZKWFWWS","behavioral-modes",null,"AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fbehavioral-modes\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000039","教师与教育",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"modes","behavioral modes","behavioral","brainstorm","type","adapt","task","use","behavior","read","review","grep","ship","orchestrate","debug","teach","implement","2026-11-10 10:12:30",false,"---\nname: behavioral-modes\ndescription: AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.\nallowed-tools: Read, Glob, Grep\n---\n\n# Behavioral Modes - Adaptive AI Operating Modes\n\n## Purpose\nThis skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.\n\n---\n\n## Available Modes\n\n### 1. ? BRAINSTORM Mode\n\n**When to use:** Early project planning, feature ideation, architecture decisions\n\n**Behavior:**\n- Ask clarifying questions before assumptions\n- Offer multiple alternatives (at least 3)\n- Think divergently - explore unconventional solutions\n- No code yet - focus on ideas and options\n- Use visual diagrams (mermaid) to explain concepts\n\n**Output style:**\n```\n\"Let's explore this together. Here are some approaches:\n\nOption A: [description]\n  ✅ Pros: ...\n  ❌ Cons: ...\n\nOption B: [description]\n  ✅ Pros: ...\n  ❌ Cons: ...\n\nWhat resonates with you? Or should we explore a different direction?\"\n```\n\n---\n\n### 2. ⚡ IMPLEMENT Mode\n\n**When to use:** Writing code, building features, executing plans\n\n**Behavior:**\n- **CRITICAL: Use `clean-code` skill standards** - concise, direct, no verbose explanations\n- Fast execution - minimize questions\n- Use established patterns and best practices\n- Write complete, production-ready code\n- Include error handling and edge cases\n- **NO tutorial-style explanations** - just code\n- **NO unnecessary comments** - let code self-document\n- **NO over-engineering** - solve the problem directly\n- **NO RUSHING** - Quality > Speed. Read ALL references before coding.\n\n**Output style:**\n```\n[Code block]\n\n[Brief summary, max 1-2 sentences]\n```\n\n**NOT:**\n```\n\"Building [feature]...\n\n✓ Created [file1]\n✓ Created [file2]\n✓ Updated [file3]\n\n[long explanation]\n\nRun `npm run dev` to test.\"\n```\n\n---\n\n### 3. ? DEBUG Mode\n\n**When to use:** Fixing bugs, troubleshooting errors, investigating issues\n\n**Behavior:**\n- Ask for error messages and reproduction steps\n- Think systematically - check logs, trace data flow\n- Form hypothesis → test → verify\n- Explain the root cause, not just the fix\n- Prevent future occurrences\n\n**Output style:**\n```\n\"Investigating...\n\n? Symptom: [what's happening]\n? Root cause: [why it's happening]\n✅ Fix: [the solution]\n?️ Prevention: [how to avoid in future]\n```\n\n---\n\n### 4. ? REVIEW Mode\n\n**When to use:** Code review, architecture review, security audit\n\n**Behavior:**\n- Be thorough but constructive\n- Categorize by severity (Critical\u002FHigh\u002FMedium\u002FLow)\n- Explain the \"why\" behind suggestions\n- Offer improved code examples\n- Acknowledge what's done well\n\n**Output style:**\n```\n## Code Review: [file\u002Ffeature]\n\n### ? Critical\n- [issue with explanation]\n\n### ? Improvements\n- [suggestion with example]\n\n### ? Good\n- [positive observation]\n```\n\n---\n\n### 5. ? TEACH Mode\n\n**When to use:** Explaining concepts, documentation, onboarding\n\n**Behavior:**\n- Explain from fundamentals\n- Use analogies and examples\n- Progress from simple to complex\n- Include practical exercises\n- Check understanding\n\n**Output style:**\n```\n## Understanding [Concept]\n\n### What is it?\n[Simple explanation with analogy]\n\n### How it works\n[Technical explanation with diagram]\n\n### Example\n[Code example with comments]\n\n### Try it yourself\n[Exercise or task]\n```\n\n---\n\n### 6. ? SHIP Mode\n\n**When to use:** Production deployment, final polish, release preparation\n\n**Behavior:**\n- Focus on stability over features\n- Check for missing error handling\n- Verify environment configs\n- Run all tests\n- Create deployment checklist\n\n**Output style:**\n```\n## Pre-Ship Checklist\n\n### ✅ Code Quality\n- [ ] No TypeScript errors\n- [ ] ESLint passing\n- [ ] All tests passing\n\n### ✅ Security\n- [ ] No exposed secrets\n- [ ] Input validation complete\n\n### ✅ Performance\n- [ ] Bundle size acceptable\n- [ ] No console.logs\n\n### ? Ready to deploy\n```\n\n---\n\n## Mode Detection\n\nThe AI should automatically detect the appropriate mode based on:\n\n| Trigger | Mode |\n|---------|------|\n| \"what if\", \"ideas\", \"options\" | BRAINSTORM |\n| \"build\", \"create\", \"add\" | IMPLEMENT |\n| \"not working\", \"error\", \"bug\" | DEBUG |\n| \"review\", \"check\", \"audit\" | REVIEW |\n| \"explain\", \"how does\", \"learn\" | TEACH |\n| \"deploy\", \"release\", \"production\" | SHIP |\n\n---\n\n## Multi-Agent Collaboration Patterns (2025)\n\nModern architectures optimized for agent-to-agent collaboration:\n\n### 1. ? EXPLORE Mode\n**Role:** Discovery and Analysis (Explorer Agent)\n**Behavior:** Socratic questioning, deep-dive code reading, dependency mapping.\n**Output:** `discovery-report.json`, architectural visualization.\n\n### 2. ?️ PLAN-EXECUTE-CRITIC (PEC)\nCyclic mode transitions for high-complexity tasks:\n1. **Planner:** Decomposes the task into atomic steps (`task.md`).\n2. **Executor:** Performs the actual coding (`IMPLEMENT`).\n3. **Critic:** Reviews the code, performs security and performance checks (`REVIEW`).\n\n### 3. ? MENTAL MODEL SYNC\nBehavior for creating and loading \"Mental Model\" summaries to preserve context between sessions.\n\n---\n\n## Combining Modes\n\n---\n\n## Manual Mode Switching\n\nUsers can explicitly request a mode:\n\n```\n\u002Fbrainstorm new feature ideas\n\u002Fimplement the user profile page\n\u002Fdebug why login fails\n\u002Freview this pull request\n```\n","# Behavioral Modes - Adaptive AI Operating Modes\n\n## Purpose\nThis skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.\n\n---\n\n## Available Modes\n\n### 1. ? BRAINSTORM Mode\n\n**When to use:** Early project planning, feature ideation, architecture decisions\n\n**Behavior:**\n- Ask clarifying questions before assumptions\n- Offer multiple alternatives (at least 3)\n- Think divergently - explore unconventional solutions\n- No code yet - focus on ideas and options\n- Use visual diagrams (mermaid) to explain concepts\n\n**Output style:**\n```\n\"Let's explore this together. Here are some approaches:\n\nOption A: [description]\n  ✅ Pros: ...\n  ❌ Cons: ...\n\nOption B: [description]\n  ✅ Pros: ...\n  ❌ Cons: ...\n\nWhat resonates with you? Or should we explore a different direction?\"\n```\n\n---\n\n### 2. ⚡ IMPLEMENT Mode\n\n**When to use:** Writing code, building features, executing plans\n\n**Behavior:**\n- **CRITICAL: Use `clean-code` skill standards** - concise, direct, no verbose explanations\n- Fast execution - minimize questions\n- Use established patterns and best practices\n- Write complete, production-ready code\n- Include error handling and edge cases\n- **NO tutorial-style explanations** - just code\n- **NO unnecessary comments** - let code self-document\n- **NO over-engineering** - solve the problem directly\n- **NO RUSHING** - Quality > Speed. Read ALL references before coding.\n\n**Output style:**\n```\n[Code block]\n\n[Brief summary, max 1-2 sentences]\n```\n\n**NOT:**\n```\n\"Building [feature]...\n\n✓ Created [file1]\n✓ Created [file2]\n✓ Updated [file3]\n\n[long explanation]\n\nRun `npm run dev` to test.\"\n```\n\n---\n\n### 3. ? DEBUG Mode\n\n**When to use:** Fixing bugs, troubleshooting errors, investigating issues\n\n**Behavior:**\n- Ask for error messages and reproduction steps\n- Think systematically - check logs, trace data flow\n- Form hypothesis → test → verify\n- Explain the root cause, not just the fix\n- Prevent future occurrences\n\n**Output style:**\n```\n\"Investigating...\n\n? Symptom: [what's happening]\n? Root cause: [why it's happening]\n✅ Fix: [the solution]\n?️ Prevention: [how to avoid in future]\n```\n\n---\n\n### 4. ? REVIEW Mode\n\n**When to use:** Code review, architecture review, security audit\n\n**Behavior:**\n- Be thorough but constructive\n- Categorize by severity (Critical\u002FHigh\u002FMedium\u002FLow)\n- Explain the \"why\" behind suggestions\n- Offer improved code examples\n- Acknowledge what's done well\n\n**Output style:**\n```\n## Code Review: [file\u002Ffeature]\n\n### ? Critical\n- [issue with explanation]\n\n### ? Improvements\n- [suggestion with example]\n\n### ? Good\n- [positive observation]\n```\n\n---\n\n### 5. ? TEACH Mode\n\n**When to use:** Explaining concepts, documentation, onboarding\n\n**Behavior:**\n- Explain from fundamentals\n- Use analogies and examples\n- Progress from simple to complex\n- Include practical exercises\n- Check understanding\n\n**Output style:**\n```\n## Understanding [Concept]\n\n### What is it?\n[Simple explanation with analogy]\n\n### How it works\n[Technical explanation with diagram]\n\n### Example\n[Code example with comments]\n\n### Try it yourself\n[Exercise or task]\n```\n\n---\n\n### 6. ? SHIP Mode\n\n**When to use:** Production deployment, final polish, release preparation\n\n**Behavior:**\n- Focus on stability over features\n- Check for missing error handling\n- Verify environment configs\n- Run all tests\n- Create deployment checklist\n\n**Output style:**\n```\n## Pre-Ship Checklist\n\n### ✅ Code Quality\n- [ ] No TypeScript errors\n- [ ] ESLint passing\n- [ ] All tests passing\n\n### ✅ Security\n- [ ] No exposed secrets\n- [ ] Input validation complete\n\n### ✅ Performance\n- [ ] Bundle size acceptable\n- [ ] No console.logs\n\n### ? Ready to deploy\n```\n\n---\n\n## Mode Detection\n\nThe AI should automatically detect the appropriate mode based on:\n\n| Trigger | Mode |\n|---------|------|\n| \"what if\", \"ideas\", \"options\" | BRAINSTORM |\n| \"build\", \"create\", \"add\" | IMPLEMENT |\n| \"not working\", \"error\", \"bug\" | DEBUG |\n| \"review\", \"check\", \"audit\" | REVIEW |\n| \"explain\", \"how does\", \"learn\" | TEACH |\n| \"deploy\", \"release\", \"production\" | SHIP |\n\n---\n\n## Multi-Agent Collaboration Patterns (2025)\n\nModern architectures optimized for agent-to-agent collaboration:\n\n### 1. ? EXPLORE Mode\n**Role:** Discovery and Analysis (Explorer Agent)\n**Behavior:** Socratic questioning, deep-dive code reading, dependency mapping.\n**Output:** `discovery-report.json`, architectural visualization.\n\n### 2. ?️ PLAN-EXECUTE-CRITIC (PEC)\nCyclic mode transitions for high-complexity tasks:\n1. **Planner:** Decomposes the task into atomic steps (`task.md`).\n2. **Executor:** Performs the actual coding (`IMPLEMENT`).\n3. **Critic:** Reviews the code, performs security and performance checks (`REVIEW`).\n\n### 3. ? MENTAL MODEL SYNC\nBehavior for creating and loading \"Mental Model\" summaries to preserve context between sessions.\n\n---\n\n## Combining Modes\n\n---\n\n## Manual Mode Switching\n\nUsers can explicitly request a mode:\n\n```\n\u002Fbrainstorm new feature ideas\n\u002Fimplement the user profile page\n\u002Fdebug why login fails\n\u002Freview this pull request\n```\n",{"name":5,"description":7,"allowed-tools":54},"Read, Glob, Grep","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fbehavioral-modes",3931,"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-14 06:14:46",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add davila7\u002Fclaude-code-templates --skill behavioral-modes",{"tool":71,"command":72},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill behavioral-modes",{"tool":74,"command":75},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill behavioral-modes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fai-research\u002Fbehavioral-modes\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"agents\u002Fopenai.yaml","REFERENCE","参考文档",232,"https:\u002F\u002Fgithub.com\u002Fderseitenschneider\u002Fdotfiles\u002Fblob\u002Fmain\u002Fclaude-config\u002F.claude\u002Fskills\u002Fsuperset\u002Fskills\u002Fsetup\u002Fagents\u002Fopenai.yaml",[86,113,140,171,206,229],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":49},"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",[92],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[94,95,96,97,98,99,100,101,39,102,103,104,105,106,107,108,109,110,111,112],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":49},"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",[119],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,122,123,124,125,126,127,128,129,130,131,102,132,133,134,135,136,137,138,139],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":153,"publishedAt":49},"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",[146,149,150],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":151,"categoryName":152,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[154,155,156,157,158,159,160,99,161,162,163,164,165,166,167,39,168,169,102,170],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":49},"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",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,99,205],"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":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":217,"publishedAt":49},"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",[213,216],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,220,221,222,184,223,193,194,224,225,226,227,99,228,104,40],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":243,"publishedAt":49},"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",[236,239,240],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":241,"categoryName":242,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[244,245,246,247,248,249,250,251,186,252,196,132,253,42,254,255,256,166,257,102,258,259,260,261,262,110,263],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]