[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EB3PTN0R44MZ2XN4PE1BEB":3,"skill-same:01M7EB3PTN0R44MZ2XN4PE1BEB":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EB3PTN0R44MZ2XN4PE1BEB","gleam-change",null,"Implement or review a change to the controller with the sans-IO boundary, confined FFI, supervision, tests and documentation the invariants require.","BiscuitBin\u002Fknarr","BiscuitBin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F345587809?v=4","01M7EB2YJH5XDMD513JY25JRH2","01M7EB2YKMFCPW7ATTQ8TWB2WD",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgleam-change\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gleam-change\ndescription: Implement or review a change to the controller with the sans-IO boundary, confined FFI, supervision, tests and documentation the invariants require.\n---\n\n# Change the controller\n\n1. Read `AGENTS.md` and `docs\u002Fdecisions\u002F0002-sans-io-boundaries.md`. Identify which module under `src\u002F` the change lands in and whether it changes what the controller writes to the cluster; an annotation, a label or a patch shape is part of the worker contract and so part of the change.\n2. Find the clause. Every behaviour has an owning module under `docs\u002Fspecs\u002F`; read the rule, its guards and its outcomes before writing code. If no clause says what you need, this is a `spec-change` first, not a judgement call in code.\n3. Put every effect behind the sans-IO boundary. Decision logic takes observations, a clock value and configuration as plain values and returns the decision; HTTP polls, Kubernetes reads and patches, timers and scheduling live in adapters that call pure builders and decoders and send through an injected function. A change that wants to read the clock, the network or the environment inside the decision logic has found a design problem, not a missing import.\n4. Keep Erlang calls in a named `*_ffi.erl` module beside the Gleam module that owns them, and nothing else may `@external`. Every process starts under a supervisor; a bare spawned process is a finding.\n5. Derive the test from the clause before implementing, and confirm it fails first. A test under `test\u002F` drives the decision logic with values and asserts the decision; an adapter test proves the HTTP or Kubernetes behaviour against a fake or the local cluster tier the test-tier decision assigns. A test already green proves nothing about the new behaviour.\n6. The controller writes only the annotations it owns on live Pod objects. It never changes replica counts, never touches a Deployment's pod template, and stops patching a pod once `deletionTimestamp` is set. A change that would do any of these is a specification question, not a code change.\n7. Run `just format-check`, `just build` and `just test`, then `just check` before handing back. Warnings are errors in `build` and in the gate alike, and `build` and `test` refuse a drifted `manifest.toml`; `gleam deps download` and a reviewed diff fix that, never a hand edit.\n8. Report by `file:line`: what changed, which clause it implements, and which test proves it.\n","# Change the controller\n\n1. Read `AGENTS.md` and `docs\u002Fdecisions\u002F0002-sans-io-boundaries.md`. Identify which module under `src\u002F` the change lands in and whether it changes what the controller writes to the cluster; an annotation, a label or a patch shape is part of the worker contract and so part of the change.\n2. Find the clause. Every behaviour has an owning module under `docs\u002Fspecs\u002F`; read the rule, its guards and its outcomes before writing code. If no clause says what you need, this is a `spec-change` first, not a judgement call in code.\n3. Put every effect behind the sans-IO boundary. Decision logic takes observations, a clock value and configuration as plain values and returns the decision; HTTP polls, Kubernetes reads and patches, timers and scheduling live in adapters that call pure builders and decoders and send through an injected function. A change that wants to read the clock, the network or the environment inside the decision logic has found a design problem, not a missing import.\n4. Keep Erlang calls in a named `*_ffi.erl` module beside the Gleam module that owns them, and nothing else may `@external`. Every process starts under a supervisor; a bare spawned process is a finding.\n5. Derive the test from the clause before implementing, and confirm it fails first. A test under `test\u002F` drives the decision logic with values and asserts the decision; an adapter test proves the HTTP or Kubernetes behaviour against a fake or the local cluster tier the test-tier decision assigns. A test already green proves nothing about the new behaviour.\n6. The controller writes only the annotations it owns on live Pod objects. It never changes replica counts, never touches a Deployment's pod template, and stops patching a pod once `deletionTimestamp` is set. A change that would do any of these is a specification question, not a code change.\n7. Run `just format-check`, `just build` and `just test`, then `just check` before handing back. Warnings are errors in `build` and in the gate alike, and `build` and `test` refuse a drifted `manifest.toml`; `gleam deps download` and a reviewed diff fix that, never a hand edit.\n8. Report by `file:line`: what changed, which clause it implements, and which test proves it.\n",{"name":5,"description":7},"main","d7cf7b41416446f1924f144702b74c385471561d",".agents\u002Fskills\u002Fgleam-change",0,"https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr","https:\u002F\u002Fgithub.com\u002FBiscuitBin","2026-11-15 07:44:15",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add BiscuitBin\u002Fknarr --skill gleam-change",{"tool":36,"command":37},"bunx","bunx skills add BiscuitBin\u002Fknarr --skill gleam-change",{"tool":39,"command":40},"pnpm","pnpm dlx skills add BiscuitBin\u002Fknarr --skill gleam-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgleam-change\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7EB5YS84RAQZ13PDA1E6GD9","witness","Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an autonomous run did not cheat its way to green.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwitness\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7EB5SXJ8DKATBNY3GJM3HE9","weed","Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweed\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7EB5N58XB3XF5TNMHBDK0R7","tend","Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftend\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7EB5KEEA1DJ28P9QH4E8JSN","spec-change","Change an Allium specification and carry the change through the tests and the implementation.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspec-change\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7EB5HPV64VRKGVKQ6B4WF8G","review-docs","Add or revise a handbook page so it satisfies the documentation contract and stays reachable.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freview-docs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7EB5FMQ5JXFDKEE6VMHK781","review-change","Review a change in this repository against its invariants, specifications, tests, and documentation contract.","https:\u002F\u002Fgithub.com\u002FBiscuitBin\u002Fknarr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freview-change\u002FSKILL.md",[],[]]