[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NW7CBBK2C59F6D73FZX8Y2":3,"skill-same:01M6NW7CBBK2C59F6D73FZX8Y2":61},{"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":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6NW7CBBK2C59F6D73FZX8Y2","research",null,"Document codebase as-is with thoughts directory for historical context","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\u002Fresearch\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32],"directory","context","document","as","false","with","opus","for","codebase","2026-11-10 10:12:30",false,"---\nname: research\ndescription: Document codebase as-is with thoughts directory for historical context\nmodel: claude-opus-4-5-20251101\nuser-invocable: false\n---\n\n# Research Codebase\n\nYou are tasked with conducting comprehensive research across the codebase to answer user questions by spawning parallel sub-agents and synthesizing their findings.\n\n## CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY\n- DO NOT suggest improvements or changes unless the user explicitly asks for them\n- DO NOT perform root cause analysis unless the user explicitly asks for them\n- DO NOT propose future enhancements unless the user explicitly asks for them\n- DO NOT critique the implementation or identify problems\n- DO NOT recommend refactoring, optimization, or architectural changes\n- ONLY describe what exists, where it exists, how it works, and how components interact\n- You are creating a technical map\u002Fdocumentation of the existing system\n\n## Initial Setup:\n\nWhen this command is invoked, respond with:\n```\nI'm ready to research the codebase. Please provide your research question or area of interest, and I'll analyze it thoroughly by exploring relevant components and connections.\n```\n\nThen wait for the user's research query.\n\n## Steps to follow after receiving the research query:\n\n1. **Read any directly mentioned files first:**\n   - If the user mentions specific files (tickets, docs, JSON), read them FULLY first\n   - **IMPORTANT**: Use the Read tool WITHOUT limit\u002Foffset parameters to read entire files\n   - **CRITICAL**: Read these files yourself in the main context before spawning any sub-tasks\n   - This ensures you have full context before decomposing the research\n\n2. **Analyze and decompose the research question:**\n   - Break down the user's query into composable research areas\n   - Take time to ultrathink about the underlying patterns, connections, and architectural implications the user might be seeking\n   - Identify specific components, patterns, or concepts to investigate\n   - Create a research plan using TodoWrite to track all subtasks\n   - Consider which directories, files, or architectural patterns are relevant\n\n3. **Spawn parallel sub-agent tasks for comprehensive research:**\n   - Create multiple Task agents to research different aspects concurrently\n   - We now have specialized agents that know how to do specific research tasks:\n\n   **For codebase research:**\n   - Use the **scout** agent for comprehensive codebase exploration (combines locating, analyzing, and pattern finding)\n\n   **IMPORTANT**: All agents are documentarians, not critics. They will describe what exists without suggesting improvements or identifying issues.\n\n   **For thoughts directory:**\n   - Use the **thoughts-locator** agent to discover what documents exist about the topic\n   - Use the **thoughts-analyzer** agent to extract key insights from specific documents (only the most relevant ones)\n\n   **For web research (only if user explicitly asks):**\n   - Use the **web-search-researcher** agent for external documentation and resources\n   - IF you use web-research agents, instruct them to return LINKS with their findings, and please INCLUDE those links in your final report\n\n   **For Linear tickets (if relevant):**\n   - Use the **linear-ticket-reader** agent to get full details of a specific ticket\n   - Use the **linear-searcher** agent to find related tickets or historical context\n\n   The key is to use these agents intelligently:\n   - Start with locator agents to find what exists\n   - Then use analyzer agents on the most promising findings to document how they work\n   - Run multiple agents in parallel when they're searching for different things\n   - Each agent knows its job - just tell it what you're looking for\n   - Don't write detailed prompts about HOW to search - the agents already know\n   - Remind agents they are documenting, not evaluating or improving\n\n4. **Wait for all sub-agents to complete and synthesize findings:**\n   - IMPORTANT: Wait for ALL sub-agent tasks to complete before proceeding\n   - Compile all sub-agent results (both codebase and thoughts findings)\n   - Prioritize live codebase findings as primary source of truth\n   - Use thoughts\u002F findings as supplementary historical context\n   - Connect findings across different components\n   - Include specific file paths and line numbers for reference\n   - Verify all thoughts\u002F paths are correct (e.g., thoughts\u002Fallison\u002F not thoughts\u002Fshared\u002F for personal files)\n   - Highlight patterns, connections, and architectural decisions\n   - Answer the user's specific questions with concrete evidence\n\n5. **Gather metadata for the research document:**\n   - Run the `hack\u002Fspec_metadata.sh` script to generate all relevant metadata\n   - Filename: `thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-ENG-XXXX-description.md`\n     - Format: `YYYY-MM-DD-ENG-XXXX-description.md` where:\n       - YYYY-MM-DD is today's date\n       - ENG-XXXX is the ticket number (omit if no ticket)\n       - description is a brief kebab-case description of the research topic\n     - Examples:\n       - With ticket: `2025-01-08-ENG-1478-parent-child-tracking.md`\n       - Without ticket: `2025-01-08-authentication-flow.md`\n\n6. **Generate research document:**\n   - Ensure directory exists: `mkdir -p thoughts\u002Fshared\u002Fresearch`\n   - Use the metadata gathered in step 4\n   - Structure the document with YAML frontmatter followed by content:\n     ```markdown\n     ---\n     date: [Current date and time with timezone in ISO format]\n     researcher: [Researcher name from thoughts status]\n     git_commit: [Current commit hash]\n     branch: [Current branch name]\n     repository: [Repository name]\n     topic: \"[User's Question\u002FTopic]\"\n     tags: [research, codebase, relevant-component-names]\n     status: complete\n     last_updated: [Current date in YYYY-MM-DD format]\n     last_updated_by: [Researcher name]\n     ---\n\n     # Research: [User's Question\u002FTopic]\n\n     **Date**: [Current date and time with timezone from step 4]\n     **Researcher**: [Researcher name from thoughts status]\n     **Git Commit**: [Current commit hash from step 4]\n     **Branch**: [Current branch name from step 4]\n     **Repository**: [Repository name]\n\n     ## Research Question\n     [Original user query]\n\n     ## Summary\n     [High-level documentation of what was found, answering the user's question by describing what exists]\n\n     ## Detailed Findings\n\n     ### [Component\u002FArea 1]\n     - Description of what exists ([file.ext:line](link))\n     - How it connects to other components\n     - Current implementation details (without evaluation)\n\n     ### [Component\u002FArea 2]\n     ...\n\n     ## Code References\n     - `path\u002Fto\u002Ffile.py:123` - Description of what's there\n     - `another\u002Ffile.ts:45-67` - Description of the code block\n\n     ## Architecture Documentation\n     [Current patterns, conventions, and design implementations found in the codebase]\n\n     ## Historical Context (from thoughts\u002F)\n     [Relevant insights from thoughts\u002F directory with references]\n     - `thoughts\u002Fshared\u002Fsomething.md` - Historical decision about X\n     - `thoughts\u002Flocal\u002Fnotes.md` - Past exploration of Y\n     Note: Paths exclude \"searchable\u002F\" even if found there\n\n     ## Related Research\n     [Links to other research documents in thoughts\u002Fshared\u002Fresearch\u002F]\n\n     ## Open Questions\n     [Any areas that need further investigation]\n     ```\n\n7. **Add GitHub permalinks (if applicable):**\n   - Check if on main branch or if commit is pushed: `git branch --show-current` and `git status`\n   - If on main\u002Fmaster or pushed, generate GitHub permalinks:\n     - Get repo info: `gh repo view --json owner,name`\n     - Create permalinks: `https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fblob\u002F{commit}\u002F{file}#L{line}`\n   - Replace local file references with permalinks in the document\n\n8. **Present findings:**\n   - Present a concise summary of findings to the user\n   - Include key file references for easy navigation\n   - Ask if they have follow-up questions or need clarification\n\n9. **Handle follow-up questions:**\n   - If the user has follow-up questions, append to the same research document\n   - Update the frontmatter fields `last_updated` and `last_updated_by` to reflect the update\n   - Add `last_updated_note: \"Added follow-up research for [brief description]\"` to frontmatter\n   - Add a new section: `## Follow-up Research [timestamp]`\n   - Spawn new sub-agents as needed for additional investigation\n   - Continue updating the document and syncing\n\n## Important notes:\n- Always use parallel Task agents to maximize efficiency and minimize context usage\n- Always run fresh codebase research - never rely solely on existing research documents\n- The thoughts\u002F directory provides historical context to supplement live findings\n- Focus on finding concrete file paths and line numbers for developer reference\n- Research documents should be self-contained with all necessary context\n- Each sub-agent prompt should be specific and focused on read-only documentation operations\n- Document cross-component connections and how systems interact\n- Include temporal context (when the research was conducted)\n- Link to GitHub when possible for permanent references\n- Keep the main agent focused on synthesis, not deep file reading\n- Have sub-agents document examples and usage patterns as they exist\n- Explore all of thoughts\u002F directory, not just research subdirectory\n- **CRITICAL**: You and all sub-agents are documentarians, not evaluators\n- **REMEMBER**: Document what IS, not what SHOULD BE\n- **NO RECOMMENDATIONS**: Only describe the current state of the codebase\n- **File reading**: Always read mentioned files FULLY (no limit\u002Foffset) before spawning sub-tasks\n- **Critical ordering**: Follow the numbered steps exactly\n  - ALWAYS read mentioned files first before spawning sub-tasks (step 1)\n  - ALWAYS wait for all sub-agents to complete before synthesizing (step 4)\n  - ALWAYS gather metadata before writing the document (step 5 before step 6)\n  - NEVER write the research document with placeholder values\n- **Path handling**: The thoughts\u002Fsearchable\u002F directory contains hard links for searching\n  - Always document paths by removing ONLY \"searchable\u002F\" - preserve all other subdirectories\n  - Examples of correct transformations:\n    - `thoughts\u002Fsearchable\u002Fallison\u002Fold_stuff\u002Fnotes.md` → `thoughts\u002Fallison\u002Fold_stuff\u002Fnotes.md`\n    - `thoughts\u002Fsearchable\u002Fshared\u002Fprs\u002F123.md` → `thoughts\u002Fshared\u002Fprs\u002F123.md`\n    - `thoughts\u002Fsearchable\u002Fglobal\u002Fshared\u002Ftemplates.md` → `thoughts\u002Fglobal\u002Fshared\u002Ftemplates.md`\n  - NEVER change allison\u002F to shared\u002F or vice versa - preserve the exact directory structure\n  - This ensures paths are correct for editing and navigation\n- **Frontmatter consistency**:\n  - Always include frontmatter at the beginning of research documents\n  - Keep frontmatter fields consistent across all research documents\n  - Update frontmatter when adding follow-up research\n  - Use snake_case for multi-word field names (e.g., `last_updated`, `git_commit`)\n  - Tags should be relevant to the research topic and components studied\n","# Research Codebase\n\nYou are tasked with conducting comprehensive research across the codebase to answer user questions by spawning parallel sub-agents and synthesizing their findings.\n\n## CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY\n- DO NOT suggest improvements or changes unless the user explicitly asks for them\n- DO NOT perform root cause analysis unless the user explicitly asks for them\n- DO NOT propose future enhancements unless the user explicitly asks for them\n- DO NOT critique the implementation or identify problems\n- DO NOT recommend refactoring, optimization, or architectural changes\n- ONLY describe what exists, where it exists, how it works, and how components interact\n- You are creating a technical map\u002Fdocumentation of the existing system\n\n## Initial Setup:\n\nWhen this command is invoked, respond with:\n```\nI'm ready to research the codebase. Please provide your research question or area of interest, and I'll analyze it thoroughly by exploring relevant components and connections.\n```\n\nThen wait for the user's research query.\n\n## Steps to follow after receiving the research query:\n\n1. **Read any directly mentioned files first:**\n   - If the user mentions specific files (tickets, docs, JSON), read them FULLY first\n   - **IMPORTANT**: Use the Read tool WITHOUT limit\u002Foffset parameters to read entire files\n   - **CRITICAL**: Read these files yourself in the main context before spawning any sub-tasks\n   - This ensures you have full context before decomposing the research\n\n2. **Analyze and decompose the research question:**\n   - Break down the user's query into composable research areas\n   - Take time to ultrathink about the underlying patterns, connections, and architectural implications the user might be seeking\n   - Identify specific components, patterns, or concepts to investigate\n   - Create a research plan using TodoWrite to track all subtasks\n   - Consider which directories, files, or architectural patterns are relevant\n\n3. **Spawn parallel sub-agent tasks for comprehensive research:**\n   - Create multiple Task agents to research different aspects concurrently\n   - We now have specialized agents that know how to do specific research tasks:\n\n   **For codebase research:**\n   - Use the **scout** agent for comprehensive codebase exploration (combines locating, analyzing, and pattern finding)\n\n   **IMPORTANT**: All agents are documentarians, not critics. They will describe what exists without suggesting improvements or identifying issues.\n\n   **For thoughts directory:**\n   - Use the **thoughts-locator** agent to discover what documents exist about the topic\n   - Use the **thoughts-analyzer** agent to extract key insights from specific documents (only the most relevant ones)\n\n   **For web research (only if user explicitly asks):**\n   - Use the **web-search-researcher** agent for external documentation and resources\n   - IF you use web-research agents, instruct them to return LINKS with their findings, and please INCLUDE those links in your final report\n\n   **For Linear tickets (if relevant):**\n   - Use the **linear-ticket-reader** agent to get full details of a specific ticket\n   - Use the **linear-searcher** agent to find related tickets or historical context\n\n   The key is to use these agents intelligently:\n   - Start with locator agents to find what exists\n   - Then use analyzer agents on the most promising findings to document how they work\n   - Run multiple agents in parallel when they're searching for different things\n   - Each agent knows its job - just tell it what you're looking for\n   - Don't write detailed prompts about HOW to search - the agents already know\n   - Remind agents they are documenting, not evaluating or improving\n\n4. **Wait for all sub-agents to complete and synthesize findings:**\n   - IMPORTANT: Wait for ALL sub-agent tasks to complete before proceeding\n   - Compile all sub-agent results (both codebase and thoughts findings)\n   - Prioritize live codebase findings as primary source of truth\n   - Use thoughts\u002F findings as supplementary historical context\n   - Connect findings across different components\n   - Include specific file paths and line numbers for reference\n   - Verify all thoughts\u002F paths are correct (e.g., thoughts\u002Fallison\u002F not thoughts\u002Fshared\u002F for personal files)\n   - Highlight patterns, connections, and architectural decisions\n   - Answer the user's specific questions with concrete evidence\n\n5. **Gather metadata for the research document:**\n   - Run the `hack\u002Fspec_metadata.sh` script to generate all relevant metadata\n   - Filename: `thoughts\u002Fshared\u002Fresearch\u002FYYYY-MM-DD-ENG-XXXX-description.md`\n     - Format: `YYYY-MM-DD-ENG-XXXX-description.md` where:\n       - YYYY-MM-DD is today's date\n       - ENG-XXXX is the ticket number (omit if no ticket)\n       - description is a brief kebab-case description of the research topic\n     - Examples:\n       - With ticket: `2025-01-08-ENG-1478-parent-child-tracking.md`\n       - Without ticket: `2025-01-08-authentication-flow.md`\n\n6. **Generate research document:**\n   - Ensure directory exists: `mkdir -p thoughts\u002Fshared\u002Fresearch`\n   - Use the metadata gathered in step 4\n   - Structure the document with YAML frontmatter followed by content:\n     ```markdown\n     ---\n     date: [Current date and time with timezone in ISO format]\n     researcher: [Researcher name from thoughts status]\n     git_commit: [Current commit hash]\n     branch: [Current branch name]\n     repository: [Repository name]\n     topic: \"[User's Question\u002FTopic]\"\n     tags: [research, codebase, relevant-component-names]\n     status: complete\n     last_updated: [Current date in YYYY-MM-DD format]\n     last_updated_by: [Researcher name]\n     ---\n\n     # Research: [User's Question\u002FTopic]\n\n     **Date**: [Current date and time with timezone from step 4]\n     **Researcher**: [Researcher name from thoughts status]\n     **Git Commit**: [Current commit hash from step 4]\n     **Branch**: [Current branch name from step 4]\n     **Repository**: [Repository name]\n\n     ## Research Question\n     [Original user query]\n\n     ## Summary\n     [High-level documentation of what was found, answering the user's question by describing what exists]\n\n     ## Detailed Findings\n\n     ### [Component\u002FArea 1]\n     - Description of what exists ([file.ext:line](link))\n     - How it connects to other components\n     - Current implementation details (without evaluation)\n\n     ### [Component\u002FArea 2]\n     ...\n\n     ## Code References\n     - `path\u002Fto\u002Ffile.py:123` - Description of what's there\n     - `another\u002Ffile.ts:45-67` - Description of the code block\n\n     ## Architecture Documentation\n     [Current patterns, conventions, and design implementations found in the codebase]\n\n     ## Historical Context (from thoughts\u002F)\n     [Relevant insights from thoughts\u002F directory with references]\n     - `thoughts\u002Fshared\u002Fsomething.md` - Historical decision about X\n     - `thoughts\u002Flocal\u002Fnotes.md` - Past exploration of Y\n     Note: Paths exclude \"searchable\u002F\" even if found there\n\n     ## Related Research\n     [Links to other research documents in thoughts\u002Fshared\u002Fresearch\u002F]\n\n     ## Open Questions\n     [Any areas that need further investigation]\n     ```\n\n7. **Add GitHub permalinks (if applicable):**\n   - Check if on main branch or if commit is pushed: `git branch --show-current` and `git status`\n   - If on main\u002Fmaster or pushed, generate GitHub permalinks:\n     - Get repo info: `gh repo view --json owner,name`\n     - Create permalinks: `https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fblob\u002F{commit}\u002F{file}#L{line}`\n   - Replace local file references with permalinks in the document\n\n8. **Present findings:**\n   - Present a concise summary of findings to the user\n   - Include key file references for easy navigation\n   - Ask if they have follow-up questions or need clarification\n\n9. **Handle follow-up questions:**\n   - If the user has follow-up questions, append to the same research document\n   - Update the frontmatter fields `last_updated` and `last_updated_by` to reflect the update\n   - Add `last_updated_note: \"Added follow-up research for [brief description]\"` to frontmatter\n   - Add a new section: `## Follow-up Research [timestamp]`\n   - Spawn new sub-agents as needed for additional investigation\n   - Continue updating the document and syncing\n\n## Important notes:\n- Always use parallel Task agents to maximize efficiency and minimize context usage\n- Always run fresh codebase research - never rely solely on existing research documents\n- The thoughts\u002F directory provides historical context to supplement live findings\n- Focus on finding concrete file paths and line numbers for developer reference\n- Research documents should be self-contained with all necessary context\n- Each sub-agent prompt should be specific and focused on read-only documentation operations\n- Document cross-component connections and how systems interact\n- Include temporal context (when the research was conducted)\n- Link to GitHub when possible for permanent references\n- Keep the main agent focused on synthesis, not deep file reading\n- Have sub-agents document examples and usage patterns as they exist\n- Explore all of thoughts\u002F directory, not just research subdirectory\n- **CRITICAL**: You and all sub-agents are documentarians, not evaluators\n- **REMEMBER**: Document what IS, not what SHOULD BE\n- **NO RECOMMENDATIONS**: Only describe the current state of the codebase\n- **File reading**: Always read mentioned files FULLY (no limit\u002Foffset) before spawning sub-tasks\n- **Critical ordering**: Follow the numbered steps exactly\n  - ALWAYS read mentioned files first before spawning sub-tasks (step 1)\n  - ALWAYS wait for all sub-agents to complete before synthesizing (step 4)\n  - ALWAYS gather metadata before writing the document (step 5 before step 6)\n  - NEVER write the research document with placeholder values\n- **Path handling**: The thoughts\u002Fsearchable\u002F directory contains hard links for searching\n  - Always document paths by removing ONLY \"searchable\u002F\" - preserve all other subdirectories\n  - Examples of correct transformations:\n    - `thoughts\u002Fsearchable\u002Fallison\u002Fold_stuff\u002Fnotes.md` → `thoughts\u002Fallison\u002Fold_stuff\u002Fnotes.md`\n    - `thoughts\u002Fsearchable\u002Fshared\u002Fprs\u002F123.md` → `thoughts\u002Fshared\u002Fprs\u002F123.md`\n    - `thoughts\u002Fsearchable\u002Fglobal\u002Fshared\u002Ftemplates.md` → `thoughts\u002Fglobal\u002Fshared\u002Ftemplates.md`\n  - NEVER change allison\u002F to shared\u002F or vice versa - preserve the exact directory structure\n  - This ensures paths are correct for editing and navigation\n- **Frontmatter consistency**:\n  - Always include frontmatter at the beginning of research documents\n  - Keep frontmatter fields consistent across all research documents\n  - Update frontmatter when adding follow-up research\n  - Use snake_case for multi-word field names (e.g., `last_updated`, `git_commit`)\n  - Tags should be relevant to the research topic and components studied\n",{"name":5,"model":38,"description":7,"user-invocable":34},"claude-opus-4-5-20251101","main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fresearch","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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add rubicanjr\u002FFinCognis --skill research",{"tool":53,"command":54},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill research",{"tool":56,"command":57},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002FSKILL.md",true,[],[62,81,89,109,138,157],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":71,"publishedAt":33},"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",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[72,73,74,75,76,77,78,79,80],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":33},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[83,88,28],"verification",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":98,"publishedAt":33},"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",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[99,100,101,102,103,104,105,106,107,108],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":119,"publishedAt":33},"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",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,125,126,127,128,31,129,130,131,102,132,133,134,135,136,137],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","fixes","dimensions","frontend","development","qa","screenshot","returns","use","frontend development",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":33},"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",[],[145,146,88,147,148,149,150,151,152,153,154,155,156],"verification loop","loop","lint","review","security","pr","system","diff","build","tests","diff review","types",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":33},"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",[],[164,165,166,167,100,168,169,170,171,106,172,173,174,175,176,31,177,178],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]