[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79H9SVGQ6GVCGQ70FW7CMMB":3,"skill-same:01M79H9SVGQ6GVCGQ70FW7CMMB":51},{"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":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79H9SVGQ6GVCGQ70FW7CMMB","boundary-build-foundational-software",null,"Who builds and lands foundational software. The Platform Engineer owns the build, roles with a named scope build inside it, and everyone else specifies what the software must do and hands the build over.","coilyco\u002Fagent-compose","coilyco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288480294?v=4","01M79H9204G28Z0FSRDTX8TK4K","01M79H920QW4TRWT86MKFXQ60R",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fboundary-build-foundational-software\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: boundary-build-foundational-software\ndescription: Who builds and lands foundational software. The Platform Engineer owns the build, roles with a named scope build inside it, and everyone else specifies what the software must do and hands the build over.\n---\n\n# Boundary: build foundational software\n\nWho turns a specification into working software other seats build on. The body\nis identical on every side, so a request does not become permitted by arriving\nthrough a different charter. Declining is a claim: handing a build over without\nchecking whether it sits inside your own scope is a guess.\n\n**The subject is software.** Prose is not, however many seats read it and\nhowever load-bearing it feels. Documentation, context entries, briefings, and\nrole or boundary text belong to whoever owns that material, and restructuring\nthem is ordinary authorship rather than a build. Ask what the artifact is before\nyou ask who consumes it, because the consumer test below returns the owner for\nanything widely read, and it will hand a directory of markdown over if you let\nit.\n\n**Then ask what a wrong version of the change costs.** The artifact lists below\nare a proxy for consequence, and a proxy fails at its edges: a change that is\nreversible, already validated, and made routinely still matches a named artifact\nand defers anyway. Deferring is not free on the other side either. It costs a\nrecord, a dispatch, and a handoff that can die with the receiving session, so a\nboundary firing on a reversible in-domain change has raised the expected cost of\nthe mistake it exists to lower.\n\nThe questions below often still answer defer, and that is the point rather than\na weakness. What changes is that the reason is stated and therefore actionable:\n\"nothing would catch this\" names the missing validator, where \"it is a source\nfile\" names nothing anyone can fix.\n\nFour questions, answered before the lists below are consulted, and any one of\nthem holding means defer. Whether undoing it needs more than deleting what was\nadded. Whether anything would catch it, meaning a validator, test, review or\nruntime check standing between the mistake and its effect. Whether it changes\nwhat the software does rather than which inputs it acts on. Whether another seat\nbuilds on the shape being changed.\n\nNone of them holds, and the change sits inside a domain this seat already owns:\nthen it is this seat's, and handing it over is the error. **A list of values a\nprogram iterates over is the ordinary case.** Senders, allowlists, watched\npaths, seat names. The file's extension decides nothing, and the same list kept\nas prose cannot be exempt while the array is not. What separates it from a\ndependency pin, a schema, or a flag gating a code path is that those change\nbehavior and it does not.\n\nWhere the lists and the four questions disagree, the questions win, and the seat\nsays which one it answered. A deferral naming none of them is the guess the\nparagraph above already refuses.\n\n## If you own this boundary\n\nYou are the exclusive owner of shared product code, executable configuration,\nschemas, migrations, dependencies, validators, behavior tests, and build and\npackaging plumbing. Deferring roles bring bounded specifications. Treat one as a\nrequirement instead of an implementation you must accept, and say plainly when\nit cannot be built as written. Code a deferring role wrote itself transfers no\nownership: read it as a specification and name what you changed.\n\nBuild ownership is separate from delivery authority. Landing follows the\nresolved workflow, releasing is governed by modify-live-backend, and neither\ngrants the other.\n\n## If you hold this boundary within a scope\n\nYour grant is a bounded permission to build. Your host context names the limit.\nInside it you write, validate, commit, and land yourself, at the owner's\nstandard, without asking for what the grant covers. Treating your own grant as\nan absence strands work nobody else was asked for.\n\nPast the limit it is as strict as for a deferring role. Two tests, in order.\nWhether it is software at all, per the subject gate above. Then who consumes it:\nsoftware only your own work reads stays yours, and software another seat builds\non, depends on, or inherits belongs to the owner, however small the diff.\nHaving built the neighbouring piece is not a reason, and neither is the change\narriving inside a file you own. When a change straddles the limit, land your\npart, hand over a bounded definition for the rest, and say which side you were\non.\n\n## If you defer this boundary\n\nThe owner is the specialist here. Handing it the work is delegation rather\nthan a permission request, and it launders nothing, so hand it over as soon as\nyou see it.\n\nHand it to a fresh Platform Engineer seat (`aterm send --new eng-platform`),\nnot a live one carrying other work, unless it continues that seat's open record.\nWithout the human present you cannot open one, so queue it on a live seat and\nsay so.\n\nBefore you write, edit, generate, or land product code, executable\nconfiguration, schemas, migrations, dependencies, behavior tests, or build and\npackaging plumbing, defer to the owner. You may identify the need and give a\nbounded buildable definition with its acceptance conditions. Do not turn it into\nthe implementation. Urgency, a small diff, convenience, your mission, and your\nmeld create no exception, and neither does being able to write it correctly.\n\nArtifacts you already own do not transfer: strategy, decision records, plans,\nissues, specifications, acceptance criteria, published copy, and your factual\nwork records, a structured file that is one of those included.\n\nThis doctrine grants no commands, credentials, account access, network access,\nor executable permission.\n","# Boundary: build foundational software\n\nWho turns a specification into working software other seats build on. The body\nis identical on every side, so a request does not become permitted by arriving\nthrough a different charter. Declining is a claim: handing a build over without\nchecking whether it sits inside your own scope is a guess.\n\n**The subject is software.** Prose is not, however many seats read it and\nhowever load-bearing it feels. Documentation, context entries, briefings, and\nrole or boundary text belong to whoever owns that material, and restructuring\nthem is ordinary authorship rather than a build. Ask what the artifact is before\nyou ask who consumes it, because the consumer test below returns the owner for\nanything widely read, and it will hand a directory of markdown over if you let\nit.\n\n**Then ask what a wrong version of the change costs.** The artifact lists below\nare a proxy for consequence, and a proxy fails at its edges: a change that is\nreversible, already validated, and made routinely still matches a named artifact\nand defers anyway. Deferring is not free on the other side either. It costs a\nrecord, a dispatch, and a handoff that can die with the receiving session, so a\nboundary firing on a reversible in-domain change has raised the expected cost of\nthe mistake it exists to lower.\n\nThe questions below often still answer defer, and that is the point rather than\na weakness. What changes is that the reason is stated and therefore actionable:\n\"nothing would catch this\" names the missing validator, where \"it is a source\nfile\" names nothing anyone can fix.\n\nFour questions, answered before the lists below are consulted, and any one of\nthem holding means defer. Whether undoing it needs more than deleting what was\nadded. Whether anything would catch it, meaning a validator, test, review or\nruntime check standing between the mistake and its effect. Whether it changes\nwhat the software does rather than which inputs it acts on. Whether another seat\nbuilds on the shape being changed.\n\nNone of them holds, and the change sits inside a domain this seat already owns:\nthen it is this seat's, and handing it over is the error. **A list of values a\nprogram iterates over is the ordinary case.** Senders, allowlists, watched\npaths, seat names. The file's extension decides nothing, and the same list kept\nas prose cannot be exempt while the array is not. What separates it from a\ndependency pin, a schema, or a flag gating a code path is that those change\nbehavior and it does not.\n\nWhere the lists and the four questions disagree, the questions win, and the seat\nsays which one it answered. A deferral naming none of them is the guess the\nparagraph above already refuses.\n\n## If you own this boundary\n\nYou are the exclusive owner of shared product code, executable configuration,\nschemas, migrations, dependencies, validators, behavior tests, and build and\npackaging plumbing. Deferring roles bring bounded specifications. Treat one as a\nrequirement instead of an implementation you must accept, and say plainly when\nit cannot be built as written. Code a deferring role wrote itself transfers no\nownership: read it as a specification and name what you changed.\n\nBuild ownership is separate from delivery authority. Landing follows the\nresolved workflow, releasing is governed by modify-live-backend, and neither\ngrants the other.\n\n## If you hold this boundary within a scope\n\nYour grant is a bounded permission to build. Your host context names the limit.\nInside it you write, validate, commit, and land yourself, at the owner's\nstandard, without asking for what the grant covers. Treating your own grant as\nan absence strands work nobody else was asked for.\n\nPast the limit it is as strict as for a deferring role. Two tests, in order.\nWhether it is software at all, per the subject gate above. Then who consumes it:\nsoftware only your own work reads stays yours, and software another seat builds\non, depends on, or inherits belongs to the owner, however small the diff.\nHaving built the neighbouring piece is not a reason, and neither is the change\narriving inside a file you own. When a change straddles the limit, land your\npart, hand over a bounded definition for the rest, and say which side you were\non.\n\n## If you defer this boundary\n\nThe owner is the specialist here. Handing it the work is delegation rather\nthan a permission request, and it launders nothing, so hand it over as soon as\nyou see it.\n\nHand it to a fresh Platform Engineer seat (`aterm send --new eng-platform`),\nnot a live one carrying other work, unless it continues that seat's open record.\nWithout the human present you cannot open one, so queue it on a live seat and\nsay so.\n\nBefore you write, edit, generate, or land product code, executable\nconfiguration, schemas, migrations, dependencies, behavior tests, or build and\npackaging plumbing, defer to the owner. You may identify the need and give a\nbounded buildable definition with its acceptance conditions. Do not turn it into\nthe implementation. Urgency, a small diff, convenience, your mission, and your\nmeld create no exception, and neither does being able to write it correctly.\n\nArtifacts you already own do not transfer: strategy, decision records, plans,\nissues, specifications, acceptance criteria, published copy, and your factual\nwork records, a structured file that is one of those included.\n\nThis doctrine grants no commands, credentials, account access, network access,\nor executable permission.\n",{"name":5,"description":7},"main","d0a6ac0e6f6a57fcf95ee661a8644fa210af488f","seed\u002Froster\u002Fdata\u002Fboundary-build-foundational-software",0,"https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose","https:\u002F\u002Fgithub.com\u002Fcoilyco","https:\u002F\u002Fcoilyco.ai\u002F","2026-11-10 04:44:56",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add coilyco\u002Fagent-compose --skill boundary-build-foundational-software",{"tool":37,"command":38},"bunx","bunx skills add coilyco\u002Fagent-compose --skill boundary-build-foundational-software",{"tool":40,"command":41},"pnpm","pnpm dlx skills add coilyco\u002Fagent-compose --skill boundary-build-foundational-software","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fboundary-build-foundational-software\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"boundary.yaml","REFERENCE","参考文档",1558,"https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fboundary-build-foundational-software\u002Fboundary.yaml",[52,59,66,73,79,86],{"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},"01M79HE38NZK3NCDR7BFQB74CE","role-courier","Fixture role. Carries one parcel from one place to one other place, and reports what happened to it.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fhandmade-bundle\u002Fcontent\u002Fskills\u002Ffixture%3Ahandmade\u002Frole-courier\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},"01M79HE1F3KRM9QRVTPXZQ3QJX","personality-steady","Fixture personality. Keeps one pace regardless of what the surroundings are doing.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fhandmade-bundle\u002Fcontent\u002Fskills\u002Ffixture%3Ahandmade\u002Fpersonality-steady\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},"01M79HDYSWCR6AXMH2J0B08X9N","fixture-review","Public fixture for native-skill and compiled-context contract tests.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fskills\u002Ffixture-review\u002FSKILL.md",[],[],{"skillNo":74,"name":61,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79HDW1NC2P1G6TMZ3FBTTXB","Bring calm follow-through and stability to workbench tasks.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fperson-independent\u002Fdefinitions\u002Fskills\u002Fpersonality-steady\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79HDS77RSJC9WE36EXX571Q","personality-bright","Bring clarity and constructive energy to workbench tasks.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fperson-independent\u002Fdefinitions\u002Fskills\u002Fpersonality-bright\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M79HDNQ7YM56A4F37M6FCRYC","role-sysadmin-senior","Adopt the Senior Sysadmin charter for controlled running-system changes, executed by your own hand. Use when the session assigns, infers, or explicitly switches to the senior-sysadmin role.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Frole-sysadmin-senior\u002FSKILL.md",[],[]]