[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NV5KN5MEYY2969ERT255DV":3,"skill-same:01M6NV5KN5MEYY2969ERT255DV":60},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6NV5KN5MEYY2969ERT255DV","knowledge-management",null,"Proje bilgisini 4 katmanli yapida organize et. Aktif projeler, sorumluluk alanlari, referans kaynaklar ve arsiv. Progressive summarization ile bilgiyi katman katman ozumse. Second brain pattern'i ile codebase bilgisini yapilandir.","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\u002Fknowledge-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"knowledge","management","knowledge management","second brain","summarization","organize","pattern","brain","codebase","2026-11-10 10:12:30",false,"---\nname: knowledge-management\ndescription: Proje bilgisini 4 katmanli yapida organize et. Aktif projeler, sorumluluk alanlari, referans kaynaklar ve arsiv. Progressive summarization ile bilgiyi katman katman ozumse. Second brain pattern'i ile codebase bilgisini yapilandir.\n---\n\n# Knowledge Management\n\nBuyuk projelerde bilgi kaybini onleyen 4 katmanli organizasyon sistemi.\n\n## 4 Katmanli Bilgi Yapisi\n\n```\nKATMAN 1: AKTIF ISLER\n  Simdi uzerinde calisilanlar. Sprint task'lari, aktif bug'lar, devam eden feature'lar.\n  Konum: thoughts\u002Factive\u002F veya .claude\u002Factive\u002F\n  Kural: Max 5-7 aktif is. Fazlasi = fokus kaybı.\n\nKATMAN 2: SORUMLULUK ALANLARI\n  Surekli sahip oldugun alanlar. Auth modulu, API layer, deployment pipeline.\n  Konum: thoughts\u002Fareas\u002F veya .claude\u002Fareas\u002F\n  Kural: Her alan icin tek sayfalik \"durum raporu\" tut.\n\nKATMAN 3: REFERANSLAR\n  Tekrar tekrar basvurulan bilgiler. API dokumantasyonu, tasarim kararlari, benchmark sonuclari.\n  Konum: thoughts\u002Freferences\u002F veya .claude\u002Freferences\u002F\n  Kural: Ihtiyac duyuldugunda hizla bulunabilmeli.\n\nKATMAN 4: ARSIV\n  Tamamlanan isler, eski kararlar, deprecated feature'lar.\n  Konum: thoughts\u002Farchive\u002F veya .claude\u002Farchive\u002F\n  Kural: Silme, tasi. Bir gun lazim olabilir.\n```\n\n## Bilgi Akisi\n\n```\nYENi BILGI geldiginde:\n  1. Aktif is ile ilgiliyse → KATMAN 1'e ekle\n  2. Surekli sorumluluk alaniysa → KATMAN 2'ye ekle\n  3. Referans\u002Fdokumantasyonsa → KATMAN 3'e ekle\n  4. Hicbirine uymuyorsa → KATMA (gereksiz bilgi)\n\nIS TAMAMLANDIGINDA:\n  1. KATMAN 1'den kaldir\n  2. Ogrenimleri KATMAN 3'e tasi (referans olarak)\n  3. Detaylari KATMAN 4'e arsivle\n```\n\n## Progressive Summarization\n\nBilgiyi katman katman ozumseme teknigi. Her geciste bilgi daha yogun ve erislebilir olur.\n\n### Katman 0: Ham Kaynak\nOrijinal icerik -- commit mesajlari, PR aciklamalari, meeting notlari, hata loglari.\n\n### Katman 1: Yakalama\nIlgili kisimları kaydet. Tam metni degil, onemli parcalari.\n\n```markdown\n# Auth Refactoring Notlari\n\n- JWT'den session-based'e gecis karari alindi (2026-03-15)\n- Neden: JWT revocation problemi, token boyutu sisiyor\n- Redis session store kullanilacak\n- Migration 3 fazda yapilacak\n```\n\n### Katman 2: Kalin Isaret\nEn onemli cumleler\u002Fkavramlar **bold** ile isaretle.\n\n```markdown\n# Auth Refactoring Notlari\n\n- **JWT'den session-based'e gecis** karari alindi (2026-03-15)\n- Neden: **JWT revocation problemi**, token boyutu sisiyor\n- **Redis session store** kullanilacak\n- Migration **3 fazda** yapilacak\n```\n\n### Katman 3: Ozet\nKendi cumlenle 2-3 satirlik ozet yaz.\n\n```markdown\n# Auth Refactoring\n\nJWT revocation problemi nedeniyle session-based auth'a geciliyor.\nRedis session store + 3 fazli migration plani var.\n```\n\n### Katman 4: Remix\nBaska bilgilerle birlestir, yeni icerik uret.\n\n```markdown\n# Auth Sistemi Mimari Karar Kaydi\n\nSession-based auth (Redis) tercih edildi. JWT'nin revocation ve boyut\nproblemleri cozumsuzdu. Bu karar API gateway tasarimini da etkiliyor --\nher istekte Redis lookup gerekecek, caching stratejisi buna gore ayarlanmali.\n```\n\n## Codebase Second Brain\n\n### Dosya Yapisi\n\n```\nthoughts\u002F\n  active\u002F\n    current-sprint.md        # Bu sprint'in task'lari\n    in-progress-feature.md   # Uzerinde calisilanlar\n  areas\u002F\n    auth.md                  # Auth modulu durumu\n    api.md                   # API layer durumu\n    infrastructure.md        # Infra durumu\n  references\u002F\n    adr\u002F                     # Architecture Decision Records\n      001-session-auth.md\n      002-redis-cache.md\n    benchmarks\u002F              # Performans sonuclari\n    api-contracts\u002F           # API sozlesmeleri\n  archive\u002F\n    2026-q1\u002F                 # Ceyreklik arsiv\n    deprecated\u002F              # Kaldirilmis feature'lar\n```\n\n### ADR (Architecture Decision Record) Formati\n\n```markdown\n# ADR-001: Session-Based Authentication\n\n## Durum\nKabul edildi (2026-03-15)\n\n## Baglam\nJWT token'lari revoke edilemiyor, token boyutu buyuyor.\n\n## Karar\nRedis-backed session authentication'a gecis.\n\n## Sonuclar\n- (+) Anlik revocation mumkun\n- (+) Token boyutu sorun degil\n- (-) Redis bagimliligi eklendi\n- (-) Her istekte session lookup gerekiyor\n```\n\n## Bilgi Yakalama Tetikleyicileri\n\n| Olay | Yakalanacak Bilgi | Nereye |\n|------|-------------------|--------|\n| Mimari karar alindi | ADR yaz | references\u002Fadr\u002F |\n| Bug cozuldu | Root cause + fix | references\u002F veya memory |\n| Sprint basladi | Task listesi | active\u002F |\n| Sprint bitti | Retrospektif | archive\u002F |\n| Yeni modul eklendi | Alan durumu | areas\u002F |\n| Performance test yapildi | Benchmark sonuclari | references\u002Fbenchmarks\u002F |\n| API degisti | Contract guncelle | references\u002Fapi-contracts\u002F |\n| Dependency upgrade | Migration notlari | active\u002F (sonra archive\u002F) |\n\n## Bilgi Erisim Hiyerarsisi\n\nBir soruya cevap ararken su sirada bak:\n\n```\n1. AKTIF ISLER (thoughts\u002Factive\u002F) → Simdi alakali mi?\n2. ALAN DURUMLARI (thoughts\u002Fareas\u002F) → Bu alanla ilgili mi?\n3. REFERANSLAR (thoughts\u002Freferences\u002F) → Daha once karar alinmis mi?\n4. ARSIV (thoughts\u002Farchive\u002F) → Gecmiste benzer is yapilmis mi?\n5. GIT HISTORY (git log\u002Fblame) → Kodda ne degismis?\n6. MEMORY SYSTEM (recall) → Baska session'larda ne ogrenmisiz?\n```\n\n## Haftalik Bakım\n\n```\nHer hafta 15 dakika:\n[ ] Aktif isler guncelle (tamamlananlar archive'a)\n[ ] Alan durumlari guncelle (degisen varsa)\n[ ] Referanslar guncelle (yeni karar varsa ADR yaz)\n[ ] Gereksiz bilgileri sil veya arsivle\n```\n\n## Anti-Pattern'ler\n\n```\nYAPMA: Her seyi kaydet\nYAP:   Sadece tekrar kullanilacak bilgiyi kaydet\n\nYAPMA: Tek buyuk dosyada tut\nYAP:   Konu basina ayri dosya\n\nYAPMA: Arsivi hicbir zaman temizleme\nYAP:   Ceyreklik arsiv, yillik temizlik\n\nYAPMA: Bilgiyi sadece kafanda tut\nYAP:   Yazdığın an unutabilirsin, hemen kaydet\n\nYAPMA: Her dosyayi ayni seviyede tut\nYAP:   Progressive summarization ile katmanla\n```\n\n## vibecosystem Entegrasyonu\n\n- **compass agent**: Session context recovery icin 4 katmanli yapiyi kullanir\n- **scribe agent**: Session handoff'larda bilgi organizasyonunu uygular\n- **self-learner agent**: Ogrenimleri uygun katmana kaydeder\n- **architect agent**: ADR yazmak icin bu formati kullanir\n- **Memory system**: KATMAN 3 (referanslar) ile memory recall birlikte calisir\n","# Knowledge Management\n\nBuyuk projelerde bilgi kaybini onleyen 4 katmanli organizasyon sistemi.\n\n## 4 Katmanli Bilgi Yapisi\n\n```\nKATMAN 1: AKTIF ISLER\n  Simdi uzerinde calisilanlar. Sprint task'lari, aktif bug'lar, devam eden feature'lar.\n  Konum: thoughts\u002Factive\u002F veya .claude\u002Factive\u002F\n  Kural: Max 5-7 aktif is. Fazlasi = fokus kaybı.\n\nKATMAN 2: SORUMLULUK ALANLARI\n  Surekli sahip oldugun alanlar. Auth modulu, API layer, deployment pipeline.\n  Konum: thoughts\u002Fareas\u002F veya .claude\u002Fareas\u002F\n  Kural: Her alan icin tek sayfalik \"durum raporu\" tut.\n\nKATMAN 3: REFERANSLAR\n  Tekrar tekrar basvurulan bilgiler. API dokumantasyonu, tasarim kararlari, benchmark sonuclari.\n  Konum: thoughts\u002Freferences\u002F veya .claude\u002Freferences\u002F\n  Kural: Ihtiyac duyuldugunda hizla bulunabilmeli.\n\nKATMAN 4: ARSIV\n  Tamamlanan isler, eski kararlar, deprecated feature'lar.\n  Konum: thoughts\u002Farchive\u002F veya .claude\u002Farchive\u002F\n  Kural: Silme, tasi. Bir gun lazim olabilir.\n```\n\n## Bilgi Akisi\n\n```\nYENi BILGI geldiginde:\n  1. Aktif is ile ilgiliyse → KATMAN 1'e ekle\n  2. Surekli sorumluluk alaniysa → KATMAN 2'ye ekle\n  3. Referans\u002Fdokumantasyonsa → KATMAN 3'e ekle\n  4. Hicbirine uymuyorsa → KATMA (gereksiz bilgi)\n\nIS TAMAMLANDIGINDA:\n  1. KATMAN 1'den kaldir\n  2. Ogrenimleri KATMAN 3'e tasi (referans olarak)\n  3. Detaylari KATMAN 4'e arsivle\n```\n\n## Progressive Summarization\n\nBilgiyi katman katman ozumseme teknigi. Her geciste bilgi daha yogun ve erislebilir olur.\n\n### Katman 0: Ham Kaynak\nOrijinal icerik -- commit mesajlari, PR aciklamalari, meeting notlari, hata loglari.\n\n### Katman 1: Yakalama\nIlgili kisimları kaydet. Tam metni degil, onemli parcalari.\n\n```markdown\n# Auth Refactoring Notlari\n\n- JWT'den session-based'e gecis karari alindi (2026-03-15)\n- Neden: JWT revocation problemi, token boyutu sisiyor\n- Redis session store kullanilacak\n- Migration 3 fazda yapilacak\n```\n\n### Katman 2: Kalin Isaret\nEn onemli cumleler\u002Fkavramlar **bold** ile isaretle.\n\n```markdown\n# Auth Refactoring Notlari\n\n- **JWT'den session-based'e gecis** karari alindi (2026-03-15)\n- Neden: **JWT revocation problemi**, token boyutu sisiyor\n- **Redis session store** kullanilacak\n- Migration **3 fazda** yapilacak\n```\n\n### Katman 3: Ozet\nKendi cumlenle 2-3 satirlik ozet yaz.\n\n```markdown\n# Auth Refactoring\n\nJWT revocation problemi nedeniyle session-based auth'a geciliyor.\nRedis session store + 3 fazli migration plani var.\n```\n\n### Katman 4: Remix\nBaska bilgilerle birlestir, yeni icerik uret.\n\n```markdown\n# Auth Sistemi Mimari Karar Kaydi\n\nSession-based auth (Redis) tercih edildi. JWT'nin revocation ve boyut\nproblemleri cozumsuzdu. Bu karar API gateway tasarimini da etkiliyor --\nher istekte Redis lookup gerekecek, caching stratejisi buna gore ayarlanmali.\n```\n\n## Codebase Second Brain\n\n### Dosya Yapisi\n\n```\nthoughts\u002F\n  active\u002F\n    current-sprint.md        # Bu sprint'in task'lari\n    in-progress-feature.md   # Uzerinde calisilanlar\n  areas\u002F\n    auth.md                  # Auth modulu durumu\n    api.md                   # API layer durumu\n    infrastructure.md        # Infra durumu\n  references\u002F\n    adr\u002F                     # Architecture Decision Records\n      001-session-auth.md\n      002-redis-cache.md\n    benchmarks\u002F              # Performans sonuclari\n    api-contracts\u002F           # API sozlesmeleri\n  archive\u002F\n    2026-q1\u002F                 # Ceyreklik arsiv\n    deprecated\u002F              # Kaldirilmis feature'lar\n```\n\n### ADR (Architecture Decision Record) Formati\n\n```markdown\n# ADR-001: Session-Based Authentication\n\n## Durum\nKabul edildi (2026-03-15)\n\n## Baglam\nJWT token'lari revoke edilemiyor, token boyutu buyuyor.\n\n## Karar\nRedis-backed session authentication'a gecis.\n\n## Sonuclar\n- (+) Anlik revocation mumkun\n- (+) Token boyutu sorun degil\n- (-) Redis bagimliligi eklendi\n- (-) Her istekte session lookup gerekiyor\n```\n\n## Bilgi Yakalama Tetikleyicileri\n\n| Olay | Yakalanacak Bilgi | Nereye |\n|------|-------------------|--------|\n| Mimari karar alindi | ADR yaz | references\u002Fadr\u002F |\n| Bug cozuldu | Root cause + fix | references\u002F veya memory |\n| Sprint basladi | Task listesi | active\u002F |\n| Sprint bitti | Retrospektif | archive\u002F |\n| Yeni modul eklendi | Alan durumu | areas\u002F |\n| Performance test yapildi | Benchmark sonuclari | references\u002Fbenchmarks\u002F |\n| API degisti | Contract guncelle | references\u002Fapi-contracts\u002F |\n| Dependency upgrade | Migration notlari | active\u002F (sonra archive\u002F) |\n\n## Bilgi Erisim Hiyerarsisi\n\nBir soruya cevap ararken su sirada bak:\n\n```\n1. AKTIF ISLER (thoughts\u002Factive\u002F) → Simdi alakali mi?\n2. ALAN DURUMLARI (thoughts\u002Fareas\u002F) → Bu alanla ilgili mi?\n3. REFERANSLAR (thoughts\u002Freferences\u002F) → Daha once karar alinmis mi?\n4. ARSIV (thoughts\u002Farchive\u002F) → Gecmiste benzer is yapilmis mi?\n5. GIT HISTORY (git log\u002Fblame) → Kodda ne degismis?\n6. MEMORY SYSTEM (recall) → Baska session'larda ne ogrenmisiz?\n```\n\n## Haftalik Bakım\n\n```\nHer hafta 15 dakika:\n[ ] Aktif isler guncelle (tamamlananlar archive'a)\n[ ] Alan durumlari guncelle (degisen varsa)\n[ ] Referanslar guncelle (yeni karar varsa ADR yaz)\n[ ] Gereksiz bilgileri sil veya arsivle\n```\n\n## Anti-Pattern'ler\n\n```\nYAPMA: Her seyi kaydet\nYAP:   Sadece tekrar kullanilacak bilgiyi kaydet\n\nYAPMA: Tek buyuk dosyada tut\nYAP:   Konu basina ayri dosya\n\nYAPMA: Arsivi hicbir zaman temizleme\nYAP:   Ceyreklik arsiv, yillik temizlik\n\nYAPMA: Bilgiyi sadece kafanda tut\nYAP:   Yazdığın an unutabilirsin, hemen kaydet\n\nYAPMA: Her dosyayi ayni seviyede tut\nYAP:   Progressive summarization ile katmanla\n```\n\n## vibecosystem Entegrasyonu\n\n- **compass agent**: Session context recovery icin 4 katmanli yapiyi kullanir\n- **scribe agent**: Session handoff'larda bilgi organizasyonunu uygular\n- **self-learner agent**: Ogrenimleri uygun katmana kaydeder\n- **architect agent**: ADR yazmak icin bu formati kullanir\n- **Memory system**: KATMAN 3 (referanslar) ile memory recall birlikte calisir\n",{"name":5,"description":7},"main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fknowledge-management","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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add rubicanjr\u002FFinCognis --skill knowledge-management",{"tool":52,"command":53},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill knowledge-management",{"tool":55,"command":56},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill knowledge-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-management\u002FSKILL.md",true,[],[61,80,89,108,138,157],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":70,"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",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[71,72,73,74,75,76,77,78,79],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":33},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[82,87,88],"verification","false",{"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,25,104,105,106,107],"websocket","patterns","websocket patterns","design","protocol","message","strategies","binary","connection",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":118,"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",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":68,"categoryName":69,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,125,126,127,128,129,130,131,102,132,133,134,135,136,137],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","for","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,87,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,105,172,173,174,175,176,128,177,178],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]