[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M784P0CGPQ48ENSDVWD1SV54":3,"skill-same:01M784P0CGPQ48ENSDVWD1SV54":101},{"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":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M784P0CGPQ48ENSDVWD1SV54","edgy-c4",null,"C4 model diagrams (Simon Brown) for one application of an EDGY architecture, as pages of an edgy-diagram delivery: the L1 system context derived from the EDGY document graph (Persons, partner systems) and L2 container pages written by hand, linked to the EDGY model by the application's id. A notation handler for edgy-diagram (extension contract 1): draw.io output, static shapes, rules C001–C007. Use it only for applications in a decided building block.","Rahola\u002Fedgy-skills","Rahola","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20344242?v=4","01M784MGJXTM1QWBCF4635ZW7X","Roope Ahola","01M784MGKX2JMBT2CBX1NBNTJX",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: edgy-c4\nversion: \"0.1.0\"\ndescription: >\n  C4 model diagrams (Simon Brown) for one application of an EDGY architecture, as pages of an\n  edgy-diagram delivery: the L1 system context derived from the EDGY document graph (Persons,\n  partner systems) and L2 container pages written by hand, linked to the EDGY model by the\n  application's id. A notation handler for edgy-diagram (extension contract 1): draw.io output,\n  static shapes, rules C001–C007. Use it only for applications in a decided building block.\ncategory: documentation\ntags: [diagram, drawio, c4, software-architecture, documentation, edgy, en]\nlanguages: [en]\nagents:\n  - claude-code\n  - generic\nrequires: [edgy-diagram]\ninstall: directory\ninputs:\n  - name: level\n    type: enum\n    values: [context, container]\n    description: >\n      context = L1 system context, derived from the EDGY graph; container = L2, from the\n      containers and relationships written on the page.\n  - name: system\n    type: text\n    description: The id of the application asset the page describes (e.g. APP-07)\noutputs:\n  - type: file\n    description: C4 pages inside the edgy-diagram draw.io file (and its preview and presentation)\nexamples:\n  - input: examples\u002Fc4-fare-engine.txt\n    output: draw.io pages c4-context-app-07 and c4-container-app-07\n---\n\n# edgy-c4 — C4 for one application\n\n## Purpose\n\nC4 (Simon Brown, c4model.com, CC BY 4.0) describes the software of one system at zoom levels.\nedgy-c4 draws **levels 1 and 2** for an application asset of an EDGY model. It is a *notation\nhandler* of edgy-diagram (`notation.json`, extension contract 1): a page with `notation: c4` is\ndrawn by `scripts\u002Fedgy_c4.py`, never by the EDGY parser, and its content never enters the EDGY\ndocument graph. EDGY stays the model; C4 is one more view of one of its applications.\n\n**When.** Only for applications in a *decided* building block (edgy-target-state): C4 describes\nhow a system is built, which is wasted on an application whose future is still open.\n\n**Install.** edgy-c4 needs the whole skill directory and edgy-diagram (`requires:`). The\nclaude-code and generic adapters install both; Vibe, Cursor and curl mode install SKILL.md only\nand refuse edgy-c4 with a message.\n\n## Agent Instructions\n\n1. Confirm the application is in a decided building block; otherwise propose the EDGY views only.\n2. Make sure the EDGY model gives the application an id, its users (*interacts with* or\n   *performs* → *requires*) and its *transfers* with data and technology.\n3. Add an L1 page (`level: context`); add an L2 page (`level: container`) only when the\n   containers are known — ask, never invent them. Name boundary crossings with `{container:}`.\n4. Generate with edgy-diagram and `--preview --qa`, fix every C-rule error and warning, and look\n   at every C4 page before delivery.\n\n## L1 — system context (derived)\n\n```text\n  - name: \"Fare engine — system context\"\n    notation: c4\n    level: context\n    system: APP-07\n```\n\nOr one page per application: `expand: per-application` with `notation: c4` and `level: context`.\nThe page is derived from the EDGY graph:\n\n| C4 | From the EDGY model |\n|----|---------------------|\n| Software System (centre) | the application asset `system:` |\n| Person | people \u002F organisations that *interact with* it |\n| Person, **inferred** (dashed, lighter) | people \u002F organisations that *perform* a process that *requires* it — a stakeholder, not an observed user |\n| Software System (partners) | the other end of its *transfers*; `[external]` ones grey |\n| Relationship | the transfers: data names and `[technology]` |\n\nA system without any Person is a **note** (the page still passes strict lint): add an\n*interacts with* or *performs* link to the model when the users are known. Model elements\nwritten on an L1 page (`- person: \"Fare analyst\" {id: PEO-02}`, `- system: … {id: APP-05}`) are\nadded to the derived ones; such a hand-written page must list its own `system:` (C005).\n\n## L2 — containers (written on the page)\n\n```text\n  - name: \"Fare engine — containers\"\n    notation: c4\n    level: container\n    system: APP-07\n    elements:\n      - container: \"Fare API - Answers price queries\" {id: C-FARE-API, technology: Kotlin}\n      - container: \"Fare rules store\" {id: C-FARE-DB, technology: PostgreSQL}\n    relationships:\n      - \"C-FARE-API\" -> \"C-FARE-DB\": \"reads and writes fare rules\" {technology: JDBC}\n```\n\n- Container ids are unique in the document, follow the id pattern and are at most 64\n  characters.\n- Every relationship has a description and `{technology:}`.\n- **Boundary crossings** come from the EDGY model: `{container: C-FARE-API}` on a *transfers*\n  of the system names the container the transfer enters or leaves. A transfer between two\n  decomposed applications names both: `{container: \"C-WEB; C-FARE-API\"}`. The key is inert on\n  EDGY pages, in the ArchiMate export and in an EDGY-only delivery. In a delivery with C4 pages\n  every `{container:}` must resolve (C001): for an L1-only delivery, add the L2 page or leave the\n  keys out of the model.\n- The L2 page links back to its L1 page, and the L1 system card links to its L2 page.\n\n## Rules\n\n| Rule | Severity | Checks |\n|------|----------|--------|\n| C001 | error | `{container:}` names an unknown or invalid container, or one of neither endpoint; an L2 relationship names an undeclared id |\n| C002 | warning | a relationship without a description |\n| C003 | warning | an L2 relationship (or boundary crossing) without a technology |\n| C004 | error | `system:` is not an application asset, or is a platform \u002F integration kind; `level:` is not `context` or `container` |\n| C005 | warning | `system:` is not drawn on its hand-written L1 page |\n| C006 | error | a container id declared twice, or two pages for the same level and system |\n| C007 | error | a line of an `elements:` or `relationships:` section that cannot be read (a missing brace, a stray item) — never dropped silently |\n\nAn error stops the generator (exit 2, no file). C001 and C006 are checked in the notation\nprepass over all C4 pages, so page order never matters.\n\n## Output\n\ndraw.io only (C4-PlantUML is planned for 0.2.0). Static styled rectangles and the `person`\nshape, `edgyNotation=c4` on every cell, page ids `c4-context-\u003Csystem>` and\n`c4-container-\u003Csystem>`. Every page carries the legend **\"C4 model (Simon Brown, CC BY 4.0)\"**.\nThe native preview, the presenter and `edgy_lint.py` draw and check the pages through the\ngeneric renderer; `--qa` and strict lint apply as for EDGY pages.\n\n```bash\npython3 \u003Cedgy-diagram>\u002Fscripts\u002Fedgy_generator.py examples\u002Fc4-fare-engine.txt --output c4.drawio --preview --qa\n```\n\nLook at the preview before delivery, as for every edgy-diagram page.\n","# edgy-c4 — C4 for one application\n\n## Purpose\n\nC4 (Simon Brown, c4model.com, CC BY 4.0) describes the software of one system at zoom levels.\nedgy-c4 draws **levels 1 and 2** for an application asset of an EDGY model. It is a *notation\nhandler* of edgy-diagram (`notation.json`, extension contract 1): a page with `notation: c4` is\ndrawn by `scripts\u002Fedgy_c4.py`, never by the EDGY parser, and its content never enters the EDGY\ndocument graph. EDGY stays the model; C4 is one more view of one of its applications.\n\n**When.** Only for applications in a *decided* building block (edgy-target-state): C4 describes\nhow a system is built, which is wasted on an application whose future is still open.\n\n**Install.** edgy-c4 needs the whole skill directory and edgy-diagram (`requires:`). The\nclaude-code and generic adapters install both; Vibe, Cursor and curl mode install SKILL.md only\nand refuse edgy-c4 with a message.\n\n## Agent Instructions\n\n1. Confirm the application is in a decided building block; otherwise propose the EDGY views only.\n2. Make sure the EDGY model gives the application an id, its users (*interacts with* or\n   *performs* → *requires*) and its *transfers* with data and technology.\n3. Add an L1 page (`level: context`); add an L2 page (`level: container`) only when the\n   containers are known — ask, never invent them. Name boundary crossings with `{container:}`.\n4. Generate with edgy-diagram and `--preview --qa`, fix every C-rule error and warning, and look\n   at every C4 page before delivery.\n\n## L1 — system context (derived)\n\n```text\n  - name: \"Fare engine — system context\"\n    notation: c4\n    level: context\n    system: APP-07\n```\n\nOr one page per application: `expand: per-application` with `notation: c4` and `level: context`.\nThe page is derived from the EDGY graph:\n\n| C4 | From the EDGY model |\n|----|---------------------|\n| Software System (centre) | the application asset `system:` |\n| Person | people \u002F organisations that *interact with* it |\n| Person, **inferred** (dashed, lighter) | people \u002F organisations that *perform* a process that *requires* it — a stakeholder, not an observed user |\n| Software System (partners) | the other end of its *transfers*; `[external]` ones grey |\n| Relationship | the transfers: data names and `[technology]` |\n\nA system without any Person is a **note** (the page still passes strict lint): add an\n*interacts with* or *performs* link to the model when the users are known. Model elements\nwritten on an L1 page (`- person: \"Fare analyst\" {id: PEO-02}`, `- system: … {id: APP-05}`) are\nadded to the derived ones; such a hand-written page must list its own `system:` (C005).\n\n## L2 — containers (written on the page)\n\n```text\n  - name: \"Fare engine — containers\"\n    notation: c4\n    level: container\n    system: APP-07\n    elements:\n      - container: \"Fare API - Answers price queries\" {id: C-FARE-API, technology: Kotlin}\n      - container: \"Fare rules store\" {id: C-FARE-DB, technology: PostgreSQL}\n    relationships:\n      - \"C-FARE-API\" -> \"C-FARE-DB\": \"reads and writes fare rules\" {technology: JDBC}\n```\n\n- Container ids are unique in the document, follow the id pattern and are at most 64\n  characters.\n- Every relationship has a description and `{technology:}`.\n- **Boundary crossings** come from the EDGY model: `{container: C-FARE-API}` on a *transfers*\n  of the system names the container the transfer enters or leaves. A transfer between two\n  decomposed applications names both: `{container: \"C-WEB; C-FARE-API\"}`. The key is inert on\n  EDGY pages, in the ArchiMate export and in an EDGY-only delivery. In a delivery with C4 pages\n  every `{container:}` must resolve (C001): for an L1-only delivery, add the L2 page or leave the\n  keys out of the model.\n- The L2 page links back to its L1 page, and the L1 system card links to its L2 page.\n\n## Rules\n\n| Rule | Severity | Checks |\n|------|----------|--------|\n| C001 | error | `{container:}` names an unknown or invalid container, or one of neither endpoint; an L2 relationship names an undeclared id |\n| C002 | warning | a relationship without a description |\n| C003 | warning | an L2 relationship (or boundary crossing) without a technology |\n| C004 | error | `system:` is not an application asset, or is a platform \u002F integration kind; `level:` is not `context` or `container` |\n| C005 | warning | `system:` is not drawn on its hand-written L1 page |\n| C006 | error | a container id declared twice, or two pages for the same level and system |\n| C007 | error | a line of an `elements:` or `relationships:` section that cannot be read (a missing brace, a stray item) — never dropped silently |\n\nAn error stops the generator (exit 2, no file). C001 and C006 are checked in the notation\nprepass over all C4 pages, so page order never matters.\n\n## Output\n\ndraw.io only (C4-PlantUML is planned for 0.2.0). Static styled rectangles and the `person`\nshape, `edgyNotation=c4` on every cell, page ids `c4-context-\u003Csystem>` and\n`c4-container-\u003Csystem>`. Every page carries the legend **\"C4 model (Simon Brown, CC BY 4.0)\"**.\nThe native preview, the presenter and `edgy_lint.py` draw and check the pages through the\ngeneric renderer; `--qa` and strict lint apply as for EDGY pages.\n\n```bash\npython3 \u003Cedgy-diagram>\u002Fscripts\u002Fedgy_generator.py examples\u002Fc4-fare-engine.txt --output c4.drawio --preview --qa\n```\n\nLook at the preview before delivery, as for every edgy-diagram page.\n",{"name":5,"tags":24,"agents":32,"inputs":35,"install":47,"outputs":48,"version":52,"category":29,"examples":53,"requires":57,"languages":59,"description":60},[25,26,27,28,29,30,31],"diagram","drawio","c4","software-architecture","documentation","edgy","en",[33,34],"claude-code","generic",[36,43],{"name":37,"type":38,"values":39,"description":42},"level","enum",[40,41],"context","container","context = L1 system context, derived from the EDGY graph; container = L2, from the containers and relationships written on the page.\n",{"name":44,"type":45,"description":46},"system","text","The id of the application asset the page describes (e.g. APP-07)","directory",[49],{"type":50,"description":51},"file","C4 pages inside the edgy-diagram draw.io file (and its preview and presentation)","0.1.0",[54],{"input":55,"output":56},"examples\u002Fc4-fare-engine.txt","draw.io pages c4-context-app-07 and c4-container-app-07",[58],"edgy-diagram",[31],"C4 model diagrams (Simon Brown) for one application of an EDGY architecture, as pages of an edgy-diagram delivery: the L1 system context derived from the EDGY document graph (Persons, partner systems) and L2 container pages written by hand, linked to the EDGY model by the application's id. A notation handler for edgy-diagram (extension contract 1): draw.io output, static shapes, rules C001–C007. Use it only for applications in a decided building block.\n","main","511bd269dc3dabd710d5897c5df7681d818a3625","skills\u002Fdocumentation\u002Fedgy-c4",0,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills","https:\u002F\u002Fgithub.com\u002FRahola","2026-10-19 17:50:29",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add Rahola\u002Fedgy-skills --skill edgy-c4",{"tool":74,"command":75},"bunx","bunx skills add Rahola\u002Fedgy-skills --skill edgy-c4",{"tool":77,"command":78},"pnpm","pnpm dlx skills add Rahola\u002Fedgy-skills --skill edgy-c4","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002FSKILL.md",true,[82,87,91,97],{"path":55,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"REFERENCE","参考文档",2384,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002Fexamples\u002Fc4-fare-engine.txt",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"notation.json",66,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002Fnotation.json",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fedgy_c4.py","SCRIPT","脚本",35189,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002Fscripts\u002Fedgy_c4.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Ftest_c4.py",14866,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation\u002Fedgy-c4\u002Fscripts\u002Ftest_c4.py",[102,108,114,120,126,132],{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M784QCQ9RS33B79PPE4BTGRQ","fx-z","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-z\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M784QA58YX5YDAFM3ZX5TEQQ","fx-y","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-y\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M784Q7B642A6WFJ0X5FBM1EK","fx-x","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-x\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M784Q4AQVCVDAWQPAN1M1VCG","fx-w","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-w\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M784Q239PJGYYCGN0X3AQW1Q","fx-top","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-top\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M784PZD95CXDA4T4PRRFR1BY","fx-plugin","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-plugin\u002FSKILL.md",[],[]]