Use whenever an AI agent executes a multi-step task to save tokens, parallelize tool calls, cache prompts, and keep replies under 2000 chars
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Bug ไฟฎๅคๅ จๆต็จใๅผบๅถ /investigate ๆพๆ นๅ ๏ผ็ฆๆญข"็ไผผไฟฎๅฅฝๅฐฑไบคไป"ใ/freeze ้ๅฎๆไปถ ้ฒๆญข้กบๆ"ๆธ ็"ๆ ๅ ณไปฃ็ ๏ผๅ ๅๅค็ฐๅคฑ่ดฅๆต่ฏๅๅไฟฎๅคใ Use when reporting bugs, errors, 500s, stack traces, or "it stopped working" type issues. Voice triggers: "ไฟฎ bug", "/bugfix-flow", "bugfix".
ๅผๅ็ปๅๆณๆปๅ ฅๅฃใๆ นๆฎ่พๅ ฅๅฝขๅผ๏ผ้ๆฑๆๆกฃ / ๅๅ้กน็ฎ / ไธๅฅ่ฏ๏ผร ๅผๅ่ๅด๏ผๅ็ซฏ / ๅ็ซฏ / ๅ จๆ ๏ผ ร ไฟฎ้ฅฐ็ฌฆ๏ผๅธฆ่ฎพ่ฎก็จฟ / ๆฐๆฎๅบ่ฟ็งป / ๅช่่ฐ ็ญ๏ผ่ชๅจ่ทฏ็ฑๅฐๆญฃ็กฎ็ๅญ skillใๅๆถ่ฆ็ 4 ็ฑป้้ๆฑไปปๅก๏ผ bugfix / ้ๆ / ๆง่ฝไผๅ / ็ฌฌไธๆนๆฅๅ ฅใ Use when asked to "ๆฅ้ๆฑ", "ๅผๅงๅผๅ", "/dev-flow", "็ปๅๆณ", "dev flow", or whenever the user hands over a development task and you need to decide which workflow skill to invoke. Voice triggers: "ๆฅ้ๆฑ", "ๅผๅงๅผๅ", "็ปๅๆณ". Note: ้ถๆฎตๅ็ๅ skills๏ผ/dev-understandใ/dev-implementใ/dev-ship-retro๏ผๆ้ถๆฎตๆๅ๏ผ ไธๆฌ่ทฏ็ฑๆๅบๆฏ็ฑปๅๆๅ็ๅญ skill ไบ่กฅ๏ผๅฝ็จๆทๆ็กฎ่ฏด"ๅชๅๆ้ถๆฎต"ๆถไผๅ ๅน้ ้ฃไบ skillใ
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
ๆง่ฝไผๅๅ จๆต็จใๅ benchmark ็ซๅบ็บฟ โ profile ๆพ็ถ้ข โ ๅไธๅ้ไผๅ โ ๅ benchmark ๅฏนๆฏใ็ฆๆญข"ๅญๆ่งไผๅ"๏ผๆฏไธชๆนๅจๅฟ ้กปๅธฆๆฐๆฎ่ฏๆใ Use when optimizing for performance, page speed, web vitals, or backend latency. Voice triggers: "ๆง่ฝไผๅ", "/perf-flow", "ๆ้".
ไปฃ็ ้ๆ / ๆด็ใไปปไฝ้ๆๅฟ ้กปๅ ๆ่ฆ็ๅพ ้ๆๅบๅ็ๆต่ฏ็ฝ๏ผๅๆญฅๅๅญ commit๏ผๆฏๆญฅ ็ปฟๆต๏ผไธๅ ่ฎธ"ๅคง็็ธๅผ้ๆ"ใๆง่ฝ/่กไธบๅๆดๅฑไบ perf-flow / dev-flow๏ผไธๅจๆญค่ๅดใ Use when refactoring code, cleaning up tech debt, or restructuring without behavior change. Voice triggers: "้ๆ", "ๆด็ไปฃ็ ", "/refactor-flow".
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions