[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NVTTZ9QQQZPJR0BW06XTFT":3,"skill-same:01M6NVTTZ9QQQZPJR0BW06XTFT":62},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6NVTTZ9QQQZPJR0BW06XTFT","notepad-system",null,"Use this skill when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks. Provides a durable notepad that survives compaction and lets any agent pick up exactly where the previous context left off.","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\u002Fnotepad-system\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"system","notepad system","tasks","compression","pick","context compression","decisions","context","session","use","up","across","critical","long","compaction","resuming","2026-11-10 10:12:30",false,"---\nname: notepad-system\ndescription: Use this skill when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks. Provides a durable notepad that survives compaction and lets any agent pick up exactly where the previous context left off.\n---\n\n# Notepad System — Compaction-Resistant State Preservation\n\nStructured storage for decisions, task state, and critical context that must survive\ncontext window compression. Extends pre-compact-state.md from manual discipline to\na concrete file-based protocol.\n\n## The Problem\n\nWhen context compresses, the following is lost:\n- Why a specific approach was chosen over alternatives\n- Which files were edited and what changed\n- Where in a multi-step task execution was paused\n- Constraints and requirements the user stated earlier in the session\n\nWithout this, the recovered context either restarts from scratch or makes assumptions\nthat contradict earlier decisions.\n\n---\n\n## Note Types\n\n| Type | Persistence | When to Use |\n|------|-------------|-------------|\n| **Priority** | Permanent until explicitly deleted | Architectural decisions, user confirmed preferences, hard constraints |\n| **Working** | Session-scoped, cleared at session end | Current task state, WIP progress, in-flight findings |\n| **Scratch** | Cleared after use (one-time calc) | Quick calculations, temp values used once |\n\n---\n\n## Storage Location\n\n```\n~\u002F.claude\u002Fprojects\u002F\u003Cproject-hash>\u002Fnotepad.md\n```\n\nThe project hash is derived from the working directory path.\nIf the directory does not exist, create it before writing.\n\n### File Format\n\n```markdown\n# Notepad\n\n## Priority Notes\n\n### [2026-03-29 14:22] Decision: Auth approach\nJWT with refresh tokens. User confirmed.\nReason: Stateless, scalable, mobile-friendly.\nRejected: Session-based (server state, scaling issues).\n\n### [2026-03-29 15:10] Constraint: Node version\nMust stay on Node 18. Server has LTS pinned, no upgrade path in scope.\n\n## Working Notes\n\n### [2026-03-29 14:45] Task: API refactor — Phase 2\nCompleted: \u002Fusers, \u002Fproducts, \u002Fcategories endpoints\nRemaining: \u002Forders, \u002Fpayments endpoints\nBlocked on: Stripe webhook secret (user to provide)\nNext action: Start \u002Forders, skip payment until secret arrives\n\n## Scratch\n\n### [2026-03-29 15:30] Token estimate\nAverage response: 256 tokens. 4x safety margin = ~1024 tokens per request budget.\nUSED — safe to delete.\n```\n\n---\n\n## Pre-Compact Protocol\n\nWhen context compression is imminent (context window at ~80% or system warning appears):\n\n**Step 1 — Dump active task state to Working Notes**\n```\nWhat task is in progress?\nWhat has been completed so far?\nWhat remains?\nAre there any blockers?\nWhat is the immediate next action when context resumes?\n```\n\n**Step 2 — Promote any pending decisions to Priority Notes**\n```\nAny architectural choice made this session → Priority Note\nAny user-confirmed preference → Priority Note\nAny external constraint discovered → Priority Note\n```\n\n**Step 3 — Record modified files**\n```\nList every file touched this session.\nNote what changed in each (one line per file is enough).\nNote whether changes are committed or uncommitted.\n```\n\n**Step 4 — Save pending decisions with their options**\n```\nIf a decision was not yet made, record the question and the options.\nThis prevents re-deriving the same options after compression.\n```\n\nDo this BEFORE continuing work. State preservation takes priority.\n\n---\n\n## Post-Compact Recovery\n\nWhen a new or compressed context begins:\n\n**Step 1 — Read notepad.md**\n```\nPath: ~\u002F.claude\u002Fprojects\u002F\u003Cproject-hash>\u002Fnotepad.md\n```\n\n**Step 2 — Inject Priority Notes into active context**\nThese are always relevant. Treat them as if the user stated them at session start.\n\n**Step 3 — Summarize Working Notes for the user**\n```\n\"Resuming: API refactor, Phase 2.\nCompleted: \u002Fusers, \u002Fproducts, \u002Fcategories.\nRemaining: \u002Forders, \u002Fpayments.\nBlocked: Stripe webhook secret needed.\nNext: starting \u002Forders.\"\n```\n\n**Step 4 — Clear Scratch notes**\nThey were single-use. Remove them now.\n\n**Step 5 — Resume from last known state**\nDo not ask the user to re-explain context that is in Working Notes.\n\n---\n\n## Note Writing Rules\n\n- Priority notes require explicit deletion: `notepad delete priority \u003Ctitle>`\n- Working notes are cleared at the end of each session (or when the task completes)\n- Never store code in notes — reference `file.ts:line` instead\n- Keep each note to 3 lines maximum (reference files for detail)\n- Always include a timestamp in the note header\n- Never duplicate information already in CLAUDE.md or memory — cross-reference instead\n\n---\n\n## CLI Operations (manual use)\n\nRead the notepad:\n```bash\ncat ~\u002F.claude\u002Fprojects\u002F\u003Chash>\u002Fnotepad.md\n```\n\nClear working notes (session end):\n```bash\n# Remove the Working Notes section content, keep the headers\n```\n\nClear scratch notes (after use):\n```bash\n# Remove individual scratch entries after they have been applied\n```\n\n---\n\n## Integration\n\n**pre-compact-state.md** — This skill is the concrete implementation of that rule.\nThe rule defines what to save; this skill defines where, how, and in what format.\n\n**compass agent** — The compass agent performs context recovery. It should read\nnotepad.md as its first action and use the contents to construct the \"Nerede kalmistik?\" summary.\n\n**Any agent** — Any agent starting work on a project should check notepad.md for\nPriority Notes that constrain their approach. An architect should not propose a\nsolution that contradicts a Priority Note.\n\n---\n\n## Example Scenarios\n\n### Scenario 1: Mid-refactor compression\n\nWorking on a large refactor across 12 files. Context at 80%.\n\nPre-compact dump:\n```markdown\n### [2026-03-29 16:00] Task: Auth system refactor — 7\u002F12 files done\nCompleted: user.service.ts, auth.controller.ts, token.service.ts,\n  session.middleware.ts, logout.handler.ts, login.handler.ts, refresh.handler.ts\nRemaining: password.service.ts, oauth.handler.ts, 2fa.handler.ts,\n  admin.auth.ts, tests\u002Fauth.test.ts\nNext: start password.service.ts — method signature unchanged, internals only\n```\n\nAfter compression, any agent reads this and knows exactly which 5 files remain.\n\n### Scenario 2: Decision under uncertainty\n\nUser asked about caching strategy but has not confirmed yet.\n\nScratch note:\n```markdown\n### [2026-03-29 16:15] Pending: Caching strategy\nOptions: (a) Redis — fast, requires infra; (b) in-memory — simple, no persistence\nAwaiting user confirmation on whether Redis is available in prod.\n```\n\nThis prevents re-deriving the same question after compression.\n\n### Scenario 3: Hard constraint from early conversation\n\nUser mentioned early in a long session that they cannot use PostgreSQL — MySQL only.\n\nPriority note created immediately:\n```markdown\n### [2026-03-29 10:05] Constraint: Database — MySQL only\nNo PostgreSQL. Server is MySQL 8.0. All queries and schema must be MySQL-compatible.\nReason: Hosting provider limitation.\n```\n\nEvery subsequent agent reads this and never proposes PostgreSQL.\n","# Notepad System — Compaction-Resistant State Preservation\n\nStructured storage for decisions, task state, and critical context that must survive\ncontext window compression. Extends pre-compact-state.md from manual discipline to\na concrete file-based protocol.\n\n## The Problem\n\nWhen context compresses, the following is lost:\n- Why a specific approach was chosen over alternatives\n- Which files were edited and what changed\n- Where in a multi-step task execution was paused\n- Constraints and requirements the user stated earlier in the session\n\nWithout this, the recovered context either restarts from scratch or makes assumptions\nthat contradict earlier decisions.\n\n---\n\n## Note Types\n\n| Type | Persistence | When to Use |\n|------|-------------|-------------|\n| **Priority** | Permanent until explicitly deleted | Architectural decisions, user confirmed preferences, hard constraints |\n| **Working** | Session-scoped, cleared at session end | Current task state, WIP progress, in-flight findings |\n| **Scratch** | Cleared after use (one-time calc) | Quick calculations, temp values used once |\n\n---\n\n## Storage Location\n\n```\n~\u002F.claude\u002Fprojects\u002F\u003Cproject-hash>\u002Fnotepad.md\n```\n\nThe project hash is derived from the working directory path.\nIf the directory does not exist, create it before writing.\n\n### File Format\n\n```markdown\n# Notepad\n\n## Priority Notes\n\n### [2026-03-29 14:22] Decision: Auth approach\nJWT with refresh tokens. User confirmed.\nReason: Stateless, scalable, mobile-friendly.\nRejected: Session-based (server state, scaling issues).\n\n### [2026-03-29 15:10] Constraint: Node version\nMust stay on Node 18. Server has LTS pinned, no upgrade path in scope.\n\n## Working Notes\n\n### [2026-03-29 14:45] Task: API refactor — Phase 2\nCompleted: \u002Fusers, \u002Fproducts, \u002Fcategories endpoints\nRemaining: \u002Forders, \u002Fpayments endpoints\nBlocked on: Stripe webhook secret (user to provide)\nNext action: Start \u002Forders, skip payment until secret arrives\n\n## Scratch\n\n### [2026-03-29 15:30] Token estimate\nAverage response: 256 tokens. 4x safety margin = ~1024 tokens per request budget.\nUSED — safe to delete.\n```\n\n---\n\n## Pre-Compact Protocol\n\nWhen context compression is imminent (context window at ~80% or system warning appears):\n\n**Step 1 — Dump active task state to Working Notes**\n```\nWhat task is in progress?\nWhat has been completed so far?\nWhat remains?\nAre there any blockers?\nWhat is the immediate next action when context resumes?\n```\n\n**Step 2 — Promote any pending decisions to Priority Notes**\n```\nAny architectural choice made this session → Priority Note\nAny user-confirmed preference → Priority Note\nAny external constraint discovered → Priority Note\n```\n\n**Step 3 — Record modified files**\n```\nList every file touched this session.\nNote what changed in each (one line per file is enough).\nNote whether changes are committed or uncommitted.\n```\n\n**Step 4 — Save pending decisions with their options**\n```\nIf a decision was not yet made, record the question and the options.\nThis prevents re-deriving the same options after compression.\n```\n\nDo this BEFORE continuing work. State preservation takes priority.\n\n---\n\n## Post-Compact Recovery\n\nWhen a new or compressed context begins:\n\n**Step 1 — Read notepad.md**\n```\nPath: ~\u002F.claude\u002Fprojects\u002F\u003Cproject-hash>\u002Fnotepad.md\n```\n\n**Step 2 — Inject Priority Notes into active context**\nThese are always relevant. Treat them as if the user stated them at session start.\n\n**Step 3 — Summarize Working Notes for the user**\n```\n\"Resuming: API refactor, Phase 2.\nCompleted: \u002Fusers, \u002Fproducts, \u002Fcategories.\nRemaining: \u002Forders, \u002Fpayments.\nBlocked: Stripe webhook secret needed.\nNext: starting \u002Forders.\"\n```\n\n**Step 4 — Clear Scratch notes**\nThey were single-use. Remove them now.\n\n**Step 5 — Resume from last known state**\nDo not ask the user to re-explain context that is in Working Notes.\n\n---\n\n## Note Writing Rules\n\n- Priority notes require explicit deletion: `notepad delete priority \u003Ctitle>`\n- Working notes are cleared at the end of each session (or when the task completes)\n- Never store code in notes — reference `file.ts:line` instead\n- Keep each note to 3 lines maximum (reference files for detail)\n- Always include a timestamp in the note header\n- Never duplicate information already in CLAUDE.md or memory — cross-reference instead\n\n---\n\n## CLI Operations (manual use)\n\nRead the notepad:\n```bash\ncat ~\u002F.claude\u002Fprojects\u002F\u003Chash>\u002Fnotepad.md\n```\n\nClear working notes (session end):\n```bash\n# Remove the Working Notes section content, keep the headers\n```\n\nClear scratch notes (after use):\n```bash\n# Remove individual scratch entries after they have been applied\n```\n\n---\n\n## Integration\n\n**pre-compact-state.md** — This skill is the concrete implementation of that rule.\nThe rule defines what to save; this skill defines where, how, and in what format.\n\n**compass agent** — The compass agent performs context recovery. It should read\nnotepad.md as its first action and use the contents to construct the \"Nerede kalmistik?\" summary.\n\n**Any agent** — Any agent starting work on a project should check notepad.md for\nPriority Notes that constrain their approach. An architect should not propose a\nsolution that contradicts a Priority Note.\n\n---\n\n## Example Scenarios\n\n### Scenario 1: Mid-refactor compression\n\nWorking on a large refactor across 12 files. Context at 80%.\n\nPre-compact dump:\n```markdown\n### [2026-03-29 16:00] Task: Auth system refactor — 7\u002F12 files done\nCompleted: user.service.ts, auth.controller.ts, token.service.ts,\n  session.middleware.ts, logout.handler.ts, login.handler.ts, refresh.handler.ts\nRemaining: password.service.ts, oauth.handler.ts, 2fa.handler.ts,\n  admin.auth.ts, tests\u002Fauth.test.ts\nNext: start password.service.ts — method signature unchanged, internals only\n```\n\nAfter compression, any agent reads this and knows exactly which 5 files remain.\n\n### Scenario 2: Decision under uncertainty\n\nUser asked about caching strategy but has not confirmed yet.\n\nScratch note:\n```markdown\n### [2026-03-29 16:15] Pending: Caching strategy\nOptions: (a) Redis — fast, requires infra; (b) in-memory — simple, no persistence\nAwaiting user confirmation on whether Redis is available in prod.\n```\n\nThis prevents re-deriving the same question after compression.\n\n### Scenario 3: Hard constraint from early conversation\n\nUser mentioned early in a long session that they cannot use PostgreSQL — MySQL only.\n\nPriority note created immediately:\n```markdown\n### [2026-03-29 10:05] Constraint: Database — MySQL only\nNo PostgreSQL. Server is MySQL 8.0. All queries and schema must be MySQL-compatible.\nReason: Hosting provider limitation.\n```\n\nEvery subsequent agent reads this and never proposes PostgreSQL.\n",{"name":5,"description":7},"main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fnotepad-system","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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add rubicanjr\u002FFinCognis --skill notepad-system",{"tool":54,"command":55},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill notepad-system",{"tool":57,"command":58},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill notepad-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fnotepad-system\u002FSKILL.md",true,[],[63,83,92,112,140,158],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":35},"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",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[75,76,77,78,79,80,81,82,21],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":35},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[85,90,91],"verification","false",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":101,"publishedAt":35},"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",[98],{"categoryNo":99,"categoryName":100,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000015","视觉设计",[102,103,104,105,106,107,108,109,110,111],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":122,"publishedAt":35},"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",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[123,124,125,126,30,127,128,129,130,131,132,133,134,105,135,136,137,138,28,139],"visual","verdict","visual verdict","ui","revise","comparison","correctness","implementing","for","fixes","dimensions","frontend","development","qa","screenshot","returns","frontend development",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":35},"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",[],[147,148,90,149,150,151,152,19,153,154,155,156,157],"verification loop","loop","lint","review","security","pr","diff","build","tests","diff review","types",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":35},"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",[],[165,166,167,168,103,169,170,171,172,109,173,174,175,176,177,131,178,179],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]