[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JM2KYTFJ0THFNNACH9JDPB":3,"skill-same:01M6JM2KYTFJ0THFNNACH9JDPB":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6JM2KYTFJ0THFNNACH9JDPB","systematic-debugging",null,"Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuring understanding before attempting solutions.","superhealth\u002Fskills-hub","superhealth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6292112?v=4","01M6JA6E7F21BYK5W3E4P270TT","01M6JA6EC0W8MPHKDJVBZDSEZ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsystematic-debugging\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"systematic debugging","debugging","systematic","test","framework","Bash","grep","read","edit","behavior","use","superpowers","bug","fixes","four-phase","2026-11-10 10:12:30",false,"---\nname: systematic-debugging\ndescription: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuring understanding before attempting solutions.\nallowed-tools: Read, Glob, Grep, Bash, Edit\nlicense: MIT\nmetadata:\n  author: obra\u002Fsuperpowers\n  version: \"1.0\"\n---\n\n# Systematic Debugging\n\n버그, 테스트 실패, 예상치 못한 동작에 대한 체계적 디버깅 방법론입니다.\n\n## Core Principle\n\n> **\"ALWAYS find root cause before attempting fixes. Symptom fixes are failure.\"**\n\n## Mandatory Phases\n\n### Phase 1: Root Cause Investigation\n\n```\n1. 에러 메시지 정확히 읽기\n2. 문제를 일관되게 재현\n3. 최근 변경사항 확인\n4. 멀티 컴포넌트 시스템에서 진단 증거 수집\n5. 데이터 흐름을 역방향으로 추적\n```\n\n### Phase 2: Pattern Analysis\n\n```\n1. 작동하는 예시 찾기\n2. 레퍼런스와 비교\n3. 차이점 식별\n4. 의존성 이해\n```\n\n### Phase 3: Hypothesis Testing\n\n```\n1. 구체적인 가설 수립\n   - \"X가 Y 때문에 발생한다고 생각됨\"\n\n2. 최소한의 테스트로 검증\n   - 한 번에 하나의 변수만 변경\n\n3. 과학적으로 결과 검증\n   - 가설이 틀렸다면 다음 가설로\n```\n\n### Phase 4: Implementation\n\n```\n1. 실패하는 테스트 케이스 작성\n2. 단일 수정 구현\n3. 결과 검증\n4. 3번 실패 시 중단\n   → 아키텍처 문제 가능성 검토\n```\n\n## Critical Rules\n\n| 규칙 | 설명 |\n|------|------|\n| 순차 진행 | 단계를 건너뛰지 않음 |\n| 단일 수정 | 동시에 여러 수정 금지 |\n| 3회 실패 시 중단 | 아키텍처 검토 필요 |\n\n## Red Flags - 프로세스 포기 징후\n\n```\n❌ \"일단 빠르게 고치고...\"\n❌ \"아마 여기가 문제인 것 같아서...\"\n❌ \"시간이 없어서 그냥...\"\n❌ \"재현은 안되지만 고쳐봤어요\"\n```\n\n## Debugging Template\n\n```markdown\n## 문제\n[증상 설명]\n\n## 재현 단계\n1. [단계 1]\n2. [단계 2]\n→ [예상 결과] vs [실제 결과]\n\n## Phase 1: 조사\n- 에러 메시지: [정확한 메시지]\n- 최근 변경: [관련 커밋\u002F변경]\n- 데이터 흐름: [추적 결과]\n\n## Phase 2: 패턴 분석\n- 작동 케이스: [예시]\n- 차이점: [식별된 차이]\n\n## Phase 3: 가설\n1. 가설: [내용]\n   테스트: [방법]\n   결과: [결과]\n\n## Phase 4: 수정\n- 수정 내용: [변경사항]\n- 테스트: [검증 방법]\n- 결과: ✅\u002F❌\n```\n\n## Evidence-Based Results\n\n```\n체계적 디버깅 적용 시:\n- 문제 해결 시간: 2-3시간 → 15-30분\n- 재발 방지: 근본 원인 해결로 재발 감소\n- 학습 효과: 시스템 이해도 향상\n```\n\n## Best Practices\n\n1. **증거 수집**: 로그, 스택 트레이스, 재현 단계 문서화\n2. **최소 변경**: 한 번에 하나만 변경하고 테스트\n3. **원복 준비**: 변경 전 상태로 돌릴 수 있게 준비\n4. **기록 유지**: 시도한 것과 결과 문서화\n","# Systematic Debugging\n\n버그, 테스트 실패, 예상치 못한 동작에 대한 체계적 디버깅 방법론입니다.\n\n## Core Principle\n\n> **\"ALWAYS find root cause before attempting fixes. Symptom fixes are failure.\"**\n\n## Mandatory Phases\n\n### Phase 1: Root Cause Investigation\n\n```\n1. 에러 메시지 정확히 읽기\n2. 문제를 일관되게 재현\n3. 최근 변경사항 확인\n4. 멀티 컴포넌트 시스템에서 진단 증거 수집\n5. 데이터 흐름을 역방향으로 추적\n```\n\n### Phase 2: Pattern Analysis\n\n```\n1. 작동하는 예시 찾기\n2. 레퍼런스와 비교\n3. 차이점 식별\n4. 의존성 이해\n```\n\n### Phase 3: Hypothesis Testing\n\n```\n1. 구체적인 가설 수립\n   - \"X가 Y 때문에 발생한다고 생각됨\"\n\n2. 최소한의 테스트로 검증\n   - 한 번에 하나의 변수만 변경\n\n3. 과학적으로 결과 검증\n   - 가설이 틀렸다면 다음 가설로\n```\n\n### Phase 4: Implementation\n\n```\n1. 실패하는 테스트 케이스 작성\n2. 단일 수정 구현\n3. 결과 검증\n4. 3번 실패 시 중단\n   → 아키텍처 문제 가능성 검토\n```\n\n## Critical Rules\n\n| 규칙 | 설명 |\n|------|------|\n| 순차 진행 | 단계를 건너뛰지 않음 |\n| 단일 수정 | 동시에 여러 수정 금지 |\n| 3회 실패 시 중단 | 아키텍처 검토 필요 |\n\n## Red Flags - 프로세스 포기 징후\n\n```\n❌ \"일단 빠르게 고치고...\"\n❌ \"아마 여기가 문제인 것 같아서...\"\n❌ \"시간이 없어서 그냥...\"\n❌ \"재현은 안되지만 고쳐봤어요\"\n```\n\n## Debugging Template\n\n```markdown\n## 문제\n[증상 설명]\n\n## 재현 단계\n1. [단계 1]\n2. [단계 2]\n→ [예상 결과] vs [실제 결과]\n\n## Phase 1: 조사\n- 에러 메시지: [정확한 메시지]\n- 최근 변경: [관련 커밋\u002F변경]\n- 데이터 흐름: [추적 결과]\n\n## Phase 2: 패턴 분석\n- 작동 케이스: [예시]\n- 차이점: [식별된 차이]\n\n## Phase 3: 가설\n1. 가설: [내용]\n   테스트: [방법]\n   결과: [결과]\n\n## Phase 4: 수정\n- 수정 내용: [변경사항]\n- 테스트: [검증 방법]\n- 결과: ✅\u002F❌\n```\n\n## Evidence-Based Results\n\n```\n체계적 디버깅 적용 시:\n- 문제 해결 시간: 2-3시간 → 15-30분\n- 재발 방지: 근본 원인 해결로 재발 감소\n- 학습 효과: 시스템 이해도 향상\n```\n\n## Best Practices\n\n1. **증거 수집**: 로그, 스택 트레이스, 재현 단계 문서화\n2. **최소 변경**: 한 번에 하나만 변경하고 테스트\n3. **원복 준비**: 변경 전 상태로 돌릴 수 있게 준비\n4. **기록 유지**: 시도한 것과 결과 문서화\n",{"name":5,"license":14,"metadata":43,"description":7,"allowed-tools":46},{"author":44,"version":45},"obra\u002Fsuperpowers","1.0","Read, Glob, Grep, Bash, Edit","master","08cc2532077058aa50e6e18f54695bc256c88152","skills\u002Fdoyajin174\u002Fsystematic-debugging","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub","https:\u002F\u002Fgithub.com\u002Fsuperhealth","java engineer","2026-04-06 22:07:23",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add superhealth\u002Fskills-hub --skill systematic-debugging",{"tool":60,"command":61},"bunx","bunx skills add superhealth\u002Fskills-hub --skill systematic-debugging",{"tool":63,"command":64},"pnpm","pnpm dlx skills add superhealth\u002Fskills-hub --skill systematic-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsystematic-debugging\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"skill-report.json","REFERENCE","参考文档",11025,"https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsystematic-debugging\u002Fskill-report.json",[75,105,129,142,158,182],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":84,"publishedAt":38},"01M6MC9F3WHV8S8FZ2W4TRB0FE","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fzhanlincui\u002Fvercel-react-best-practices\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"react","vercel react best practices","best practices","vercel","react best practices","data fetching","code","triggers","pages","next","patterns","refactoring","data","Optimization","tasks","guidelines","react components","components","performance","writing",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":113,"publishedAt":38},"01M6MB8KWE1Q5A5KERR7RFTQWP","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-testing-best-practices\u002FSKILL.md",[111,112],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},[114,115,116,87,117,118,119,120,121,33,122,95,26,123,124,125,126,127,128],"vue testing best practices","testing best practices","vue","testing","testing patterns","js","e2e","vitest","component","mocking","for","utils","e2e testing","github","playwright",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":38},"01M6MB8GK06M6GA4KVYNDV1BZP","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-router-best-practices\u002FSKILL.md",[135],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},[87,116,137,138,139,95,140,141,122,127],"router","vue router best practices","route","navigation","lifecycle",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":38},"01M6MB8DQF21TZMQ9XC3745ERW","vue-pinia-best-practices","Pinia stores, state management patterns, store setup, and reactivity with stores.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-pinia-best-practices\u002FSKILL.md",[148],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},[150,151,116,87,152,153,95,154,155,156,157,127],"vue pinia best practices","pinia","with","store","management","state","state management","setup",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":173,"publishedAt":38},"01M6MB8A7MC08747J9TV4GWQ9A","vue-options-api-best-practices","Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-options-api-best-practices\u002FSKILL.md",[164,165,168],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[116,174,175,176,87,177,178,179,180,97,127,181],"options","vue options api best practices","api","methods","reference","only","context","style",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":38},"01M6MB85ZTQC24Q04X49MM4YXN","vue-development-guides","A collection of best practices and tips for developing applications using Vue.js. This skill MUST be apply when developing, refactoring or reviewing Vue.js or Nuxt projects.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-development-guides\u002FSKILL.md",[188],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},[190,116,191,192,127,193,194,124,195,196,197,119,96,198,199,87],"development","guides","vue development guides","tips","apply","project","nuxt","projects","collection","applications"]