[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTF47ESD715N9P583TGNAY":3,"skill-same:01M6NTF47ESD715N9P583TGNAY":71},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6NTF47ESD715N9P583TGNAY","compound-learnings",null,"Transform session learnings into permanent capabilities (skills, rules, agents). Use when asked to \"improve setup\", \"learn from sessions\", \"compound learnings\", or \"what patterns should become skills\".","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\u002Fcompound-learnings\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"compound learnings","compound","learnings","write","transform","patterns","use","session","edit","sessions","read","grep","Rules","improve","Bash","capabilities","learn","setup","2026-11-10 10:12:30",false,"---\nname: compound-learnings\ndescription: Transform session learnings into permanent capabilities (skills, rules, agents). Use when asked to \"improve setup\", \"learn from sessions\", \"compound learnings\", or \"what patterns should become skills\".\nallowed-tools: [Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion]\n---\n\n# Compound Learnings\n\nTransform ephemeral session learnings into permanent, compounding capabilities.\n\n## When to Use\n\n- \"What should I learn from recent sessions?\"\n- \"Improve my setup based on recent work\"\n- \"Turn learnings into skills\u002Frules\"\n- \"What patterns should become permanent?\"\n- \"Compound my learnings\"\n\n## Process\n\n### Step 1: Gather Learnings\n\n```bash\n# List learnings (most recent first)\nls -t $CLAUDE_PROJECT_DIR\u002F.claude\u002Fcache\u002Flearnings\u002F*.md | head -20\n\n# Count total\nls $CLAUDE_PROJECT_DIR\u002F.claude\u002Fcache\u002Flearnings\u002F*.md | wc -l\n```\n\nRead the most recent 5-10 files (or specify a date range).\n\n### Step 2: Extract Patterns (Structured)\n\nFor each learnings file, extract entries from these specific sections:\n\n| Section Header | What to Extract |\n|----------------|-----------------|\n| `## Patterns` or `Reusable techniques` | Direct candidates for rules |\n| `**Takeaway:**` or `**Actionable takeaway:**` | Decision heuristics |\n| `## What Worked` | Success patterns |\n| `## What Failed` | Anti-patterns (invert to rules) |\n| `## Key Decisions` | Design principles |\n\nBuild a frequency table as you go:\n\n```markdown\n| Pattern | Sessions | Category |\n|---------|----------|----------|\n| \"Check artifacts before editing\" | abc, def, ghi | debugging |\n| \"Pass IDs explicitly\" | abc, def, ghi, jkl | reliability |\n```\n\n### Step 2b: Consolidate Similar Patterns\n\nBefore counting, merge patterns that express the same principle:\n\n**Example consolidation:**\n- \"Artifact-first debugging\"\n- \"Verify hook output by inspecting files\"\n- \"Filesystem-first debugging\"\n→ All express: **\"Observe outputs before editing code\"**\n\nUse the most general formulation. Update the frequency table.\n\n### Step 3: Detect Meta-Patterns\n\n**Critical step:** Look at what the learnings cluster around.\n\nIf >50% of patterns relate to one topic (e.g., \"hooks\", \"tracing\", \"async\"):\n→ That topic may need a **dedicated skill** rather than multiple rules\n→ One skill compounds better than five rules\n\nAsk yourself: *\"Is there a skill that would make all these rules unnecessary?\"*\n\n### Step 4: Categorize (Decision Tree)\n\nFor each pattern, determine artifact type:\n\n```\nIs it a sequence of commands\u002Fsteps?\n  → YES → SKILL (executable > declarative)\n  → NO ↓\n\nShould it run automatically on an event (SessionEnd, PostToolUse, etc.)?\n  → YES → HOOK (automatic > manual)\n  → NO ↓\n\nIs it \"when X, do Y\" or \"never do X\"?\n  → YES → RULE\n  → NO ↓\n\nDoes it enhance an existing agent workflow?\n  → YES → AGENT UPDATE\n  → NO → Skip (not worth capturing)\n```\n\n**Artifact Type Examples:**\n\n| Pattern | Type | Why |\n|---------|------|-----|\n| \"Run linting before commit\" | Hook (PreToolUse) | Automatic gate |\n| \"Extract learnings on session end\" | Hook (SessionEnd) | Automatic trigger |\n| \"Debug hooks step by step\" | Skill | Manual sequence |\n| \"Always pass IDs explicitly\" | Rule | Heuristic |\n\n### Step 5: Apply Signal Thresholds\n\n| Occurrences | Action |\n|-------------|--------|\n| 1 | Note but skip (unless critical failure) |\n| 2 | Consider - present to user |\n| 3+ | Strong signal - recommend creation |\n| 4+ | Definitely create |\n\n### Step 6: Propose Artifacts\n\nPresent each proposal in this format:\n\n```markdown\n---\n\n## Pattern: [Generalized Name]\n\n**Signal:** [N] sessions ([list session IDs])\n\n**Category:** [debugging \u002F reliability \u002F workflow \u002F etc.]\n\n**Artifact Type:** Rule \u002F Skill \u002F Agent Update\n\n**Rationale:** [Why this artifact type, why worth creating]\n\n**Draft Content:**\n\\`\\`\\`markdown\n[Actual content that would be written to file]\n\\`\\`\\`\n\n**File:** `.claude\u002Frules\u002F[name].md` or `.claude\u002Fskills\u002F[name]\u002FSKILL.md`\n\n---\n```\n\nUse `AskUserQuestion` to get approval for each artifact (or batch approval).\n\n### Step 7: Create Approved Artifacts\n\n#### For Rules:\n```bash\n# Write to rules directory\ncat > $CLAUDE_PROJECT_DIR\u002F.claude\u002Frules\u002F\u003Cname>.md \u003C\u003C 'EOF'\n# Rule Name\n\n[Context: why this rule exists, based on N sessions]\n\n## Pattern\n[The reusable principle]\n\n## DO\n- [Concrete action]\n\n## DON'T\n- [Anti-pattern]\n\n## Source Sessions\n- [session-id-1]: [what happened]\n- [session-id-2]: [what happened]\nEOF\n```\n\n#### For Skills:\nCreate `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` with:\n- Frontmatter (name, description, allowed-tools)\n- When to Use\n- Step-by-step instructions (executable)\n- Examples from the learnings\n\nAdd triggers to `skill-rules.json` if appropriate.\n\n#### For Hooks:\nCreate shell wrapper + TypeScript handler:\n\n```bash\n# Shell wrapper\ncat > $CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh \u003C\u003C 'EOF'\n#!\u002Fbin\u002Fbash\nset -e\ncd \"$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\"\ncat | node dist\u002F\u003Cname>.mjs\nEOF\nchmod +x $CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh\n```\n\nThen create `src\u002F\u003Cname>.ts`, build with esbuild, and register in `settings.json`:\n\n```json\n{\n  \"hooks\": {\n    \"EventName\": [{\n      \"hooks\": [{\n        \"type\": \"command\",\n        \"command\": \"$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh\"\n      }]\n    }]\n  }\n}\n```\n\n#### For Agent Updates:\nEdit existing agent in `.claude\u002Fagents\u002F\u003Cname>.md` to add the learned capability.\n\n### Step 8: Summary Report\n\n```markdown\n## Compounding Complete\n\n**Learnings Analyzed:** [N] sessions\n**Patterns Found:** [M]\n**Artifacts Created:** [K]\n\n### Created:\n- Rule: `explicit-identity.md` - Pass IDs explicitly across boundaries\n- Skill: `debug-hooks` - Hook debugging workflow\n\n### Skipped (insufficient signal):\n- \"Pattern X\" (1 occurrence)\n\n**Your setup is now permanently improved.**\n```\n\n## Quality Checks\n\nBefore creating any artifact:\n\n1. **Is it general enough?** Would it apply in other projects?\n2. **Is it specific enough?** Does it give concrete guidance?\n3. **Does it already exist?** Check `.claude\u002Frules\u002F` and `.claude\u002Fskills\u002F` first\n4. **Is it the right type?** Sequences → skills, heuristics → rules\n\n## Files Reference\n\n- Learnings: `.claude\u002Fcache\u002Flearnings\u002F*.md`\n- Skills: `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`\n- Rules: `.claude\u002Frules\u002F\u003Cname>.md`\n- Hooks: `.claude\u002Fhooks\u002F\u003Cname>.sh` + `src\u002F\u003Cname>.ts` + `dist\u002F\u003Cname>.mjs`\n- Agents: `.claude\u002Fagents\u002F\u003Cname>.md`\n- Skill triggers: `.claude\u002Fskills\u002Fskill-rules.json`\n- Hook registration: `.claude\u002Fsettings.json` → `hooks` section\n","# Compound Learnings\n\nTransform ephemeral session learnings into permanent, compounding capabilities.\n\n## When to Use\n\n- \"What should I learn from recent sessions?\"\n- \"Improve my setup based on recent work\"\n- \"Turn learnings into skills\u002Frules\"\n- \"What patterns should become permanent?\"\n- \"Compound my learnings\"\n\n## Process\n\n### Step 1: Gather Learnings\n\n```bash\n# List learnings (most recent first)\nls -t $CLAUDE_PROJECT_DIR\u002F.claude\u002Fcache\u002Flearnings\u002F*.md | head -20\n\n# Count total\nls $CLAUDE_PROJECT_DIR\u002F.claude\u002Fcache\u002Flearnings\u002F*.md | wc -l\n```\n\nRead the most recent 5-10 files (or specify a date range).\n\n### Step 2: Extract Patterns (Structured)\n\nFor each learnings file, extract entries from these specific sections:\n\n| Section Header | What to Extract |\n|----------------|-----------------|\n| `## Patterns` or `Reusable techniques` | Direct candidates for rules |\n| `**Takeaway:**` or `**Actionable takeaway:**` | Decision heuristics |\n| `## What Worked` | Success patterns |\n| `## What Failed` | Anti-patterns (invert to rules) |\n| `## Key Decisions` | Design principles |\n\nBuild a frequency table as you go:\n\n```markdown\n| Pattern | Sessions | Category |\n|---------|----------|----------|\n| \"Check artifacts before editing\" | abc, def, ghi | debugging |\n| \"Pass IDs explicitly\" | abc, def, ghi, jkl | reliability |\n```\n\n### Step 2b: Consolidate Similar Patterns\n\nBefore counting, merge patterns that express the same principle:\n\n**Example consolidation:**\n- \"Artifact-first debugging\"\n- \"Verify hook output by inspecting files\"\n- \"Filesystem-first debugging\"\n→ All express: **\"Observe outputs before editing code\"**\n\nUse the most general formulation. Update the frequency table.\n\n### Step 3: Detect Meta-Patterns\n\n**Critical step:** Look at what the learnings cluster around.\n\nIf >50% of patterns relate to one topic (e.g., \"hooks\", \"tracing\", \"async\"):\n→ That topic may need a **dedicated skill** rather than multiple rules\n→ One skill compounds better than five rules\n\nAsk yourself: *\"Is there a skill that would make all these rules unnecessary?\"*\n\n### Step 4: Categorize (Decision Tree)\n\nFor each pattern, determine artifact type:\n\n```\nIs it a sequence of commands\u002Fsteps?\n  → YES → SKILL (executable > declarative)\n  → NO ↓\n\nShould it run automatically on an event (SessionEnd, PostToolUse, etc.)?\n  → YES → HOOK (automatic > manual)\n  → NO ↓\n\nIs it \"when X, do Y\" or \"never do X\"?\n  → YES → RULE\n  → NO ↓\n\nDoes it enhance an existing agent workflow?\n  → YES → AGENT UPDATE\n  → NO → Skip (not worth capturing)\n```\n\n**Artifact Type Examples:**\n\n| Pattern | Type | Why |\n|---------|------|-----|\n| \"Run linting before commit\" | Hook (PreToolUse) | Automatic gate |\n| \"Extract learnings on session end\" | Hook (SessionEnd) | Automatic trigger |\n| \"Debug hooks step by step\" | Skill | Manual sequence |\n| \"Always pass IDs explicitly\" | Rule | Heuristic |\n\n### Step 5: Apply Signal Thresholds\n\n| Occurrences | Action |\n|-------------|--------|\n| 1 | Note but skip (unless critical failure) |\n| 2 | Consider - present to user |\n| 3+ | Strong signal - recommend creation |\n| 4+ | Definitely create |\n\n### Step 6: Propose Artifacts\n\nPresent each proposal in this format:\n\n```markdown\n---\n\n## Pattern: [Generalized Name]\n\n**Signal:** [N] sessions ([list session IDs])\n\n**Category:** [debugging \u002F reliability \u002F workflow \u002F etc.]\n\n**Artifact Type:** Rule \u002F Skill \u002F Agent Update\n\n**Rationale:** [Why this artifact type, why worth creating]\n\n**Draft Content:**\n\\`\\`\\`markdown\n[Actual content that would be written to file]\n\\`\\`\\`\n\n**File:** `.claude\u002Frules\u002F[name].md` or `.claude\u002Fskills\u002F[name]\u002FSKILL.md`\n\n---\n```\n\nUse `AskUserQuestion` to get approval for each artifact (or batch approval).\n\n### Step 7: Create Approved Artifacts\n\n#### For Rules:\n```bash\n# Write to rules directory\ncat > $CLAUDE_PROJECT_DIR\u002F.claude\u002Frules\u002F\u003Cname>.md \u003C\u003C 'EOF'\n# Rule Name\n\n[Context: why this rule exists, based on N sessions]\n\n## Pattern\n[The reusable principle]\n\n## DO\n- [Concrete action]\n\n## DON'T\n- [Anti-pattern]\n\n## Source Sessions\n- [session-id-1]: [what happened]\n- [session-id-2]: [what happened]\nEOF\n```\n\n#### For Skills:\nCreate `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` with:\n- Frontmatter (name, description, allowed-tools)\n- When to Use\n- Step-by-step instructions (executable)\n- Examples from the learnings\n\nAdd triggers to `skill-rules.json` if appropriate.\n\n#### For Hooks:\nCreate shell wrapper + TypeScript handler:\n\n```bash\n# Shell wrapper\ncat > $CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh \u003C\u003C 'EOF'\n#!\u002Fbin\u002Fbash\nset -e\ncd \"$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\"\ncat | node dist\u002F\u003Cname>.mjs\nEOF\nchmod +x $CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh\n```\n\nThen create `src\u002F\u003Cname>.ts`, build with esbuild, and register in `settings.json`:\n\n```json\n{\n  \"hooks\": {\n    \"EventName\": [{\n      \"hooks\": [{\n        \"type\": \"command\",\n        \"command\": \"$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002F\u003Cname>.sh\"\n      }]\n    }]\n  }\n}\n```\n\n#### For Agent Updates:\nEdit existing agent in `.claude\u002Fagents\u002F\u003Cname>.md` to add the learned capability.\n\n### Step 8: Summary Report\n\n```markdown\n## Compounding Complete\n\n**Learnings Analyzed:** [N] sessions\n**Patterns Found:** [M]\n**Artifacts Created:** [K]\n\n### Created:\n- Rule: `explicit-identity.md` - Pass IDs explicitly across boundaries\n- Skill: `debug-hooks` - Hook debugging workflow\n\n### Skipped (insufficient signal):\n- \"Pattern X\" (1 occurrence)\n\n**Your setup is now permanently improved.**\n```\n\n## Quality Checks\n\nBefore creating any artifact:\n\n1. **Is it general enough?** Would it apply in other projects?\n2. **Is it specific enough?** Does it give concrete guidance?\n3. **Does it already exist?** Check `.claude\u002Frules\u002F` and `.claude\u002Fskills\u002F` first\n4. **Is it the right type?** Sequences → skills, heuristics → rules\n\n## Files Reference\n\n- Learnings: `.claude\u002Fcache\u002Flearnings\u002F*.md`\n- Skills: `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`\n- Rules: `.claude\u002Frules\u002F\u003Cname>.md`\n- Hooks: `.claude\u002Fhooks\u002F\u003Cname>.sh` + `src\u002F\u003Cname>.ts` + `dist\u002F\u003Cname>.mjs`\n- Agents: `.claude\u002Fagents\u002F\u003Cname>.md`\n- Skill triggers: `.claude\u002Fskills\u002Fskill-rules.json`\n- Hook registration: `.claude\u002Fsettings.json` → `hooks` section\n",{"name":5,"description":7,"allowed-tools":42},[43,44,45,46,47,33,48],"Read","Glob","Grep","Write","Edit","AskUserQuestion","main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fcompound-learnings","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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add rubicanjr\u002FFinCognis --skill compound-learnings",{"tool":63,"command":64},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill compound-learnings",{"tool":66,"command":67},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill compound-learnings","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fcompound-learnings\u002FSKILL.md",true,[],[72,93,102,121,150,169],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":37},"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",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[84,85,86,87,88,89,90,91,92],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":37},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[95,100,101],"verification","false",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":37},"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000015","视觉设计",[112,24,113,114,115,116,117,118,119,120],"websocket","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":131,"publishedAt":37},"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",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},[132,133,134,135,136,137,138,139,140,141,142,143,144,114,145,146,147,148,25,149],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","for","fixes","dimensions","frontend","development","qa","screenshot","returns","frontend development",{"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":156,"publishedAt":37},"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",[],[157,158,100,159,160,161,162,163,164,165,166,167,168],"verification loop","loop","lint","review","security","pr","system","diff","build","tests","diff review","types",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":37},"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",[],[176,177,178,179,24,180,181,182,183,118,184,185,186,187,188,141,189,190],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]