[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DK9D6W6GP5ASEFPF3VAGJ2":3,"skill-same:01M7DK9D6W6GP5ASEFPF3VAGJ2":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DK9D6W6GP5ASEFPF3VAGJ2","ai-memory-durable-pages",null,"Use this skill for any explicit wiki mutation in ai-memory: saving durable or time-bounded project knowledge, recording a rule or annotation, updating a note, or deleting a memory page. Trigger by semantic intent rather than exact wording; routine session capture is not a durable-page request.","TheHefty\u002Fjvsl.env.agents.container","TheHefty","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165610515?v=4","01M7CE9QCF7JH950RN330BKCF4","João Lima","01M7DK9BR7HVQK0TMTRFPY7MC8",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fai-memory-durable-pages\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ai-memory-durable-pages\ndescription: \"Use this skill for any explicit wiki mutation in ai-memory: saving durable or time-bounded project knowledge, recording a rule or annotation, updating a note, or deleting a memory page. Trigger by semantic intent rather than exact wording; routine session capture is not a durable-page request.\"\n---\n\u003C!-- ai-memory-managed: routing-skill -->\n\n# ai-memory durable pages\n\nUse this skill only for deliberate durable wiki mutations. Routine session capture is automatic, and permanent notes require an explicit user request.\n\n## Tools in this cluster\n\n- `memory_write_page` writes a durable wiki page for permanent project knowledge.\n- `memory_delete_page` removes a durable wiki page by exact path.\n\n## Writing durable memory\n\nWrite a page only when the user explicitly asks to remember something permanently, save a note, add an annotation, or record project knowledge. Do not use durable pages for transient progress, normal status updates, or next-session context.\n\nPut the page title as a `# H1` on the first line of the body and omit the separate title argument. ai-memory derives the title from that H1. Keep the content concise and fact-like, with enough context that a future agent can apply it without rereading the whole session.\n\nWhen the user explicitly wants a note to be temporary, pass `expires_at` as an\nRFC3339 instant or a bare `YYYY-MM-DD` (the end of that day in UTC). After the\nTTL, normal search, recent, and briefing reads hide the page; the next forget\nsweep deletes it. A TTL outranks `pinned`, so do not combine them unless the user\nhas deliberately requested that behavior.\n\n## Project rules belong in instructions first\n\nIf the user asks to create a durable project rule such as always do X or never do Y, update the project's canonical agent instruction file when the repository says one exists. Use a durable page only when the user explicitly wants the rule in the wiki too, or when no canonical instruction file applies.\n\n## Deleting durable memory\n\nDelete only by exact path. If the user gives a vague title or topic, first resolve it to the page path using read-only lookup. Preserve sibling projects unless the user explicitly names them.\n\n## Scope default\n\nDefault to the current project. Pass workspace and project together only when the user explicitly names a different project. Never pass scope arguments for phrases like this project, here, we, or our work.\n\n## Architectural decisions get ADR structure and a pin\n\nWhen the user asks to record an architectural decision (a chosen approach, a rejected alternative, a standing trade-off), write it as a durable page under `decisions\u002F\u003Cshort-slug>.md` with `pinned: true` and this structure in the body:\n\n```markdown\n# \u003CDecision title>\n\n**Status:** accepted   \u003C!-- proposed | accepted | superseded by [[decisions\u002Fother]] -->\n\n## Context\nWhat situation forced a decision; the constraints that mattered.\n\n## Decision\nWhat was decided, stated as a fact.\n\n## Consequences\nWhat becomes easier, what becomes harder, what was given up.\nRejected alternatives and WHY, so future sessions don't re-propose them.\n```\n\nPinned pages are exempt from retention decay and curation, and the auto-improvement path refuses to rewrite them — the record stays immutable unless a human unpins it. To supersede a decision, write a NEW page and set the old page's status line to `superseded by [[decisions\u002F\u003Cnew>]]`; never edit the old decision's substance. Note: ai-memory never touches files in the project repository — a `docs\u002Fadr\u002F` directory managed there (by hand or by another tool) is outside ai-memory entirely; these wiki ADRs complement it for cross-session retrieval.\n\n## Standing user\u002Fteam preferences go to the global scope\n\nWhen the fact is a standing preference that should apply to EVERY project — technology choices (\"always use pnpm workspaces\"), code style (\"prefer composition over inheritance\"), personal conventions (\"never `--force` without asking\") — call `memory_write_page` with `scope: \"global\"` instead of the current project. The page lands in the reserved `_global` scope, and default memory reads surface it in every project as `global_scope_hits`. `scope: \"global\"` cannot be combined with workspace\u002Fproject arguments. Use it only for genuinely cross-project preferences; project-specific rules stay in the project (or its instruction file, per the section above).\n","\u003C!-- ai-memory-managed: routing-skill -->\n\n# ai-memory durable pages\n\nUse this skill only for deliberate durable wiki mutations. Routine session capture is automatic, and permanent notes require an explicit user request.\n\n## Tools in this cluster\n\n- `memory_write_page` writes a durable wiki page for permanent project knowledge.\n- `memory_delete_page` removes a durable wiki page by exact path.\n\n## Writing durable memory\n\nWrite a page only when the user explicitly asks to remember something permanently, save a note, add an annotation, or record project knowledge. Do not use durable pages for transient progress, normal status updates, or next-session context.\n\nPut the page title as a `# H1` on the first line of the body and omit the separate title argument. ai-memory derives the title from that H1. Keep the content concise and fact-like, with enough context that a future agent can apply it without rereading the whole session.\n\nWhen the user explicitly wants a note to be temporary, pass `expires_at` as an\nRFC3339 instant or a bare `YYYY-MM-DD` (the end of that day in UTC). After the\nTTL, normal search, recent, and briefing reads hide the page; the next forget\nsweep deletes it. A TTL outranks `pinned`, so do not combine them unless the user\nhas deliberately requested that behavior.\n\n## Project rules belong in instructions first\n\nIf the user asks to create a durable project rule such as always do X or never do Y, update the project's canonical agent instruction file when the repository says one exists. Use a durable page only when the user explicitly wants the rule in the wiki too, or when no canonical instruction file applies.\n\n## Deleting durable memory\n\nDelete only by exact path. If the user gives a vague title or topic, first resolve it to the page path using read-only lookup. Preserve sibling projects unless the user explicitly names them.\n\n## Scope default\n\nDefault to the current project. Pass workspace and project together only when the user explicitly names a different project. Never pass scope arguments for phrases like this project, here, we, or our work.\n\n## Architectural decisions get ADR structure and a pin\n\nWhen the user asks to record an architectural decision (a chosen approach, a rejected alternative, a standing trade-off), write it as a durable page under `decisions\u002F\u003Cshort-slug>.md` with `pinned: true` and this structure in the body:\n\n```markdown\n# \u003CDecision title>\n\n**Status:** accepted   \u003C!-- proposed | accepted | superseded by [[decisions\u002Fother]] -->\n\n## Context\nWhat situation forced a decision; the constraints that mattered.\n\n## Decision\nWhat was decided, stated as a fact.\n\n## Consequences\nWhat becomes easier, what becomes harder, what was given up.\nRejected alternatives and WHY, so future sessions don't re-propose them.\n```\n\nPinned pages are exempt from retention decay and curation, and the auto-improvement path refuses to rewrite them — the record stays immutable unless a human unpins it. To supersede a decision, write a NEW page and set the old page's status line to `superseded by [[decisions\u002F\u003Cnew>]]`; never edit the old decision's substance. Note: ai-memory never touches files in the project repository — a `docs\u002Fadr\u002F` directory managed there (by hand or by another tool) is outside ai-memory entirely; these wiki ADRs complement it for cross-session retrieval.\n\n## Standing user\u002Fteam preferences go to the global scope\n\nWhen the fact is a standing preference that should apply to EVERY project — technology choices (\"always use pnpm workspaces\"), code style (\"prefer composition over inheritance\"), personal conventions (\"never `--force` without asking\") — call `memory_write_page` with `scope: \"global\"` instead of the current project. The page lands in the reserved `_global` scope, and default memory reads surface it in every project as `global_scope_hits`. `scope: \"global\"` cannot be combined with workspace\u002Fproject arguments. Use it only for genuinely cross-project preferences; project-specific rules stay in the project (or its instruction file, per the section above).\n",{"name":5,"description":7},"master","e4865519cb1c8f3e0af4852ab91d612413d70117",".agents\u002Fskills\u002Fai-memory-durable-pages","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container","https:\u002F\u002Fgithub.com\u002FTheHefty","https:\u002F\u002Fwww.fahrenheit404.com.br","2026-11-04 14:42:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-durable-pages",{"tool":37,"command":38},"bunx","bunx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-durable-pages",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TheHefty\u002Fjvsl.env.agents.container --skill ai-memory-durable-pages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fai-memory-durable-pages\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DKC53FSDENMQ30AAR4022D","study","Build study material for a topic the developer wants to understand before writing about it — a guide in docs\u002Fstudy\u002F\u003Cslug>\u002F, tracked as a study task. Use when the developer asks to study a topic, to turn a blog candidate or a report topic into study material, or to prepare before writing a post. Never writes the post.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fstudy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DKBZ1KZKZQQAVB89YSCV7S","split-markdown","Split a Markdown file that reached the size limit (50 KiB) into a folder of its subjects — one file per top-level section, a README.md index, every inbound link updated — the way the rules prescribe. Use when check-md-size or the pre-commit hook refuses a file, or when the developer asks to split a Markdown file that grew too large. Shows the plan and writes nothing until the developer agrees.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fsplit-markdown\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DKBTQG1Y99AA8KNM3VSS6F","review","End-of-day review with the developer — show each task worked today against its done criterion, and record the developer's acceptance or reopen it with what is missing. Use when the developer asks to review the day or close out today's work, or as the first part of the end-of-day block.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DKBNCKYKA9HXG84JY1ZMV4","retro","The day's retrospective with the developer — report what was discovered, what surprised, what went wrong and what was decided without asking, take the developer's own \"what I want to learn\" line and elaborate on it, grounded in the day's work, and write the day's journal entry. Use after the review at the end of the day, or when the developer asks for the retro. Never skipped.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fretro\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DKBGG57AZR87EG60MQBNA4","refine","Refinement with the developer — grill the next candidate items or a new idea, propose stories and tasks in the tracker, and agree or reject them on the developer's word, so tomorrow's planning has agreed tasks to pick. Use after the retro at the end of the day, or when the developer asks to refine or plan the next work.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"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":19},"01M7DKBBBFQC5ETAK11F45JCME","project-report","A read-only report on the project — overview, decisions documented and implicit, critical areas, quality and tests, a study list by risk, and topics worth writing about — written to docs\u002FREPORT.md, which git ignores. Use when the developer asks for a project report, an overview of the codebase, what to study, or what is worth writing about.","https:\u002F\u002Fgithub.com\u002FTheHefty\u002Fjvsl.env.agents.container\u002Fblob\u002Fmaster\u002Fcore\u002Fplugin\u002Fagent-container\u002Fskills\u002Fproject-report\u002FSKILL.md",[],[]]