[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FPRF0R4KMB8SF7G4F78AG":3,"skill-same:01M70FPRF0R4KMB8SF7G4F78AG":76},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M70FPRF0R4KMB8SF7G4F78AG","codebase-onboarding",null,"Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodebase-onboarding\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"codebase","onboarding","codebase onboarding","starter","with","use","repo","for","new project","guide","generate","onboarding guide","analyze","architecture","code","when","map","up","time","project","2026-11-10 10:12:30",false,"---\nname: codebase-onboarding\ndescription: Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.\nmetadata:\n  origin: ECC\n---\n\n# Codebase Onboarding\n\nSystematically analyze an unfamiliar codebase and produce a structured onboarding guide. Designed for developers joining a new project or setting up Claude Code in an existing repo for the first time.\n\n## When to Use\n\n- First time opening a project with Claude Code\n- Joining a new team or repository\n- User asks \"help me understand this codebase\"\n- User asks to generate a CLAUDE.md for a project\n- User says \"onboard me\" or \"walk me through this repo\"\n\n## How It Works\n\n### Phase 1: Reconnaissance\n\nGather raw signals about the project without reading every file. Run these checks in parallel:\n\n```\n1. Package manifest detection\n   → package.json, go.mod, Cargo.toml, pyproject.toml, pom.xml, build.gradle,\n     Gemfile, composer.json, mix.exs, pubspec.yaml\n\n2. Framework fingerprinting\n   → next.config.*, nuxt.config.*, angular.json, vite.config.*,\n     django settings, flask app factory, fastapi main, rails config\n\n3. Entry point identification\n   → main.*, index.*, app.*, server.*, cmd\u002F, src\u002Fmain\u002F\n\n4. Directory structure snapshot\n   → Top 2 levels of the directory tree, ignoring node_modules, vendor,\n     .git, dist, build, __pycache__, .next\n\n5. Config and tooling detection\n   → .eslintrc*, .prettierrc*, tsconfig.json, Makefile, Dockerfile,\n     docker-compose*, .github\u002Fworkflows\u002F, .env.example, CI configs\n\n6. Test structure detection\n   → tests\u002F, test\u002F, __tests__\u002F, *_test.go, *.spec.ts, *.test.js,\n     pytest.ini, jest.config.*, vitest.config.*\n```\n\n### Phase 2: Architecture Mapping\n\nFrom the reconnaissance data, identify:\n\n**Tech Stack**\n- Language(s) and version constraints\n- Framework(s) and major libraries\n- Database(s) and ORMs\n- Build tools and bundlers\n- CI\u002FCD platform\n\n**Architecture Pattern**\n- Monolith, monorepo, microservices, or serverless\n- Frontend\u002Fbackend split or full-stack\n- API style: REST, GraphQL, gRPC, tRPC\n\n**Key Directories**\nMap the top-level directories to their purpose:\n\n\u003C!-- Example for a React project — replace with detected directories -->\n```\nsrc\u002Fcomponents\u002F  → React UI components\nsrc\u002Fapi\u002F         → API route handlers\nsrc\u002Flib\u002F         → Shared utilities\nsrc\u002Fdb\u002F          → Database models and migrations\ntests\u002F           → Test suites\nscripts\u002F         → Build and deployment scripts\n```\n\n**Data Flow**\nTrace one request from entry to response:\n- Where does a request enter? (router, handler, controller)\n- How is it validated? (middleware, schemas, guards)\n- Where is business logic? (services, models, use cases)\n- How does it reach the database? (ORM, raw queries, repositories)\n\n### Phase 3: Convention Detection\n\nIdentify patterns the codebase already follows:\n\n**Naming Conventions**\n- File naming: kebab-case, camelCase, PascalCase, snake_case\n- Component\u002Fclass naming patterns\n- Test file naming: `*.test.ts`, `*.spec.ts`, `*_test.go`\n\n**Code Patterns**\n- Error handling style: try\u002Fcatch, Result types, error codes\n- Dependency injection or direct imports\n- State management approach\n- Async patterns: callbacks, promises, async\u002Fawait, channels\n\n**Git Conventions**\n- Branch naming from recent branches\n- Commit message style from recent commits\n- PR workflow (squash, merge, rebase)\n- If the repo has no commits yet or only a shallow history (e.g. `git clone --depth 1`), skip this section and note \"Git history unavailable or too shallow to detect conventions\"\n\n### Phase 4: Generate Onboarding Artifacts\n\nProduce two outputs:\n\n#### Output 1: Onboarding Guide\n\n```markdown\n# Onboarding Guide: [Project Name]\n\n## Overview\n[2-3 sentences: what this project does and who it serves]\n\n## Tech Stack\n\u003C!-- Example for a Next.js project — replace with detected stack -->\n| Layer | Technology | Version |\n|-------|-----------|---------|\n| Language | TypeScript | 5.x |\n| Framework | Next.js | 14.x |\n| Database | PostgreSQL | 16 |\n| ORM | Prisma | 5.x |\n| Testing | Jest + Playwright | - |\n\n## Architecture\n[Diagram or description of how components connect]\n\n## Key Entry Points\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n- **API routes**: `src\u002Fapp\u002Fapi\u002F` — Next.js route handlers\n- **UI pages**: `src\u002Fapp\u002F(dashboard)\u002F` — authenticated pages\n- **Database**: `prisma\u002Fschema.prisma` — data model source of truth\n- **Config**: `next.config.ts` — build and runtime config\n\n## Directory Map\n[Top-level directory → purpose mapping]\n\n## Request Lifecycle\n[Trace one API request from entry to response]\n\n## Conventions\n- [File naming pattern]\n- [Error handling approach]\n- [Testing patterns]\n- [Git workflow]\n\n## Common Tasks\n\u003C!-- Example for a Node.js project — replace with detected commands -->\n- **Run dev server**: `npm run dev`\n- **Run tests**: `npm test`\n- **Run linter**: `npm run lint`\n- **Database migrations**: `npx prisma migrate dev`\n- **Build for production**: `npm run build`\n\n## Where to Look\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n| I want to... | Look at... |\n|--------------|-----------|\n| Add an API endpoint | `src\u002Fapp\u002Fapi\u002F` |\n| Add a UI page | `src\u002Fapp\u002F(dashboard)\u002F` |\n| Add a database table | `prisma\u002Fschema.prisma` |\n| Add a test | `tests\u002F` matching the source path |\n| Change build config | `next.config.ts` |\n```\n\n#### Output 2: Starter CLAUDE.md\n\nGenerate or update a project-specific CLAUDE.md based on detected conventions. If `CLAUDE.md` already exists, read it first and enhance it — preserve existing project-specific instructions and clearly call out what was added or changed.\n\n```markdown\n# Project Instructions\n\n## Tech Stack\n[Detected stack summary]\n\n## Code Style\n- [Detected naming conventions]\n- [Detected patterns to follow]\n\n## Testing\n- Run tests: `[detected test command]`\n- Test pattern: [detected test file convention]\n- Coverage: [if configured, the coverage command]\n\n## Build & Run\n- Dev: `[detected dev command]`\n- Build: `[detected build command]`\n- Lint: `[detected lint command]`\n\n## Project Structure\n[Key directory → purpose map]\n\n## Conventions\n- [Commit style if detectable]\n- [PR workflow if detectable]\n- [Error handling patterns]\n```\n\n## Best Practices\n\n1. **Don't read everything** — reconnaissance should use Glob and Grep, not Read on every file. Read selectively only for ambiguous signals.\n2. **Verify, don't guess** — if a framework is detected from config but the actual code uses something different, trust the code.\n3. **Respect existing CLAUDE.md** — if one already exists, enhance it rather than replacing it. Call out what's new vs existing.\n4. **Stay concise** — the onboarding guide should be scannable in 2 minutes. Details belong in the code, not the guide.\n5. **Flag unknowns** — if a convention can't be confidently detected, say so rather than guessing. \"Could not determine test runner\" is better than a wrong answer.\n\n## Anti-Patterns to Avoid\n\n- Generating a CLAUDE.md that's longer than 100 lines — keep it focused\n- Listing every dependency — highlight only the ones that shape how you write code\n- Describing obvious directory names — `src\u002F` doesn't need an explanation\n- Copying the README — the onboarding guide adds structural insight the README lacks\n\n## Examples\n\n### Example 1: First time in a new repo\n**User**: \"Onboard me to this codebase\"\n**Action**: Run full 4-phase workflow → produce Onboarding Guide + Starter CLAUDE.md\n**Output**: Onboarding Guide printed directly to the conversation, plus a `CLAUDE.md` written to the project root\n\n### Example 2: Generate CLAUDE.md for existing project\n**User**: \"Generate a CLAUDE.md for this project\"\n**Action**: Run Phases 1-3, skip Onboarding Guide, produce only CLAUDE.md\n**Output**: Project-specific `CLAUDE.md` with detected conventions\n\n### Example 3: Enhance existing CLAUDE.md\n**User**: \"Update the CLAUDE.md with current project conventions\"\n**Action**: Read existing CLAUDE.md, run Phases 1-3, merge new findings\n**Output**: Updated `CLAUDE.md` with additions clearly marked\n","# Codebase Onboarding\n\nSystematically analyze an unfamiliar codebase and produce a structured onboarding guide. Designed for developers joining a new project or setting up Claude Code in an existing repo for the first time.\n\n## When to Use\n\n- First time opening a project with Claude Code\n- Joining a new team or repository\n- User asks \"help me understand this codebase\"\n- User asks to generate a CLAUDE.md for a project\n- User says \"onboard me\" or \"walk me through this repo\"\n\n## How It Works\n\n### Phase 1: Reconnaissance\n\nGather raw signals about the project without reading every file. Run these checks in parallel:\n\n```\n1. Package manifest detection\n   → package.json, go.mod, Cargo.toml, pyproject.toml, pom.xml, build.gradle,\n     Gemfile, composer.json, mix.exs, pubspec.yaml\n\n2. Framework fingerprinting\n   → next.config.*, nuxt.config.*, angular.json, vite.config.*,\n     django settings, flask app factory, fastapi main, rails config\n\n3. Entry point identification\n   → main.*, index.*, app.*, server.*, cmd\u002F, src\u002Fmain\u002F\n\n4. Directory structure snapshot\n   → Top 2 levels of the directory tree, ignoring node_modules, vendor,\n     .git, dist, build, __pycache__, .next\n\n5. Config and tooling detection\n   → .eslintrc*, .prettierrc*, tsconfig.json, Makefile, Dockerfile,\n     docker-compose*, .github\u002Fworkflows\u002F, .env.example, CI configs\n\n6. Test structure detection\n   → tests\u002F, test\u002F, __tests__\u002F, *_test.go, *.spec.ts, *.test.js,\n     pytest.ini, jest.config.*, vitest.config.*\n```\n\n### Phase 2: Architecture Mapping\n\nFrom the reconnaissance data, identify:\n\n**Tech Stack**\n- Language(s) and version constraints\n- Framework(s) and major libraries\n- Database(s) and ORMs\n- Build tools and bundlers\n- CI\u002FCD platform\n\n**Architecture Pattern**\n- Monolith, monorepo, microservices, or serverless\n- Frontend\u002Fbackend split or full-stack\n- API style: REST, GraphQL, gRPC, tRPC\n\n**Key Directories**\nMap the top-level directories to their purpose:\n\n\u003C!-- Example for a React project — replace with detected directories -->\n```\nsrc\u002Fcomponents\u002F  → React UI components\nsrc\u002Fapi\u002F         → API route handlers\nsrc\u002Flib\u002F         → Shared utilities\nsrc\u002Fdb\u002F          → Database models and migrations\ntests\u002F           → Test suites\nscripts\u002F         → Build and deployment scripts\n```\n\n**Data Flow**\nTrace one request from entry to response:\n- Where does a request enter? (router, handler, controller)\n- How is it validated? (middleware, schemas, guards)\n- Where is business logic? (services, models, use cases)\n- How does it reach the database? (ORM, raw queries, repositories)\n\n### Phase 3: Convention Detection\n\nIdentify patterns the codebase already follows:\n\n**Naming Conventions**\n- File naming: kebab-case, camelCase, PascalCase, snake_case\n- Component\u002Fclass naming patterns\n- Test file naming: `*.test.ts`, `*.spec.ts`, `*_test.go`\n\n**Code Patterns**\n- Error handling style: try\u002Fcatch, Result types, error codes\n- Dependency injection or direct imports\n- State management approach\n- Async patterns: callbacks, promises, async\u002Fawait, channels\n\n**Git Conventions**\n- Branch naming from recent branches\n- Commit message style from recent commits\n- PR workflow (squash, merge, rebase)\n- If the repo has no commits yet or only a shallow history (e.g. `git clone --depth 1`), skip this section and note \"Git history unavailable or too shallow to detect conventions\"\n\n### Phase 4: Generate Onboarding Artifacts\n\nProduce two outputs:\n\n#### Output 1: Onboarding Guide\n\n```markdown\n# Onboarding Guide: [Project Name]\n\n## Overview\n[2-3 sentences: what this project does and who it serves]\n\n## Tech Stack\n\u003C!-- Example for a Next.js project — replace with detected stack -->\n| Layer | Technology | Version |\n|-------|-----------|---------|\n| Language | TypeScript | 5.x |\n| Framework | Next.js | 14.x |\n| Database | PostgreSQL | 16 |\n| ORM | Prisma | 5.x |\n| Testing | Jest + Playwright | - |\n\n## Architecture\n[Diagram or description of how components connect]\n\n## Key Entry Points\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n- **API routes**: `src\u002Fapp\u002Fapi\u002F` — Next.js route handlers\n- **UI pages**: `src\u002Fapp\u002F(dashboard)\u002F` — authenticated pages\n- **Database**: `prisma\u002Fschema.prisma` — data model source of truth\n- **Config**: `next.config.ts` — build and runtime config\n\n## Directory Map\n[Top-level directory → purpose mapping]\n\n## Request Lifecycle\n[Trace one API request from entry to response]\n\n## Conventions\n- [File naming pattern]\n- [Error handling approach]\n- [Testing patterns]\n- [Git workflow]\n\n## Common Tasks\n\u003C!-- Example for a Node.js project — replace with detected commands -->\n- **Run dev server**: `npm run dev`\n- **Run tests**: `npm test`\n- **Run linter**: `npm run lint`\n- **Database migrations**: `npx prisma migrate dev`\n- **Build for production**: `npm run build`\n\n## Where to Look\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n| I want to... | Look at... |\n|--------------|-----------|\n| Add an API endpoint | `src\u002Fapp\u002Fapi\u002F` |\n| Add a UI page | `src\u002Fapp\u002F(dashboard)\u002F` |\n| Add a database table | `prisma\u002Fschema.prisma` |\n| Add a test | `tests\u002F` matching the source path |\n| Change build config | `next.config.ts` |\n```\n\n#### Output 2: Starter CLAUDE.md\n\nGenerate or update a project-specific CLAUDE.md based on detected conventions. If `CLAUDE.md` already exists, read it first and enhance it — preserve existing project-specific instructions and clearly call out what was added or changed.\n\n```markdown\n# Project Instructions\n\n## Tech Stack\n[Detected stack summary]\n\n## Code Style\n- [Detected naming conventions]\n- [Detected patterns to follow]\n\n## Testing\n- Run tests: `[detected test command]`\n- Test pattern: [detected test file convention]\n- Coverage: [if configured, the coverage command]\n\n## Build & Run\n- Dev: `[detected dev command]`\n- Build: `[detected build command]`\n- Lint: `[detected lint command]`\n\n## Project Structure\n[Key directory → purpose map]\n\n## Conventions\n- [Commit style if detectable]\n- [PR workflow if detectable]\n- [Error handling patterns]\n```\n\n## Best Practices\n\n1. **Don't read everything** — reconnaissance should use Glob and Grep, not Read on every file. Read selectively only for ambiguous signals.\n2. **Verify, don't guess** — if a framework is detected from config but the actual code uses something different, trust the code.\n3. **Respect existing CLAUDE.md** — if one already exists, enhance it rather than replacing it. Call out what's new vs existing.\n4. **Stay concise** — the onboarding guide should be scannable in 2 minutes. Details belong in the code, not the guide.\n5. **Flag unknowns** — if a convention can't be confidently detected, say so rather than guessing. \"Could not determine test runner\" is better than a wrong answer.\n\n## Anti-Patterns to Avoid\n\n- Generating a CLAUDE.md that's longer than 100 lines — keep it focused\n- Listing every dependency — highlight only the ones that shape how you write code\n- Describing obvious directory names — `src\u002F` doesn't need an explanation\n- Copying the README — the onboarding guide adds structural insight the README lacks\n\n## Examples\n\n### Example 1: First time in a new repo\n**User**: \"Onboard me to this codebase\"\n**Action**: Run full 4-phase workflow → produce Onboarding Guide + Starter CLAUDE.md\n**Output**: Onboarding Guide printed directly to the conversation, plus a `CLAUDE.md` written to the project root\n\n### Example 2: Generate CLAUDE.md for existing project\n**User**: \"Generate a CLAUDE.md for this project\"\n**Action**: Run Phases 1-3, skip Onboarding Guide, produce only CLAUDE.md\n**Output**: Project-specific `CLAUDE.md` with detected conventions\n\n### Example 3: Enhance existing CLAUDE.md\n**User**: \"Update the CLAUDE.md with current project conventions\"\n**Action**: Read existing CLAUDE.md, run Phases 1-3, merge new findings\n**Output**: Updated `CLAUDE.md` with additions clearly marked\n",{"name":5,"metadata":52,"description":7},{"origin":53},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodebase-onboarding",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill codebase-onboarding",{"tool":68,"command":69},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill codebase-onboarding",{"tool":71,"command":72},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill codebase-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodebase-onboarding\u002FSKILL.md",true,[],[77,85,113,131,150,165],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":105,"publishedAt":47},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[91,96,99,102],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":100,"categoryName":101,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":103,"categoryName":104,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000008","测试与质量",[106,107,108,109,32,110,111,42,112],"writing","writing skills","editing","deployment","Existing","new","work",{"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":122,"publishedAt":47},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[119,120,121],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,123,124,125,42,41,34,32,126,127,128,129,130],"writing plans","plans","you","requirements","task","multi","spec","multi-step task",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":47},"01M70JNTYVGXFZT8PASZ844TH8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[138,139,140,141,142,143,32,144,145,146,42,147,112,148,149],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":47},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[156],{"categoryNo":100,"categoryName":101,"taxonomyType":94,"taxonomyTypeDesc":95},[158,159,160,161,32,42,162,163,164],"using superpowers","superpowers","conversation","how to","how","find","questions",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":47},"01M70JN57CE588NPYPYTWH1DWG","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[172,173,174,175,176,177,42,112,178,179,180,181,182,183,184,124,32,185,186],"using git worktrees","Using git","git","worktrees","git worktrees","implementation","git worktree","worktree","native","Tools","isolation","fallback","feature","via","workspace"]