[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ECGJT6SZXPH9PDSJ74TTC":3,"skill-same:01M79ECGJT6SZXPH9PDSJ74TTC":65},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79ECGJT6SZXPH9PDSJ74TTC","pr-lens",null,"WHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request","AO-HyS\u002Fdevelopment-system","AO-HyS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286554351?v=4","01M79DCXZGC6076EH5QATNXCY2","AO HyS","01M79DCY06TSBCJ946VP0BT0RG",0,"MIT","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-lens\ndescription: \"WHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request\"\n---\n\n# PR Lens\n\nPR Lens draws code as visually rich animated diagrams. It can represent diffs, architecture, data flows, and more.\n\nThe diff or code is represented as one JSON document (lanes, nodes, edges, ordered flows) and it renders the JSON as an animated SVG\n\n## Operating manual\n\n1. **Read the diff.** When asked to represent a code change: `git diff --find-renames \u003Cbase>...\u003Chead>`. The base is the merge base, not the tip of the base branch.\n\n   If not expressing a code diff, read the code to be visually represented\n\n2. **Write the document** to `.pr-lens\u002Fgraph.json`, following `references\u002Fgraph-document.md`. `references\u002Fexample.graph.json` is valid reference with three lanes, all four delta states, a hero edge, a seven-step flow, a nested drill-down tree. Read it before you write your first one. It is quicker than reading the reference.\n\n3. **Validate, and fix**\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 validate .pr-lens\u002Fgraph.json\n   ```\n\n   Fix every failure and run it again. Do not render an invalid document; do not \"work around\" a failure by deleting the element it names.\n\n4. **Render.**\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 render .pr-lens\u002Fgraph.json --theme dark\n   ```\n\n   Render dark as the default theme unless explicitly requested. The SVGs, the manifest and `drawn.graph.json` land in `.pr-lens\u002F`, which the CLI adds to the repository's .gitignore. Do not commit any of it. These files are rebuilt from the diff whenever anyone wants them again. Each SVG is named after its view, the theme and a content hash; `manifest.json` lists them by lens and view, so read the names from there or from the directory.\n\n   Keep diagrams local by default and return the generated SVG path. A request\n   to explain code does not authorize uploading it. Use a private temporary\n   directory when generating outside a requested repository change.\n   Run `canvas push` only when the user explicitly authorized publishing this\n   diagram to the public PR Lens service. Never expose canvas edit tokens.\n   Authorization to open a PR covers its intended description and attachments,\n   not a separate public canvas. Verify the target repository and visibility.\n\n5. **Attach, when there is a pull request to attach to.** That means the user asked you to open a PR, asked for a diagram on one that exists, or you are opening a PR as part of changes made. Otherwise skip this step.\n\n   GitHub CLI uploads the diagram with the pull request. Write the body with a Markdown image pointing at the local file, then pass the same path to `--attach`. `gh` rewrites the reference to the uploaded asset and keeps the alt text you wrote:\n\n   ```markdown\n   Moves bulk sending off the per-recipient trigger and onto a batch endpoint.\n\n   ![Architecture after this change: the queue route, the new bulk sender and the retired per-recipient path](.pr-lens\u002Foverview-dark-4f9bd6c1.svg)\n   ```\n\n   ```bash\n   gh pr create --title \"Batch broadcast sends\" --body-file .pr-lens\u002Fbody.md \\\n     --attach .pr-lens\u002Foverview-dark-4f9bd6c1.svg\n   ```\n\n   On a pull request that already exists, `gh pr edit \u003Cnumber>` with the same two flags puts the diagram in the description, and `gh pr comment \u003Cnumber>` puts it in a comment. Repeat `--attach` for each diagram the body references.\n\n   gh has three rules:\n   - The reference has to be a Markdown image, `![alt](path)`. An HTML `\u003Cimg>` or `\u003Cpicture>` is left as written, and the file is appended at the bottom of the body instead.\n   - The alt text is the caption a reader without images gets. Say what the diagram shows, in one line.\n   - `--attach` arrived in GitHub CLI 2.99. Check with `gh --version` before you write a body around it.\n\n   Attach the views a reviewer needs and leave the rest in `.pr-lens\u002F`: the top architecture view first, then a data flow if the change has a sequence worth following. A body with four diagrams reads worse than one with two, except the four are really needed to understand the change e.g., in the case of a complex feature or refactor.\n\n   When `--attach` is not an option, publish the SVGs somewhere durable and let the CLI compose the comment instead:\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 comment \\\n     --graph .pr-lens\u002Fdrawn.graph.json \\\n     --manifest .pr-lens\u002Fmanifest.json \\\n     --asset-base-url https:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cowner>\u002F\u003Crepo>\u002F\u003Cbranch>\u002F\u003Cdir>\n   ```\n\n   `--graph` takes `drawn.graph.json`, not the document you wrote, because corrections change what the diagrams show and the CLI refuses a document its manifest does not describe. `--asset-base-url` is where you published the SVGs; leave it out and the markdown points at local paths no reader can fetch. The markdown goes to stdout, with each diagram as a `\u003Cpicture>` pair; posting it is your business.\n\nAuthor the graph directly with the current model; `validate` and `render` need\nno second LLM account. Do not run provider-backed `analyze` unless the user asks\nfor that additional inference path. The renderer has no model usage fee;\nprovider usage and hosting may have independent costs.\n\n## The pull request body, when there is one\n\nA reviewer should understand the change before reading the diff, so the diagram goes where they look first: the description, not a trailing comment. Open with one sentence on why the change exists, then the architecture diagram, then whatever proves the change works, such as a screenshot of the result or a recording of the interaction. Use one visual per idea. A diagram that needs a paragraph of explanation has a document problem; go back to step 2.\n\n## What makes a document worth reading\n\n- **Include what did not change.** A diagram of only the changed nodes says nothing about blast radius. The unchanged neighbours a change touches are the context; mark them `delta: \"unchanged\"`.\n- **Lanes are the reader's mental model** (a runtime, a tier, a boundary), not the folder tree.\n- **One hero edge**, two at the outside: the connection the change is really about.\n- **Add a flow only when there is a sequence** worth animating. One good flow beats three thin ones.\n- **Attach file refs**: they become the permalinks a reviewer clicks.\n- **There is no findings lens.** PR Lens is the comprehension layer, not another review bot. There is no field for a bug, a risk or a security note, and a document that invents one is rejected rather than trimmed.\n\n## Choosing architecture views\n\nTreat architecture views as a C4-inspired decision tree, not a checklist. One useful view is enough for a small change. Start with system context when the change affects a user, an external system or a system boundary. Use a container view for the affected applications, services, jobs, data stores and runtimes. Add a component child only when an affected container's internals matter. Do not add code-level views by default.\n\nEvery child moves down one level and covers a materially narrower scope. Skip empty, repetitive or speculative levels, and do not infer architecture from folder names alone. Two views should not carry substantially the same nodes and edges. Keep the unchanged direct neighbours that explain blast radius.\n\nKeep data-flow views as separate roots rather than nesting them in the architecture tree. Set `defaultOpen: true` on the highest useful architecture view. Lower levels should normally keep the default, `false`.\n\n## What the validator will catch\n\nRead `references\u002Fgraph-document.md` before writing. The four failures that account for nearly everything:\n\n| Code                         | What you did                                                         |\n| ---------------------------- | -------------------------------------------------------------------- |\n| `BROKEN_REFERENCE`           | an edge, a flow step or a view names an id you never declared        |\n| `INVALID_DOCUMENT`           | an invented field; the schemas are strict, unknown keys are rejected |\n| `DUPLICATE_ID`               | two nodes, edges or views sharing an id                              |\n| `UNSUPPORTED_SCHEMA_VERSION` | `schemaVersion` is not the contract version installed                |\n\nFour rules cannot be expressed in JSON Schema and are checked only by the parser, so structured output alone does not make a document valid: referential integrity, a line range that ends before it starts, a `self` message whose endpoints disagree, and a patch whose two commits are the same. Always validate.\n\n## Fixing a map instead of writing one\n\nWhen someone says the diagram is wrong (a node is misnamed, a folder should not be on it, something sits in the wrong lane), do not edit the generated document. It is regenerated on every run. Write the correction into `.github\u002Fpr-lens.yml`, which is an overlay applied over fresh inference every time:\n\n```yaml\nschemaVersion: 0.1.0\nmap:\n  rename:\n    - match: functions\u002Fsrc\u002Fbroadcast\u002FsendBroadcastBulk.ts\n      to: Broadcast sender\n  exclude:\n    - \"**\u002F*.test.ts\"\n  lane:\n    - match: packages\u002Fbroadcast-lib\u002F**\n      lane: functions\n```\n\n`references\u002Fconfig.md` has the full format and the recipes. Validate it the same way: `npx @coldtea\u002Fpr-lens-cli@0.2.0 validate .github\u002Fpr-lens.yml`.\n\nA `match` beginning with `id:` addresses one node exactly; anything else is a path glob matched against a node's file paths. Prefer the glob, because it keeps holding when the next run names the node differently. A lane pin may name a lane the document never declared: the band is created, and takes the id for its label, so give it one a reader would want to see.\n\n`pr-lens render` says so when a correction matched nothing, which is how a config that has drifted, because the file it named moved or was deleted, becomes visible instead of quietly doing nothing.\n\n## What ships with this skill\n\nEverything you need is beside this page. Nothing here asks you to install a package first.\n\n|                                 |                                                                                    |\n| ------------------------------- | ---------------------------------------------------------------------------------- |\n| `references\u002Fgraph-document.md`  | the document, field by field: enums, limits, and where documents actually go wrong |\n| `references\u002Fconfig.md`          | `.github\u002Fpr-lens.yml`, the correction overlay, in full                             |\n| `references\u002Fexample.graph.json` | one complete document that validates, to read and to copy the shape of             |\n\nThe same document ships as `postmark-refactor.graph.json` in `@coldtea\u002Fpr-lens-schema`, and the JSON Schema the validator enforces is published at `https:\u002F\u002Funpkg.com\u002F@coldtea\u002Fpr-lens-schema\u002Fjson-schema\u002Fgraph-doc.schema.json`. Neither is something you need to fetch to write a document.\n","# PR Lens\n\nPR Lens draws code as visually rich animated diagrams. It can represent diffs, architecture, data flows, and more.\n\nThe diff or code is represented as one JSON document (lanes, nodes, edges, ordered flows) and it renders the JSON as an animated SVG\n\n## Operating manual\n\n1. **Read the diff.** When asked to represent a code change: `git diff --find-renames \u003Cbase>...\u003Chead>`. The base is the merge base, not the tip of the base branch.\n\n   If not expressing a code diff, read the code to be visually represented\n\n2. **Write the document** to `.pr-lens\u002Fgraph.json`, following `references\u002Fgraph-document.md`. `references\u002Fexample.graph.json` is valid reference with three lanes, all four delta states, a hero edge, a seven-step flow, a nested drill-down tree. Read it before you write your first one. It is quicker than reading the reference.\n\n3. **Validate, and fix**\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 validate .pr-lens\u002Fgraph.json\n   ```\n\n   Fix every failure and run it again. Do not render an invalid document; do not \"work around\" a failure by deleting the element it names.\n\n4. **Render.**\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 render .pr-lens\u002Fgraph.json --theme dark\n   ```\n\n   Render dark as the default theme unless explicitly requested. The SVGs, the manifest and `drawn.graph.json` land in `.pr-lens\u002F`, which the CLI adds to the repository's .gitignore. Do not commit any of it. These files are rebuilt from the diff whenever anyone wants them again. Each SVG is named after its view, the theme and a content hash; `manifest.json` lists them by lens and view, so read the names from there or from the directory.\n\n   Keep diagrams local by default and return the generated SVG path. A request\n   to explain code does not authorize uploading it. Use a private temporary\n   directory when generating outside a requested repository change.\n   Run `canvas push` only when the user explicitly authorized publishing this\n   diagram to the public PR Lens service. Never expose canvas edit tokens.\n   Authorization to open a PR covers its intended description and attachments,\n   not a separate public canvas. Verify the target repository and visibility.\n\n5. **Attach, when there is a pull request to attach to.** That means the user asked you to open a PR, asked for a diagram on one that exists, or you are opening a PR as part of changes made. Otherwise skip this step.\n\n   GitHub CLI uploads the diagram with the pull request. Write the body with a Markdown image pointing at the local file, then pass the same path to `--attach`. `gh` rewrites the reference to the uploaded asset and keeps the alt text you wrote:\n\n   ```markdown\n   Moves bulk sending off the per-recipient trigger and onto a batch endpoint.\n\n   ![Architecture after this change: the queue route, the new bulk sender and the retired per-recipient path](.pr-lens\u002Foverview-dark-4f9bd6c1.svg)\n   ```\n\n   ```bash\n   gh pr create --title \"Batch broadcast sends\" --body-file .pr-lens\u002Fbody.md \\\n     --attach .pr-lens\u002Foverview-dark-4f9bd6c1.svg\n   ```\n\n   On a pull request that already exists, `gh pr edit \u003Cnumber>` with the same two flags puts the diagram in the description, and `gh pr comment \u003Cnumber>` puts it in a comment. Repeat `--attach` for each diagram the body references.\n\n   gh has three rules:\n   - The reference has to be a Markdown image, `![alt](path)`. An HTML `\u003Cimg>` or `\u003Cpicture>` is left as written, and the file is appended at the bottom of the body instead.\n   - The alt text is the caption a reader without images gets. Say what the diagram shows, in one line.\n   - `--attach` arrived in GitHub CLI 2.99. Check with `gh --version` before you write a body around it.\n\n   Attach the views a reviewer needs and leave the rest in `.pr-lens\u002F`: the top architecture view first, then a data flow if the change has a sequence worth following. A body with four diagrams reads worse than one with two, except the four are really needed to understand the change e.g., in the case of a complex feature or refactor.\n\n   When `--attach` is not an option, publish the SVGs somewhere durable and let the CLI compose the comment instead:\n\n   ```bash\n   npx @coldtea\u002Fpr-lens-cli@0.2.0 comment \\\n     --graph .pr-lens\u002Fdrawn.graph.json \\\n     --manifest .pr-lens\u002Fmanifest.json \\\n     --asset-base-url https:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cowner>\u002F\u003Crepo>\u002F\u003Cbranch>\u002F\u003Cdir>\n   ```\n\n   `--graph` takes `drawn.graph.json`, not the document you wrote, because corrections change what the diagrams show and the CLI refuses a document its manifest does not describe. `--asset-base-url` is where you published the SVGs; leave it out and the markdown points at local paths no reader can fetch. The markdown goes to stdout, with each diagram as a `\u003Cpicture>` pair; posting it is your business.\n\nAuthor the graph directly with the current model; `validate` and `render` need\nno second LLM account. Do not run provider-backed `analyze` unless the user asks\nfor that additional inference path. The renderer has no model usage fee;\nprovider usage and hosting may have independent costs.\n\n## The pull request body, when there is one\n\nA reviewer should understand the change before reading the diff, so the diagram goes where they look first: the description, not a trailing comment. Open with one sentence on why the change exists, then the architecture diagram, then whatever proves the change works, such as a screenshot of the result or a recording of the interaction. Use one visual per idea. A diagram that needs a paragraph of explanation has a document problem; go back to step 2.\n\n## What makes a document worth reading\n\n- **Include what did not change.** A diagram of only the changed nodes says nothing about blast radius. The unchanged neighbours a change touches are the context; mark them `delta: \"unchanged\"`.\n- **Lanes are the reader's mental model** (a runtime, a tier, a boundary), not the folder tree.\n- **One hero edge**, two at the outside: the connection the change is really about.\n- **Add a flow only when there is a sequence** worth animating. One good flow beats three thin ones.\n- **Attach file refs**: they become the permalinks a reviewer clicks.\n- **There is no findings lens.** PR Lens is the comprehension layer, not another review bot. There is no field for a bug, a risk or a security note, and a document that invents one is rejected rather than trimmed.\n\n## Choosing architecture views\n\nTreat architecture views as a C4-inspired decision tree, not a checklist. One useful view is enough for a small change. Start with system context when the change affects a user, an external system or a system boundary. Use a container view for the affected applications, services, jobs, data stores and runtimes. Add a component child only when an affected container's internals matter. Do not add code-level views by default.\n\nEvery child moves down one level and covers a materially narrower scope. Skip empty, repetitive or speculative levels, and do not infer architecture from folder names alone. Two views should not carry substantially the same nodes and edges. Keep the unchanged direct neighbours that explain blast radius.\n\nKeep data-flow views as separate roots rather than nesting them in the architecture tree. Set `defaultOpen: true` on the highest useful architecture view. Lower levels should normally keep the default, `false`.\n\n## What the validator will catch\n\nRead `references\u002Fgraph-document.md` before writing. The four failures that account for nearly everything:\n\n| Code                         | What you did                                                         |\n| ---------------------------- | -------------------------------------------------------------------- |\n| `BROKEN_REFERENCE`           | an edge, a flow step or a view names an id you never declared        |\n| `INVALID_DOCUMENT`           | an invented field; the schemas are strict, unknown keys are rejected |\n| `DUPLICATE_ID`               | two nodes, edges or views sharing an id                              |\n| `UNSUPPORTED_SCHEMA_VERSION` | `schemaVersion` is not the contract version installed                |\n\nFour rules cannot be expressed in JSON Schema and are checked only by the parser, so structured output alone does not make a document valid: referential integrity, a line range that ends before it starts, a `self` message whose endpoints disagree, and a patch whose two commits are the same. Always validate.\n\n## Fixing a map instead of writing one\n\nWhen someone says the diagram is wrong (a node is misnamed, a folder should not be on it, something sits in the wrong lane), do not edit the generated document. It is regenerated on every run. Write the correction into `.github\u002Fpr-lens.yml`, which is an overlay applied over fresh inference every time:\n\n```yaml\nschemaVersion: 0.1.0\nmap:\n  rename:\n    - match: functions\u002Fsrc\u002Fbroadcast\u002FsendBroadcastBulk.ts\n      to: Broadcast sender\n  exclude:\n    - \"**\u002F*.test.ts\"\n  lane:\n    - match: packages\u002Fbroadcast-lib\u002F**\n      lane: functions\n```\n\n`references\u002Fconfig.md` has the full format and the recipes. Validate it the same way: `npx @coldtea\u002Fpr-lens-cli@0.2.0 validate .github\u002Fpr-lens.yml`.\n\nA `match` beginning with `id:` addresses one node exactly; anything else is a path glob matched against a node's file paths. Prefer the glob, because it keeps holding when the next run names the node differently. A lane pin may name a lane the document never declared: the band is created, and takes the id for its label, so give it one a reader would want to see.\n\n`pr-lens render` says so when a correction matched nothing, which is how a config that has drifted, because the file it named moved or was deleted, becomes visible instead of quietly doing nothing.\n\n## What ships with this skill\n\nEverything you need is beside this page. Nothing here asks you to install a package first.\n\n|                                 |                                                                                    |\n| ------------------------------- | ---------------------------------------------------------------------------------- |\n| `references\u002Fgraph-document.md`  | the document, field by field: enums, limits, and where documents actually go wrong |\n| `references\u002Fconfig.md`          | `.github\u002Fpr-lens.yml`, the correction overlay, in full                             |\n| `references\u002Fexample.graph.json` | one complete document that validates, to read and to copy the shape of             |\n\nThe same document ships as `postmark-refactor.graph.json` in `@coldtea\u002Fpr-lens-schema`, and the JSON Schema the validator enforces is published at `https:\u002F\u002Funpkg.com\u002F@coldtea\u002Fpr-lens-schema\u002Fjson-schema\u002Fgraph-doc.schema.json`. Neither is something you need to fetch to write a document.\n",{"name":5,"description":7},"main","9f5b43aadb1a92441d65e9cb74a584cd6fca62bc","artifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system","https:\u002F\u002Fgithub.com\u002FAO-HyS","https:\u002F\u002Faohys.net\u002F","Software Boutique, we make your projects come true live. ","2026-11-14 03:17:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add AO-HyS\u002Fdevelopment-system --skill pr-lens",{"tool":39,"command":40},"bunx","bunx skills add AO-HyS\u002Fdevelopment-system --skill pr-lens",{"tool":42,"command":43},"pnpm","pnpm dlx skills add AO-HyS\u002Fdevelopment-system --skill pr-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002FSKILL.md",true,[47,51,57,61],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fconfig.md","REFERENCE","参考文档",3339,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002Freferences\u002Fconfig.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fexample.graph.json",14959,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002Freferences\u002Fexample.graph.json",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fgraph-document.md",10105,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.6.0\u002Fskills\u002Finternal\u002Fpr-lens\u002Freferences\u002Fgraph-document.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":20},"01M79EQ4BPYQTX8RWN1Y1J2K1F","working-backwards","Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fworking-backwards\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":20},"01M79EQ2E8P85Y1Y7VNJZMNEJE","flow-implement","Implement a requested software change through verification, corrections, and its authorized delivery endpoint.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fflow-implement\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M79EQ0PNMKHPJ78F8WMNX06P","development-steward","Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fdevelopment-steward\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":20},"01M79EPXJ56MX7955GWP1HD4B0","grill-with-docs","Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M79EPTFPHYEV40ZG52Z0GVS2","global-agent-guardrails","Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fglobal-agent-guardrails\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M79EPR0KPHKAFN7V6CEEDR0Y","impeccable","Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FSKILL.md",[],[]]