[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTRAFE894ASD3PTHBEB1SJ":3,"skill-same:01M6NTRAFE894ASD3PTHBEB1SJ":74},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6NTRAFE894ASD3PTHBEB1SJ","explore",null,"Meta-skill for internal codebase exploration at varying depths (quick\u002Fdeep\u002Farchitecture)","rubicanjr\u002FFinCognis","rubicanjr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234912519?v=4","01M6NT156NND8J474G34SB3923","Rubi","01M6NT15B70RWXE1N3YV0BZY8A",0,"MIT","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fexplore\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"exploration","codebase exploration","for","layers","at","quick","deep","brownfield","meta-skill","call","architecture","task","call graph","write","read","analyze","Bash","Meta","graph","2026-11-10 10:12:30",false,"---\nname: explore\ndescription: Meta-skill for internal codebase exploration at varying depths (quick\u002Fdeep\u002Farchitecture)\nallowed-tools: [Bash, Task, Read, Glob, Grep, Write]\nkeywords: [explore, codebase, architecture, understand, analyze, layers, call graph, brownfield]\n---\n\n# Explore - Internal Codebase Exploration\n\nMeta-skill for exploring an internal codebase at varying depths. READ-ONLY workflow - no code changes.\n\n## Usage\n\n```\n\u002Fexplore \u003Cdepth> [options]\n```\n\n## Question Flow (No Arguments)\n\nIf the user types just `\u002Fexplore` with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase.\n\n### Phase 0: Workflow Selection\n\n```yaml\nquestion: \"How would you like to explore?\"\nheader: \"Explore\"\noptions:\n  - label: \"Help me choose (Recommended)\"\n    description: \"I'll ask questions to pick the right exploration depth\"\n  - label: \"Quick - fast overview\"\n    description: \"Chain: tldr tree → tldr structure (~1 min)\"\n  - label: \"Deep - comprehensive analysis\"\n    description: \"Chain: onboard → tldr → research → document (~5 min)\"\n  - label: \"Architecture - layers & dependencies\"\n    description: \"Chain: tldr arch → call graph → layer mapping (~3 min)\"\n```\n\n**Mapping:**\n- \"Help me choose\" → Continue to Phase 1-4 questions\n- \"Quick\" → Set depth=quick, skip to Phase 2 (scope)\n- \"Deep\" → Set depth=deep, skip to Phase 2 (scope)\n- \"Architecture\" → Set depth=architecture, skip to Phase 2 (scope)\n\n**If Answer is Unclear (via \"Other\"):**\n```yaml\nquestion: \"I want to understand how deep you want to explore. Did you mean...\"\nheader: \"Clarify\"\noptions:\n  - label: \"Help me choose\"\n    description: \"Not sure - guide me through questions\"\n  - label: \"Quick - fast overview\"\n    description: \"Just want to see what's here\"\n  - label: \"Deep - comprehensive analysis\"\n    description: \"Need thorough understanding\"\n  - label: \"Neither - let me explain differently\"\n    description: \"I'll describe what I need\"\n```\n\n### Phase 1: Exploration Goal\n\n```yaml\nquestion: \"What are you trying to understand?\"\nheader: \"Goal\"\noptions:\n  - label: \"Get oriented in the codebase\"\n    description: \"Quick overview of structure\"\n  - label: \"Understand how something works\"\n    description: \"Deep dive into specific area\"\n  - label: \"Map the architecture\"\n    description: \"Layers, dependencies, patterns\"\n  - label: \"Find where something is\"\n    description: \"Locate specific code\u002Ffunctionality\"\n```\n\n**Mapping:**\n- \"Get oriented\" → quick depth\n- \"Understand how\" → deep depth\n- \"Map architecture\" → architecture depth\n- \"Find where\" → quick with --focus\n\n### Phase 2: Scope\n\n```yaml\nquestion: \"What area should I focus on?\"\nheader: \"Focus\"\noptions:\n  - label: \"Entire codebase\"\n    description: \"Explore everything\"\n  - label: \"Specific directory or module\"\n    description: \"I'll specify the path\"\n  - label: \"Specific concept\u002Ffeature\"\n    description: \"e.g., 'authentication', 'API routes'\"\n```\n\nIf \"Specific directory\" or \"Specific concept\" → ask follow-up for the path\u002Fkeyword.\n\n### Phase 3: Output Format\n\n```yaml\nquestion: \"What should I produce?\"\nheader: \"Output\"\noptions:\n  - label: \"Just tell me what you find\"\n    description: \"Interactive summary in chat\"\n  - label: \"Create a documentation file\"\n    description: \"Write to thoughts\u002Fshared\u002Fdocs\u002F\"\n  - label: \"Create handoff for implementation\"\n    description: \"Prepare context for coding agent\"\n```\n\n**Mapping:**\n- \"Documentation file\" → --output doc\n- \"Handoff for implementation\" → --output handoff\n\n### Phase 4: Entry Point (Architecture only)\n\nIf architecture depth selected:\n\n```yaml\nquestion: \"Where should I start the analysis?\"\nheader: \"Entry point\"\noptions:\n  - label: \"Auto-detect (main, cli, app)\"\n    description: \"Find common entry points\"\n  - label: \"Specific function\u002Ffile\"\n    description: \"I'll specify the entry point\"\n```\n\n### Summary Before Execution\n\n```\nBased on your answers, I'll run:\n\n**Depth:** deep\n**Focus:** \"authentication\"\n**Output:** handoff\n**Path:** src\u002F\n\nProceed? [Yes \u002F Adjust settings]\n```\n\n### Depths\n\n| Depth | Time | What it does |\n|-------|------|--------------|\n| `quick` | ~1 min | tldr-explorer only - fast structure overview |\n| `deep` | ~5 min | onboard + tldr-explorer + research-codebase + write doc |\n| `architecture` | ~3 min | tldr arch + call graph + layer mapping + circular dep detection |\n\n### Options\n\n| Option | Description | Example |\n|--------|-------------|---------|\n| `--focus \"area\"` | Focus on specific area | `--focus \"auth\"`, `--focus \"api\"` |\n| `--output handoff` | Create handoff for next agent | `--output handoff` |\n| `--output doc` | Create documentation file | `--output doc` |\n| `--entry \"func\"` | Start from specific entry point | `--entry \"main\"`, `--entry \"process_request\"` |\n\n## Examples\n\n```bash\n# Quick structure overview\n\u002Fexplore quick\n\n# Deep exploration focused on auth\n\u002Fexplore deep --focus \"auth\" --output doc\n\n# Architecture analysis from specific entry\n\u002Fexplore architecture --entry \"cli\" --output handoff\n\n# Quick focused exploration\n\u002Fexplore quick --focus \"hooks\"\n```\n\n## Workflow Details\n\n### Quick Depth\n\nFast structure overview using tldr-explorer. Best for:\n- Initial orientation\n- Quick questions about structure\n- Finding where things are\n\n**Steps:**\n1. Run `tldr tree` for file structure\n2. Run `tldr structure` for codemaps\n3. If `--focus` provided, run `tldr search` for targeted results\n4. Return summary\n\n**Commands:**\n```bash\n# 1. File tree\ntldr tree ${PATH:-src\u002F} --ext .py\n\n# 2. Code structure\ntldr structure ${PATH:-src\u002F} --lang python\n\n# 3. Focused search (if --focus provided)\ntldr search \"${FOCUS}\" ${PATH:-src\u002F}\n```\n\n### Deep Depth\n\nComprehensive exploration with documentation output. Best for:\n- First time in a codebase\n- Preparing for major work\n- Creating reference documentation\n\n**Steps:**\n1. Check if onboarded (look for `.claude\u002Fcache\u002Ftldr\u002F`), if not run onboard\n2. Run tldr-explorer for structure\n3. Spawn research-codebase agent for patterns\n4. Write findings to doc or handoff\n\n**Subprocess:**\n```\n# 1. Onboard check\nif [ ! -f .claude\u002Fcache\u002Ftldr\u002Farch.json ]; then\n    # Spawn onboard agent\nfi\n\n# 2. Structure analysis\ntldr structure src\u002F --lang python\ntldr calls src\u002F\n\n# 3. Research patterns (via scout agent)\nTask: research-codebase → \"Document existing patterns in ${FOCUS:-codebase}\"\n\n# 4. Write output\n→ thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-explore-{focus}.md\n→ OR thoughts\u002Fshared\u002Fhandoffs\u002F{session}\u002Fexplore-{focus}.yaml\n```\n\n### Architecture Depth\n\nArchitecture-focused analysis with layer detection. Best for:\n- Understanding system boundaries\n- Preparing for refactoring\n- Identifying coupling issues\n\n**Steps:**\n1. Run `tldr arch` for layer detection\n2. Run `tldr calls` for cross-file call graph\n3. Analyze entry\u002Fmiddle\u002Fleaf layers\n4. Detect circular dependencies\n5. Map architectural boundaries\n\n**Commands:**\n```bash\n# 1. Architecture detection\ntldr arch ${PATH:-src\u002F}\n# Returns: entry_layer, middle_layer, leaf_layer, circular_deps\n\n# 2. Call graph\ntldr calls ${PATH:-src\u002F}\n# Returns: edges, nodes\n\n# 3. Impact analysis from entry point (if --entry provided)\ntldr impact ${ENTRY} ${PATH:-src\u002F} --depth 3\n```\n\n**Output Structure:**\n```yaml\nlayers:\n  entry: [routes.py, cli.py, main.py]  # Controllers\u002Fhandlers\n  middle: [services.py, auth.py]        # Business logic\n  leaf: [utils.py, helpers.py]          # Utilities\n\ncall_graph:\n  total_edges: 142\n  hot_paths: [process_request → validate → authorize]\n\ncircular_deps:\n  - [module_a, module_b]  # A imports B, B imports A\n\nboundaries:\n  - name: API layer\n    files: [src\u002Fapi\u002F*]\n    calls_to: [src\u002Fservices\u002F*]\n```\n\n## Output Formats\n\n### --output doc\n\nCreates: `thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-explore-{focus}.md`\n\n```markdown\n---\ndate: {ISO timestamp}\ntype: exploration\ndepth: {quick|deep|architecture}\nfocus: {focus area or \"full\"}\ncommit: {git hash}\n---\n\n# Codebase Exploration: {focus}\n\n## Summary\n{High-level findings}\n\n## Structure\n{File tree \u002F codemaps}\n\n## Architecture\n{Layer analysis - for architecture depth}\n\n## Key Components\n{Important files and their roles}\n\n## Patterns Found\n{Existing patterns - for deep depth}\n\n## References\n- `path\u002Fto\u002Ffile.py:line` - Description\n```\n\n### --output handoff\n\nCreates: `thoughts\u002Fshared\u002Fhandoffs\u002F{session}\u002Fexplore-{focus}.yaml`\n\n```yaml\n---\ntype: exploration\nts: {ISO timestamp}\ndepth: {quick|deep|architecture}\nfocus: {focus area}\ncommit: {git hash}\n---\n\nsummary: {One-line summary of findings}\n\nstructure:\n  entry_points: [{main.py}, {cli.py}]\n  key_modules: [{auth.py}, {routes.py}]\n  test_coverage: [{tests\u002F}]\n\narchitecture:\n  layers:\n    entry: [{files}]\n    middle: [{files}]\n    leaf: [{files}]\n  circular_deps: [{pairs}]\n\nfindings:\n  - {key finding with file:line}\n\nnext_steps:\n  - {Recommended action based on exploration}\n\nrefs:\n  - path: {file.py}\n    role: {what it does}\n```\n\n## Integration with \u002Fbuild\n\nThe explore skill is designed to feed into `\u002Fbuild brownfield`:\n\n```bash\n# Step 1: Explore to understand\n\u002Fexplore architecture --output handoff\n\n# Step 2: Build with context from exploration\n\u002Fbuild brownfield --from-handoff thoughts\u002Fshared\u002Fhandoffs\u002Fsession\u002Fexplore-full.yaml\n```\n\n## Implementation\n\nWhen user invokes `\u002Fexplore \u003Cdepth> [options]`:\n\n### Parse Arguments\n```python\ndepth = args[0]  # quick | deep | architecture\nfocus = extract_option(args, \"--focus\")\noutput = extract_option(args, \"--output\")  # handoff | doc\nentry = extract_option(args, \"--entry\")\n```\n\n### Execute Based on Depth\n\n**Quick:**\n```bash\n# Just tldr commands, no agents\ntldr tree ${src_dir} --ext .py\ntldr structure ${src_dir} --lang python\nif [ -n \"$focus\" ]; then\n    tldr search \"$focus\" ${src_dir}\nfi\n```\n\n**Deep:**\n```bash\n# 1. Check\u002Frun onboard\nif [ ! -f .claude\u002Fcache\u002Ftldr\u002Fmeta.json ]; then\n    # Spawn onboard agent via Task tool\nfi\n\n# 2. Structure\ntldr structure src\u002F --lang python\n\n# 3. Research (spawn scout agent)\n# Task tool with subagent_type: \"scout\"\n# Prompt: \"Research patterns in ${focus:-codebase}\"\n\n# 4. Write output\n# → doc or handoff based on --output\n```\n\n**Architecture:**\n```bash\n# 1. Arch detection\narch_output=$(tldr arch ${src_dir})\n\n# 2. Call graph\ncalls_output=$(tldr calls ${src_dir})\n\n# 3. Impact from entry (if provided)\nif [ -n \"$entry\" ]; then\n    impact_output=$(tldr impact $entry ${src_dir} --depth 3)\nfi\n\n# 4. Synthesize and write output\n```\n\n## Key Principles\n\n1. **READ-ONLY** - This skill never modifies code\n2. **Uses scout, not Explore** - Per project rules, scout (Sonnet) over Explore (Haiku)\n3. **Token-efficient** - Uses tldr commands (95% savings over raw reads)\n4. **Outputs to shared locations** - `thoughts\u002Fshared\u002Fresearch\u002F` or handoff directory\n5. **Entry point to \u002Fbuild** - Exploration handoffs feed into brownfield builds\n\n## Related Skills\n\n| Skill | When to Use |\n|-------|-------------|\n| **tldr-explorer** | Direct tldr commands (used internally by explore) |\n| **tldr-code** | Specific analysis commands (cfg, dfg, slice) |\n| **onboard** | First-time project setup (used by deep depth) |\n| **research-codebase** | Pattern documentation (used by deep depth) |\n| **create_handoff** | Handoff format (used by --output handoff) |\n\n## Troubleshooting\n\n**tldr not found:**\n```bash\n# Check if installed\nwhich tldr\n# Install if missing\nuv tool install llm-tldr\n# or: pip install llm-tldr\n```\n\n**No Python files found:**\n```bash\n# Check language, adjust --lang\ntldr structure src\u002F --lang typescript  # or go, rust\n```\n\n**Empty architecture output:**\n```bash\n# May need to specify src directory\ntldr arch .\u002F  # Current directory\ntldr arch src\u002F  # Explicit src\n```\n","# Explore - Internal Codebase Exploration\n\nMeta-skill for exploring an internal codebase at varying depths. READ-ONLY workflow - no code changes.\n\n## Usage\n\n```\n\u002Fexplore \u003Cdepth> [options]\n```\n\n## Question Flow (No Arguments)\n\nIf the user types just `\u002Fexplore` with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase.\n\n### Phase 0: Workflow Selection\n\n```yaml\nquestion: \"How would you like to explore?\"\nheader: \"Explore\"\noptions:\n  - label: \"Help me choose (Recommended)\"\n    description: \"I'll ask questions to pick the right exploration depth\"\n  - label: \"Quick - fast overview\"\n    description: \"Chain: tldr tree → tldr structure (~1 min)\"\n  - label: \"Deep - comprehensive analysis\"\n    description: \"Chain: onboard → tldr → research → document (~5 min)\"\n  - label: \"Architecture - layers & dependencies\"\n    description: \"Chain: tldr arch → call graph → layer mapping (~3 min)\"\n```\n\n**Mapping:**\n- \"Help me choose\" → Continue to Phase 1-4 questions\n- \"Quick\" → Set depth=quick, skip to Phase 2 (scope)\n- \"Deep\" → Set depth=deep, skip to Phase 2 (scope)\n- \"Architecture\" → Set depth=architecture, skip to Phase 2 (scope)\n\n**If Answer is Unclear (via \"Other\"):**\n```yaml\nquestion: \"I want to understand how deep you want to explore. Did you mean...\"\nheader: \"Clarify\"\noptions:\n  - label: \"Help me choose\"\n    description: \"Not sure - guide me through questions\"\n  - label: \"Quick - fast overview\"\n    description: \"Just want to see what's here\"\n  - label: \"Deep - comprehensive analysis\"\n    description: \"Need thorough understanding\"\n  - label: \"Neither - let me explain differently\"\n    description: \"I'll describe what I need\"\n```\n\n### Phase 1: Exploration Goal\n\n```yaml\nquestion: \"What are you trying to understand?\"\nheader: \"Goal\"\noptions:\n  - label: \"Get oriented in the codebase\"\n    description: \"Quick overview of structure\"\n  - label: \"Understand how something works\"\n    description: \"Deep dive into specific area\"\n  - label: \"Map the architecture\"\n    description: \"Layers, dependencies, patterns\"\n  - label: \"Find where something is\"\n    description: \"Locate specific code\u002Ffunctionality\"\n```\n\n**Mapping:**\n- \"Get oriented\" → quick depth\n- \"Understand how\" → deep depth\n- \"Map architecture\" → architecture depth\n- \"Find where\" → quick with --focus\n\n### Phase 2: Scope\n\n```yaml\nquestion: \"What area should I focus on?\"\nheader: \"Focus\"\noptions:\n  - label: \"Entire codebase\"\n    description: \"Explore everything\"\n  - label: \"Specific directory or module\"\n    description: \"I'll specify the path\"\n  - label: \"Specific concept\u002Ffeature\"\n    description: \"e.g., 'authentication', 'API routes'\"\n```\n\nIf \"Specific directory\" or \"Specific concept\" → ask follow-up for the path\u002Fkeyword.\n\n### Phase 3: Output Format\n\n```yaml\nquestion: \"What should I produce?\"\nheader: \"Output\"\noptions:\n  - label: \"Just tell me what you find\"\n    description: \"Interactive summary in chat\"\n  - label: \"Create a documentation file\"\n    description: \"Write to thoughts\u002Fshared\u002Fdocs\u002F\"\n  - label: \"Create handoff for implementation\"\n    description: \"Prepare context for coding agent\"\n```\n\n**Mapping:**\n- \"Documentation file\" → --output doc\n- \"Handoff for implementation\" → --output handoff\n\n### Phase 4: Entry Point (Architecture only)\n\nIf architecture depth selected:\n\n```yaml\nquestion: \"Where should I start the analysis?\"\nheader: \"Entry point\"\noptions:\n  - label: \"Auto-detect (main, cli, app)\"\n    description: \"Find common entry points\"\n  - label: \"Specific function\u002Ffile\"\n    description: \"I'll specify the entry point\"\n```\n\n### Summary Before Execution\n\n```\nBased on your answers, I'll run:\n\n**Depth:** deep\n**Focus:** \"authentication\"\n**Output:** handoff\n**Path:** src\u002F\n\nProceed? [Yes \u002F Adjust settings]\n```\n\n### Depths\n\n| Depth | Time | What it does |\n|-------|------|--------------|\n| `quick` | ~1 min | tldr-explorer only - fast structure overview |\n| `deep` | ~5 min | onboard + tldr-explorer + research-codebase + write doc |\n| `architecture` | ~3 min | tldr arch + call graph + layer mapping + circular dep detection |\n\n### Options\n\n| Option | Description | Example |\n|--------|-------------|---------|\n| `--focus \"area\"` | Focus on specific area | `--focus \"auth\"`, `--focus \"api\"` |\n| `--output handoff` | Create handoff for next agent | `--output handoff` |\n| `--output doc` | Create documentation file | `--output doc` |\n| `--entry \"func\"` | Start from specific entry point | `--entry \"main\"`, `--entry \"process_request\"` |\n\n## Examples\n\n```bash\n# Quick structure overview\n\u002Fexplore quick\n\n# Deep exploration focused on auth\n\u002Fexplore deep --focus \"auth\" --output doc\n\n# Architecture analysis from specific entry\n\u002Fexplore architecture --entry \"cli\" --output handoff\n\n# Quick focused exploration\n\u002Fexplore quick --focus \"hooks\"\n```\n\n## Workflow Details\n\n### Quick Depth\n\nFast structure overview using tldr-explorer. Best for:\n- Initial orientation\n- Quick questions about structure\n- Finding where things are\n\n**Steps:**\n1. Run `tldr tree` for file structure\n2. Run `tldr structure` for codemaps\n3. If `--focus` provided, run `tldr search` for targeted results\n4. Return summary\n\n**Commands:**\n```bash\n# 1. File tree\ntldr tree ${PATH:-src\u002F} --ext .py\n\n# 2. Code structure\ntldr structure ${PATH:-src\u002F} --lang python\n\n# 3. Focused search (if --focus provided)\ntldr search \"${FOCUS}\" ${PATH:-src\u002F}\n```\n\n### Deep Depth\n\nComprehensive exploration with documentation output. Best for:\n- First time in a codebase\n- Preparing for major work\n- Creating reference documentation\n\n**Steps:**\n1. Check if onboarded (look for `.claude\u002Fcache\u002Ftldr\u002F`), if not run onboard\n2. Run tldr-explorer for structure\n3. Spawn research-codebase agent for patterns\n4. Write findings to doc or handoff\n\n**Subprocess:**\n```\n# 1. Onboard check\nif [ ! -f .claude\u002Fcache\u002Ftldr\u002Farch.json ]; then\n    # Spawn onboard agent\nfi\n\n# 2. Structure analysis\ntldr structure src\u002F --lang python\ntldr calls src\u002F\n\n# 3. Research patterns (via scout agent)\nTask: research-codebase → \"Document existing patterns in ${FOCUS:-codebase}\"\n\n# 4. Write output\n→ thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-explore-{focus}.md\n→ OR thoughts\u002Fshared\u002Fhandoffs\u002F{session}\u002Fexplore-{focus}.yaml\n```\n\n### Architecture Depth\n\nArchitecture-focused analysis with layer detection. Best for:\n- Understanding system boundaries\n- Preparing for refactoring\n- Identifying coupling issues\n\n**Steps:**\n1. Run `tldr arch` for layer detection\n2. Run `tldr calls` for cross-file call graph\n3. Analyze entry\u002Fmiddle\u002Fleaf layers\n4. Detect circular dependencies\n5. Map architectural boundaries\n\n**Commands:**\n```bash\n# 1. Architecture detection\ntldr arch ${PATH:-src\u002F}\n# Returns: entry_layer, middle_layer, leaf_layer, circular_deps\n\n# 2. Call graph\ntldr calls ${PATH:-src\u002F}\n# Returns: edges, nodes\n\n# 3. Impact analysis from entry point (if --entry provided)\ntldr impact ${ENTRY} ${PATH:-src\u002F} --depth 3\n```\n\n**Output Structure:**\n```yaml\nlayers:\n  entry: [routes.py, cli.py, main.py]  # Controllers\u002Fhandlers\n  middle: [services.py, auth.py]        # Business logic\n  leaf: [utils.py, helpers.py]          # Utilities\n\ncall_graph:\n  total_edges: 142\n  hot_paths: [process_request → validate → authorize]\n\ncircular_deps:\n  - [module_a, module_b]  # A imports B, B imports A\n\nboundaries:\n  - name: API layer\n    files: [src\u002Fapi\u002F*]\n    calls_to: [src\u002Fservices\u002F*]\n```\n\n## Output Formats\n\n### --output doc\n\nCreates: `thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-explore-{focus}.md`\n\n```markdown\n---\ndate: {ISO timestamp}\ntype: exploration\ndepth: {quick|deep|architecture}\nfocus: {focus area or \"full\"}\ncommit: {git hash}\n---\n\n# Codebase Exploration: {focus}\n\n## Summary\n{High-level findings}\n\n## Structure\n{File tree \u002F codemaps}\n\n## Architecture\n{Layer analysis - for architecture depth}\n\n## Key Components\n{Important files and their roles}\n\n## Patterns Found\n{Existing patterns - for deep depth}\n\n## References\n- `path\u002Fto\u002Ffile.py:line` - Description\n```\n\n### --output handoff\n\nCreates: `thoughts\u002Fshared\u002Fhandoffs\u002F{session}\u002Fexplore-{focus}.yaml`\n\n```yaml\n---\ntype: exploration\nts: {ISO timestamp}\ndepth: {quick|deep|architecture}\nfocus: {focus area}\ncommit: {git hash}\n---\n\nsummary: {One-line summary of findings}\n\nstructure:\n  entry_points: [{main.py}, {cli.py}]\n  key_modules: [{auth.py}, {routes.py}]\n  test_coverage: [{tests\u002F}]\n\narchitecture:\n  layers:\n    entry: [{files}]\n    middle: [{files}]\n    leaf: [{files}]\n  circular_deps: [{pairs}]\n\nfindings:\n  - {key finding with file:line}\n\nnext_steps:\n  - {Recommended action based on exploration}\n\nrefs:\n  - path: {file.py}\n    role: {what it does}\n```\n\n## Integration with \u002Fbuild\n\nThe explore skill is designed to feed into `\u002Fbuild brownfield`:\n\n```bash\n# Step 1: Explore to understand\n\u002Fexplore architecture --output handoff\n\n# Step 2: Build with context from exploration\n\u002Fbuild brownfield --from-handoff thoughts\u002Fshared\u002Fhandoffs\u002Fsession\u002Fexplore-full.yaml\n```\n\n## Implementation\n\nWhen user invokes `\u002Fexplore \u003Cdepth> [options]`:\n\n### Parse Arguments\n```python\ndepth = args[0]  # quick | deep | architecture\nfocus = extract_option(args, \"--focus\")\noutput = extract_option(args, \"--output\")  # handoff | doc\nentry = extract_option(args, \"--entry\")\n```\n\n### Execute Based on Depth\n\n**Quick:**\n```bash\n# Just tldr commands, no agents\ntldr tree ${src_dir} --ext .py\ntldr structure ${src_dir} --lang python\nif [ -n \"$focus\" ]; then\n    tldr search \"$focus\" ${src_dir}\nfi\n```\n\n**Deep:**\n```bash\n# 1. Check\u002Frun onboard\nif [ ! -f .claude\u002Fcache\u002Ftldr\u002Fmeta.json ]; then\n    # Spawn onboard agent via Task tool\nfi\n\n# 2. Structure\ntldr structure src\u002F --lang python\n\n# 3. Research (spawn scout agent)\n# Task tool with subagent_type: \"scout\"\n# Prompt: \"Research patterns in ${focus:-codebase}\"\n\n# 4. Write output\n# → doc or handoff based on --output\n```\n\n**Architecture:**\n```bash\n# 1. Arch detection\narch_output=$(tldr arch ${src_dir})\n\n# 2. Call graph\ncalls_output=$(tldr calls ${src_dir})\n\n# 3. Impact from entry (if provided)\nif [ -n \"$entry\" ]; then\n    impact_output=$(tldr impact $entry ${src_dir} --depth 3)\nfi\n\n# 4. Synthesize and write output\n```\n\n## Key Principles\n\n1. **READ-ONLY** - This skill never modifies code\n2. **Uses scout, not Explore** - Per project rules, scout (Sonnet) over Explore (Haiku)\n3. **Token-efficient** - Uses tldr commands (95% savings over raw reads)\n4. **Outputs to shared locations** - `thoughts\u002Fshared\u002Fresearch\u002F` or handoff directory\n5. **Entry point to \u002Fbuild** - Exploration handoffs feed into brownfield builds\n\n## Related Skills\n\n| Skill | When to Use |\n|-------|-------------|\n| **tldr-explorer** | Direct tldr commands (used internally by explore) |\n| **tldr-code** | Specific analysis commands (cfg, dfg, slice) |\n| **onboard** | First-time project setup (used by deep depth) |\n| **research-codebase** | Pattern documentation (used by deep depth) |\n| **create_handoff** | Handoff format (used by --output handoff) |\n\n## Troubleshooting\n\n**tldr not found:**\n```bash\n# Check if installed\nwhich tldr\n# Install if missing\nuv tool install llm-tldr\n# or: pip install llm-tldr\n```\n\n**No Python files found:**\n```bash\n# Check language, adjust --lang\ntldr structure src\u002F --lang typescript  # or go, rust\n```\n\n**Empty architecture output:**\n```bash\n# May need to specify src directory\ntldr arch .\u002F  # Current directory\ntldr arch src\u002F  # Explicit src\n```\n",{"name":5,"keywords":43,"description":7,"allowed-tools":46},[5,44,29,45,34,22,31,26],"codebase","understand",[35,47,48,49,50,51],"Task","Read","Glob","Grep","Write","main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fexplore","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis","https:\u002F\u002Fgithub.com\u002Frubicanjr","linktr.ee\u002Ffinanskodu","Industrial Engineer & CIO @FinansKodu. Architecting AI-driven financial agents and autonomous workflows. 🏗️ Building systems, not just prompts.","2026-06-09 13:50:15",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add rubicanjr\u002FFinCognis --skill explore",{"tool":66,"command":67},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill explore",{"tool":69,"command":70},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill explore","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fexplore\u002FSKILL.md",true,[],[75,96,105,125,154,173],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":38},"01M6NWS9DAXJTADT4T5MB49X8W","workflow-router","Goal-based workflow orchestration - routes tasks to specialist agents based on user goals","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,95],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":38},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[98,103,104],"verification","false",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":38},"01M6NWS0XW9CVQZBDA1EGW0TWC","websocket-patterns","Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwebsocket-patterns\u002Fskill.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000015","视觉设计",[115,116,117,118,119,120,121,122,123,124],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":38},"01M6NWRDQDX9ZNETAWRRMQWV52","visual-verdict","Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS\u002FREVISE\u002FFAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-verdict\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[136,137,138,139,140,141,142,143,144,21,145,146,147,118,148,149,150,151,152,153],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","fixes","dimensions","frontend","development","qa","screenshot","returns","use","frontend development",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":38},"01M6NWR8HSNRS7MNDK2J02QYMN","verification-loop","Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[161,162,103,163,164,165,166,167,168,169,170,171,172],"verification loop","loop","lint","review","security","pr","system","diff","build","tests","diff review","types",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":38},"01M6NWR4HHSFR0VR5EXFRWA747","vector-db-patterns","Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvector-db-patterns\u002Fskill.md",[],[180,181,182,183,116,184,185,186,187,122,188,189,190,191,192,21,193,194],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]