[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWE7VS6CWD1KFG57G02RGC":3,"skill-same:01M6WWE7VS6CWD1KFG57G02RGC":48},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":13,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M6WWE7VS6CWD1KFG57G02RGC","standard-application-engineering",null,"projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-application-engineering\u002FSKILL.md",[],[18,19,20,21],"engineering","application","standard","standard application engineering","2026-11-10 10:12:30",false,"---\nname: standard-application-engineering\ndescription: Company application engineering standards: application profiles, Twelve-Factor alignment, CLI command grammar (Unix, kubectl, or OpenStackClient style), layered configuration, output\u002Flogging\u002Fevidence channels, and compatibility of machine interfaces. Use when building or changing a CLI, service, worker, or MCP server's commands, options, configuration, output, logs, JSON results, schemas, or public contracts, or when deciding which standards apply to a product.\n---\n\n# standard-application-engineering\n\n\u003C!-- generated by standards.py from projectious-work\u002Fstandards; do not edit -->\n\nBinding company standard. The rules below are the summary; the linked file is authoritative. Read only the section the task needs.\n\n## Application profiles for engineering standards\n\nSelect standards by product behavior, not implementation language. Declare\nevery applicable profile, combine their requirements, and make exceptions\nexplicit and reviewable. Services, workers, and remote MCP servers follow\n*Twelve-Factor App* with the listed deviations: layered CLI configuration,\nlocal release, development containers, and evidence as a separate channel.\n\nFull standard: `.standards\u002Fapplication-profiles.md`. Sections:\n\n- Purpose\n- Profiles\n- Twelve-Factor alignment\n- Conditional overlays\n- Composite products\n- Applicability record\n\n## Command-line interface design standard\n\nEach CLI picks one recorded style (ADR): A Unix utility `tool [opts]\n[operands]`, B verb–resource `tool \u003Cverb> \u003Ctype> [\u003Cname>]` (kubectl), or C\nobject–action `tool \u003Cobject> \u003Caction>` (OpenStackClient). All follow the\n*Unix Philosophy* and the baseline: `--help` with examples, `--version`,\nlong names for all options, `--` and `-`, machine envelope as contract, no\nsecrets in options, prompts only on a TTY, `--dry-run` for destructive use.\n\nFull standard: `.standards\u002Fcommand-line-interface-design.md`. Sections:\n\n- Purpose and scope\n- Choosing a style\n- Baseline for every style\n- A. Unix utility style\n- B. Verb–resource style (kubectl)\n- C. Object–action style (OpenStackClient)\n\n## Application configuration standard\n\nConfiguration precedence answers which source wins; authority answers\nwhether that source may set the key at all. Preserve both, expose redacted\nprovenance, and never use committed project configuration as an implicit\nprivilege escalation path. Services and workers are environment-first\n(*Twelve-Factor App* III); layered files are for CLIs.\n\nFull standard: `.standards\u002Fapplication-configuration.md`. Sections:\n\n- Purpose and scope\n- Precedence\n- Authority is separate from precedence\n- File and value behavior\n- Effective configuration and provenance\n- Testing\n\n## Application output, logging, and evidence standard\n\nOutput answers the request. Logs are a disposable event stream that explains\noperation (*Twelve-Factor App* XI). Evidence is a durable record written on\npurpose that must survive log loss; a log line is never proof. Do not collapse\nthese channels. Structure and redact events before rendering or export.\n\nFull standard: `.standards\u002Fapplication-output-logging-and-evidence.md`. Sections:\n\n- Purpose and scope\n- Three information channels\n- Semantic events and rendering\n- Streams and formats\n- Redaction and data handling\n- Failure and correlation\n- Evidence integrity\n- Testing\n\n## Compatibility and machine-interface standard\n\nTreat public and persisted machine interfaces as products. Version their\nmeaning, keep human rendering separate, prove rejection behavior, and never\ncall a change compatible based only on syntactic schema compatibility.\n\nFull standard: `.standards\u002Fcompatibility-and-machine-interfaces.md`. Sections:\n\n- Purpose and scope\n- Versioning\n- Machine-readable results\n- CLI profile\n- Change classification\n- Contract verification\n","# standard-application-engineering\n\n\u003C!-- generated by standards.py from projectious-work\u002Fstandards; do not edit -->\n\nBinding company standard. The rules below are the summary; the linked file is authoritative. Read only the section the task needs.\n\n## Application profiles for engineering standards\n\nSelect standards by product behavior, not implementation language. Declare\nevery applicable profile, combine their requirements, and make exceptions\nexplicit and reviewable. Services, workers, and remote MCP servers follow\n*Twelve-Factor App* with the listed deviations: layered CLI configuration,\nlocal release, development containers, and evidence as a separate channel.\n\nFull standard: `.standards\u002Fapplication-profiles.md`. Sections:\n\n- Purpose\n- Profiles\n- Twelve-Factor alignment\n- Conditional overlays\n- Composite products\n- Applicability record\n\n## Command-line interface design standard\n\nEach CLI picks one recorded style (ADR): A Unix utility `tool [opts]\n[operands]`, B verb–resource `tool \u003Cverb> \u003Ctype> [\u003Cname>]` (kubectl), or C\nobject–action `tool \u003Cobject> \u003Caction>` (OpenStackClient). All follow the\n*Unix Philosophy* and the baseline: `--help` with examples, `--version`,\nlong names for all options, `--` and `-`, machine envelope as contract, no\nsecrets in options, prompts only on a TTY, `--dry-run` for destructive use.\n\nFull standard: `.standards\u002Fcommand-line-interface-design.md`. Sections:\n\n- Purpose and scope\n- Choosing a style\n- Baseline for every style\n- A. Unix utility style\n- B. Verb–resource style (kubectl)\n- C. Object–action style (OpenStackClient)\n\n## Application configuration standard\n\nConfiguration precedence answers which source wins; authority answers\nwhether that source may set the key at all. Preserve both, expose redacted\nprovenance, and never use committed project configuration as an implicit\nprivilege escalation path. Services and workers are environment-first\n(*Twelve-Factor App* III); layered files are for CLIs.\n\nFull standard: `.standards\u002Fapplication-configuration.md`. Sections:\n\n- Purpose and scope\n- Precedence\n- Authority is separate from precedence\n- File and value behavior\n- Effective configuration and provenance\n- Testing\n\n## Application output, logging, and evidence standard\n\nOutput answers the request. Logs are a disposable event stream that explains\noperation (*Twelve-Factor App* XI). Evidence is a durable record written on\npurpose that must survive log loss; a log line is never proof. Do not collapse\nthese channels. Structure and redact events before rendering or export.\n\nFull standard: `.standards\u002Fapplication-output-logging-and-evidence.md`. Sections:\n\n- Purpose and scope\n- Three information channels\n- Semantic events and rendering\n- Streams and formats\n- Redaction and data handling\n- Failure and correlation\n- Evidence integrity\n- Testing\n\n## Compatibility and machine-interface standard\n\nTreat public and persisted machine interfaces as products. Version their\nmeaning, keep human rendering separate, prove rejection behavior, and never\ncall a change compatible based only on syntactic schema compatibility.\n\nFull standard: `.standards\u002Fcompatibility-and-machine-interfaces.md`. Sections:\n\n- Purpose and scope\n- Versioning\n- Machine-readable results\n- CLI profile\n- Change classification\n- Contract verification\n",{},"main","ee2efce442098152b5028ef01a10ee8a1735c5b2",".agents\u002Fskills\u002Fstandard-application-engineering","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":7,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add projectious-work\u002Fprocesskit --skill standard-application-engineering",{"tool":40,"command":41},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill standard-application-engineering",{"tool":43,"command":44},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill standard-application-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-application-engineering\u002FSKILL.md",true,[],[49,56,63,69,97,117],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":55},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":22},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,85,86,87,88,89,90,91,92,71,93,94,95,96],"management","skill management","ontology","v1","create","as","work","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":22},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[103],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[105,106,81,107,108,109,110,111,112,113,114,115,87,89,90,92,116],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":22},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[124,81,125,126,85,127,128,129,87,89,130,131,91,132,92,133,134,135,136,137],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]