[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BFEFWPR9ZXEWACJJBQBRS":3,"skill-same:01M75BFEFWPR9ZXEWACJJBQBRS":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75BFEFWPR9ZXEWACJJBQBRS","token-codebase-exploration",null,"Use when exploring an unfamiliar codebase, understanding how a specific feature or pattern works, or learning how components interact. Provides the exploration workflow and strategy.","NormandErwan\u002FClaude","NormandErwan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7470865?v=4","01M75BENGB5CYYFMHFPN2P5VDN","Erwan Normand","01M75BENH549BJRCTY1483T64R",1,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-codebase-exploration\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: token-codebase-exploration\ndescription: Use when exploring an unfamiliar codebase, understanding how a specific feature or pattern works, or learning how components interact. Provides the exploration workflow and strategy.\nversion: 1.3.1\nallowed-tools: Bash, Read, Grep, Glob\n---\n\n# Token Codebase Exploration\n\n## Step 1: Determine Targeted vs Broad Before Reading Anything\n\n| User request | Approach |\n|---|---|\n| \"Help me understand this project\" | **Broad** |\n| \"How is this codebase organized?\" | **Broad** |\n| \"How does the AuthService work?\" | **Targeted** |\n| \"How do I implement this pattern here?\" | **Targeted** |\n| \"Show me examples of X\" | **Targeted** |\n| \"What patterns are used in this project?\" | Broad → then Targeted |\n\nNever start reading files before making this determination.\n\n---\n\n## Targeted Learning (when user asks \"how does X work\" or \"show me examples of Y\")\n\nFollow these 5 steps in order. Do not skip ahead to reading.\n\n**Step 1: Extract the concept** from the user's request and identify the likely file names\nor terms to search for.\n\n**Step 2: Search — do not read files yet.** Use grep and find to locate candidates.\nAnchor grep patterns to exclude comment lines.\n\n**Step 3: Rank examples** — prefer files with self-documenting names and explicit variable\nnames over short, dense files. A 35-line file with clear names teaches a pattern better\nthan an 8-line file with abbreviations. Use `wc -l` only as a tiebreaker between files\nof similar readability, not as the primary criterion.\n\n**Step 4: Read 2–3 selected examples fully** — not more. One simple or minimal example,\none standard example, and one advanced example only if the pattern has genuinely different\nvariations.\n\n**Step 5: Extract and explain the pattern** — never just show code. Explain what the\npattern does conceptually, what elements are required, and the common pitfalls specific\nto this codebase.\n\n---\n\n## Broad Exploration (when user asks to understand the whole project)\n\nWork through these phases in order. Read only what each phase requires.\n\n**Phase 1 — Structure overview (no Read yet):**\n\n```bash\ntree -L 2 || find . -maxdepth 2 -type d | head -30   # tree with fallback if absent\nls -la\ncat README.md   # this is the legitimate first Read\n```\n\n**Phase 2 — Entry point:** identify the main executable or initialization file for this\nlanguage and framework.\nRead the entry point — this is file 1.\n\n**Phase 3 — Core abstractions:** search for interface definitions and abstract base classes\nwithout reading files. These reveal the architecture's vocabulary.\n\n**Phase 4 — Most-used components and recent activity:** identify what modules are depended\non most frequently (via import\u002Fusing analysis) and which files have been modified recently\n(via git log). These two signals together locate the active core of the project.\n\nRead order after the entry point: one core service or business logic file → one\ninfrastructure file (repository, adapter, external interface). That is files 2 and 3.\n\n---\n\n## Stop at 5 Files — Then Summarize\n\nAfter reading 5 files, STOP. The limit is not about context window saturation\n(5 typical files use approximately 2% of the available context window). The limit\nexists to force a consolidation step: reading without summarizing produces worse answers\nthan reading 5 files, articulating what you now understand, and then reading 2 more\nwith a specific question in mind.\n\nSummarize findings and state what you now understand. Then read further only with a\nspecific question that summary leaves open.\n","# Token Codebase Exploration\n\n## Step 1: Determine Targeted vs Broad Before Reading Anything\n\n| User request | Approach |\n|---|---|\n| \"Help me understand this project\" | **Broad** |\n| \"How is this codebase organized?\" | **Broad** |\n| \"How does the AuthService work?\" | **Targeted** |\n| \"How do I implement this pattern here?\" | **Targeted** |\n| \"Show me examples of X\" | **Targeted** |\n| \"What patterns are used in this project?\" | Broad → then Targeted |\n\nNever start reading files before making this determination.\n\n---\n\n## Targeted Learning (when user asks \"how does X work\" or \"show me examples of Y\")\n\nFollow these 5 steps in order. Do not skip ahead to reading.\n\n**Step 1: Extract the concept** from the user's request and identify the likely file names\nor terms to search for.\n\n**Step 2: Search — do not read files yet.** Use grep and find to locate candidates.\nAnchor grep patterns to exclude comment lines.\n\n**Step 3: Rank examples** — prefer files with self-documenting names and explicit variable\nnames over short, dense files. A 35-line file with clear names teaches a pattern better\nthan an 8-line file with abbreviations. Use `wc -l` only as a tiebreaker between files\nof similar readability, not as the primary criterion.\n\n**Step 4: Read 2–3 selected examples fully** — not more. One simple or minimal example,\none standard example, and one advanced example only if the pattern has genuinely different\nvariations.\n\n**Step 5: Extract and explain the pattern** — never just show code. Explain what the\npattern does conceptually, what elements are required, and the common pitfalls specific\nto this codebase.\n\n---\n\n## Broad Exploration (when user asks to understand the whole project)\n\nWork through these phases in order. Read only what each phase requires.\n\n**Phase 1 — Structure overview (no Read yet):**\n\n```bash\ntree -L 2 || find . -maxdepth 2 -type d | head -30   # tree with fallback if absent\nls -la\ncat README.md   # this is the legitimate first Read\n```\n\n**Phase 2 — Entry point:** identify the main executable or initialization file for this\nlanguage and framework.\nRead the entry point — this is file 1.\n\n**Phase 3 — Core abstractions:** search for interface definitions and abstract base classes\nwithout reading files. These reveal the architecture's vocabulary.\n\n**Phase 4 — Most-used components and recent activity:** identify what modules are depended\non most frequently (via import\u002Fusing analysis) and which files have been modified recently\n(via git log). These two signals together locate the active core of the project.\n\nRead order after the entry point: one core service or business logic file → one\ninfrastructure file (repository, adapter, external interface). That is files 2 and 3.\n\n---\n\n## Stop at 5 Files — Then Summarize\n\nAfter reading 5 files, STOP. The limit is not about context window saturation\n(5 typical files use approximately 2% of the available context window). The limit\nexists to force a consolidation step: reading without summarizing produces worse answers\nthan reading 5 files, articulating what you now understand, and then reading 2 more\nwith a specific question in mind.\n\nSummarize findings and state what you now understand. Then read further only with a\nspecific question that summary leaves open.\n",{"name":5,"version":24,"description":7,"allowed-tools":25},"1.3.1","Bash, Read, Grep, Glob","main","336ef9f9a6dd71a2cc287082873fa3c8597dcf75","skills\u002Ftoken-codebase-exploration",0,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude","https:\u002F\u002Fgithub.com\u002FNormandErwan","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fnormanderwan\u002F","2026-11-11 04:37:11",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add NormandErwan\u002FClaude --skill token-codebase-exploration",{"tool":40,"command":41},"bunx","bunx skills add NormandErwan\u002FClaude --skill token-codebase-exploration",{"tool":43,"command":44},"pnpm","pnpm dlx skills add NormandErwan\u002FClaude --skill token-codebase-exploration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-codebase-exploration\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M75BG0TBQH53V52ZF840MGD2","write-guide","Use when writing a guide someone else will follow - a method guide, a playbook, a how-we-do-it document for a team or a client - or when reworking, auditing or extending one that already exists. Also when an outline is handed to you to fill in, when a guide's rules need evidence labels, or when a second guide joins the first and the two start contradicting each other.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-guide\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75BFX09MYSAKVZCM1713YAE","write-french","Use when the output is French - a chat reply in French, or a French markdown deliverable such as a guide, a report or a synthesis - including when the user writes in French and expects French back. Prevents French that reads as translated English: word-for-word calques, sentences compressed until the meaning is gone, jargon used before it is defined, invented turns of phrase.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75BFQQ0EPV92467E0C40CEX","verify-sources","Use when about to state a factual, technical, historical, or procedural claim in ANY domain (software, DIY\u002Fcraft, health, legal, finance...) - a version number, default value, statistic, API behavior, a legal deadline, a health claim, a manufacturer spec, \"X always\u002Fnever does Y\", \"the docs say\", \"best practice is\" - that you have not verified against a source this turn, or when tempted to answer a factual question from memory under time pressure","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fverify-sources\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75BFJW35J7NT1MGEZ0P477T","token-file-ops","Use when reading, editing, creating, or manipulating files; or running commands with potentially large output. Provides generic bash-first patterns for any file type.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-file-ops\u002FSKILL.md",[],[],{"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":19},"01M75BFBQA8JWX7TFPDWTCTFW2","teach","Use when the user sets learning a topic or skill as their own goal - \"teach me X\", \"I want to learn X\", \"help me get good at X\", a course or study plan for themselves. Not for a question one reply answers (\"what is X\", \"explain X\").","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M75BF8H0DK5VBG33Z5ZW83X4","search-first","Use before writing any script, config, workflow or service that automates a task or connects two systems - even when a standard approach seems obvious. Search for an existing tool, package, GitHub Action or service first, then adopt, extend, compose or build.","MIT","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fsearch-first\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fsearch-first\u002FSKILL.md",[],[]]