[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM0903MBG1K2HVCKBAF8VN":3,"skill-same:01M7CM0903MBG1K2HVCKBAF8VN":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7CM0903MBG1K2HVCKBAF8VN","behavioral-modes",null,"AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.","haliltek\u002Fdev.tr","haliltek","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31656259?v=4","01M7CKZCVHYRZ5CFNDBMFT5S7Q","Halil TEK","01M7CKZCWH3RX91D93NHE4DP2J",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbehavioral-modes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: behavioral-modes\ndescription: AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.\nwhen_to_use: \"When adapting AI behavior for specific task types: brainstorm, implement, debug, review, teach, ship, or orchestrate modes.\"\nallowed-tools: Read, Glob, Grep\nversion: 1.0.0\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\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\nModes are not exclusive — most real tasks chain several in sequence:\n\n| Flow | Mode Chain |\n|------|------------|\n| New feature | BRAINSTORM → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW → SHIP |\n| Bug fix | EXPLORE → DEBUG → IMPLEMENT → REVIEW |\n| Unfamiliar codebase | EXPLORE → TEACH → BRAINSTORM |\n| Risky refactor | EXPLORE → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW |\n\nSwitch modes when the work changes shape (e.g. drop from IMPLEMENT to DEBUG the moment a test fails), and carry context forward with MENTAL MODEL SYNC across long sessions.\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\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\nModes are not exclusive — most real tasks chain several in sequence:\n\n| Flow | Mode Chain |\n|------|------------|\n| New feature | BRAINSTORM → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW → SHIP |\n| Bug fix | EXPLORE → DEBUG → IMPLEMENT → REVIEW |\n| Unfamiliar codebase | EXPLORE → TEACH → BRAINSTORM |\n| Risky refactor | EXPLORE → PLAN-EXECUTE-CRITIC → IMPLEMENT → REVIEW |\n\nSwitch modes when the work changes shape (e.g. drop from IMPLEMENT to DEBUG the moment a test fails), and carry context forward with MENTAL MODEL SYNC across long sessions.\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,"version":24,"description":7,"when_to_use":25,"allowed-tools":26},"1.0.0","When adapting AI behavior for specific task types: brainstorm, implement, debug, review, teach, ship, or orchestrate modes.","Read, Glob, Grep","main","35fc33da79b31d7f8dadfc704083baff1b5672a0",".agents\u002Fskills\u002Fbehavioral-modes","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr","https:\u002F\u002Fgithub.com\u002Fhaliltek","2026-11-13 01:38:48",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add haliltek\u002Fdev.tr --skill behavioral-modes",{"tool":39,"command":40},"bunx","bunx skills add haliltek\u002Fdev.tr --skill behavioral-modes",{"tool":42,"command":43},"pnpm","pnpm dlx skills add haliltek\u002Fdev.tr --skill behavioral-modes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbehavioral-modes\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CM8JAC0X6HVS8VCHH51KPZ","respectfully","Wraps any prompt with a reminder to respect CLAUDE.md files","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frespectfully\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CM8FPHK4J5EP607Y77XHA4","recruiter","Think like a skeptical technical recruiter when working on the daily.dev Recruiter platform. Use when reviewing UI\u002FUX, features, or code in webapp\u002Fpages\u002Frecruiter.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecruiter\u002FSKILL.md",[],[],{"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":19},"01M7CM8CB9XR2W46XJ3T2X0245","changelog","Generate a daily.dev changelog post for a new feature or update. Use when a team member needs to write a changelog announcement.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CM88HKHZP4S2H9GYKWCBPB","webapp-testing","Web application testing principles. E2E, Playwright, deep audit strategies.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CM831R2XYCHFNRGXD6NYS1","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CM7XTJ13ZQFZ9Y5SRYF8CP","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvulnerability-scanner\u002FSKILL.md",[],[]]