[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDACE6SYD9R34HJKT4CH4X":3,"skill-same:01M6MDACE6SYD9R34HJKT4CH4X":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6MDACE6SYD9R34HJKT4CH4X","architecture-audit",null,"Systematic architecture review workflow. Use before major feature work on an unfamiliar or inherited codebase, before scaling milestones, or as a periodic health check. Maps the system as-built (not as-documented), dispatches parallel specialist reviews, and produces an evidence-backed findings report with severity verdicts.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Farchitecture-audit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"architecture","audit","architecture audit","evidence","milestones","reviews","as","systematic","feature","scaling","maps","periodic","review","work","parallel","system","work on","severity","architecture review","workflow","2026-11-10 10:12:30",false,"---\nname: architecture-audit\ndescription: Systematic architecture review workflow. Use before major feature work on an unfamiliar or inherited codebase, before scaling milestones, or as a periodic health check. Maps the system as-built (not as-documented), dispatches parallel specialist reviews, and produces an evidence-backed findings report with severity verdicts.\n---\n\n# Architecture Audit\n\n## The Law\n\n```\nAN ARCHITECTURE CLAIM WITHOUT A FILE REFERENCE IS AN OPINION.\n\"The service layer is tightly coupled\" is not a finding.\n\"OrderService imports 14 concrete classes from 6 modules (src\u002Fservices\u002Forder.ts:1-22),\nso a payment-provider swap requires touching all 6\" is a finding.\n```\n\n## When to Use\n\n- Before major feature work on an inherited or unfamiliar codebase\n- Before a scaling milestone (10× users, new region, new platform)\n- After rapid growth phases where structure was sacrificed for speed\n- As a periodic health check on long-lived systems\n- NOT for greenfield design — use the **architect** agent and **brainstorming** skill instead\n\n## Audit Workflow\n\n### Step 1: Map the System As-Built\n\nDocument what the code actually does, not what the docs or diagrams claim. Read entry points, build files, and dependency manifests before any source.\n\n```markdown\n## System Map — YYYY-MM-DD\n\n**Entry points:** (servers, CLIs, cron jobs, queue consumers — with file paths)\n**Modules\u002Flayers:** (as they exist in the folder structure, not the intended design)\n**External dependencies:** (databases, queues, third-party APIs — where each is called from)\n**Data flow:** (request → response path for the 2-3 most important operations)\n**Trust boundaries:** (where unvalidated input enters, where auth is checked)\n```\n\nIf the as-built map contradicts existing architecture docs, record every divergence — each one is a finding.\n\n### Step 2: Identify Load-Bearing Decisions\n\nList the architectural decisions the system depends on, whether or not anyone made them deliberately:\n\n| Decision | Where visible | Deliberate or accidental? |\n|----------|--------------|--------------------------|\n| Monolith vs services | repo layout, deploy config | |\n| Sync vs async processing | queue usage, HTTP call chains | |\n| Data ownership | which modules write which tables | |\n| Coupling direction | import graph between layers | |\n| State management | session stores, caches, singletons | |\n\n### Step 3: Dispatch Parallel Specialist Reviews\n\nUse the **dispatching-parallel-agents** skill. Each specialist gets the Step 1 system map plus a scoped question:\n\n| Agent | Scoped question |\n|-------|----------------|\n| **architect** | Do module boundaries and coupling direction support the next 12 months of planned work? |\n| **security-reviewer** | Are trust boundaries enforced at every entry point in the system map? |\n| **performance-profiler** | Which architectural choices (N+1 patterns, sync chains, missing caches) cap throughput? |\n| **database-reviewer** | Does data ownership match module boundaries? Any schema shared by unrelated modules? |\n| **infra-reviewer** | Does the deploy topology match the code topology? Any single points of failure? |\n\nSkip a specialist only if their domain is absent (e.g., no database → no database-reviewer).\n\n### Step 4: Consolidate Findings with Evidence\n\nEvery finding must carry a file reference and a consequence:\n\n```markdown\n## Finding N: \u003Cone-line statement>\n\n**Evidence:** `path\u002Fto\u002Ffile.ts:12-40` — \u003Cwhat the code shows>\n**Consequence:** \u003Cwhat breaks, slows, or blocks because of this>\n**Effort to fix:** S \u002F M \u002F L\n**Risk if unfixed:** \u003Cconcrete scenario, not \"tech debt\">\n```\n\nFindings without evidence are deleted, not softened.\n\n### Step 5: Classify Severity\n\n| Severity | Criteria | Action |\n|----------|---------|--------|\n| **CRITICAL** | Data loss, security boundary bypass, or scaling wall within one milestone | Block feature work until addressed |\n| **HIGH** | Change amplification — routine features require touching 3+ modules | Schedule before next major feature |\n| **MEDIUM** | Coupling or duplication that slows work but doesn't block it | Backlog with owner |\n| **LOW** | Style-level structure issues | Note only |\n\n### Step 6: Verdict and Report\n\n```markdown\n## Architecture Audit — YYYY-MM-DD\n\n**Scope:** \u003Cwhat was audited>\n**System map:** (Step 1 output)\n**Findings:** N critical \u002F N high \u002F N medium \u002F N low\n**Verdict:** SOUND | SOUND-WITH-RISKS | INTERVENTION-REQUIRED\n\n**Top 3 actions:** (ordered by risk-to-effort ratio)\n```\n\n| Verdict | Criteria |\n|---------|---------|\n| **SOUND** | No critical or high findings — proceed with planned work |\n| **SOUND-WITH-RISKS** | High findings exist with agreed mitigation dates |\n| **INTERVENTION-REQUIRED** | Any critical finding — architecture work precedes feature work |\n\nFeed CRITICAL and HIGH findings into the **writing-plans** skill as remediation plans. Record accepted risks as ADRs via the **architect** agent so the next audit can check whether the risk materialised.\n\n## Rationalization Red Flags\n\n- \"The architecture is fine, the team just needs to be careful\" — change amplification is structural, not behavioural\n- \"We'll audit after this next feature ships\" — the next feature is built on the unaudited structure\n- \"The diagram in the wiki shows clean layers\" — audit the code, not the diagram\n","# Architecture Audit\n\n## The Law\n\n```\nAN ARCHITECTURE CLAIM WITHOUT A FILE REFERENCE IS AN OPINION.\n\"The service layer is tightly coupled\" is not a finding.\n\"OrderService imports 14 concrete classes from 6 modules (src\u002Fservices\u002Forder.ts:1-22),\nso a payment-provider swap requires touching all 6\" is a finding.\n```\n\n## When to Use\n\n- Before major feature work on an inherited or unfamiliar codebase\n- Before a scaling milestone (10× users, new region, new platform)\n- After rapid growth phases where structure was sacrificed for speed\n- As a periodic health check on long-lived systems\n- NOT for greenfield design — use the **architect** agent and **brainstorming** skill instead\n\n## Audit Workflow\n\n### Step 1: Map the System As-Built\n\nDocument what the code actually does, not what the docs or diagrams claim. Read entry points, build files, and dependency manifests before any source.\n\n```markdown\n## System Map — YYYY-MM-DD\n\n**Entry points:** (servers, CLIs, cron jobs, queue consumers — with file paths)\n**Modules\u002Flayers:** (as they exist in the folder structure, not the intended design)\n**External dependencies:** (databases, queues, third-party APIs — where each is called from)\n**Data flow:** (request → response path for the 2-3 most important operations)\n**Trust boundaries:** (where unvalidated input enters, where auth is checked)\n```\n\nIf the as-built map contradicts existing architecture docs, record every divergence — each one is a finding.\n\n### Step 2: Identify Load-Bearing Decisions\n\nList the architectural decisions the system depends on, whether or not anyone made them deliberately:\n\n| Decision | Where visible | Deliberate or accidental? |\n|----------|--------------|--------------------------|\n| Monolith vs services | repo layout, deploy config | |\n| Sync vs async processing | queue usage, HTTP call chains | |\n| Data ownership | which modules write which tables | |\n| Coupling direction | import graph between layers | |\n| State management | session stores, caches, singletons | |\n\n### Step 3: Dispatch Parallel Specialist Reviews\n\nUse the **dispatching-parallel-agents** skill. Each specialist gets the Step 1 system map plus a scoped question:\n\n| Agent | Scoped question |\n|-------|----------------|\n| **architect** | Do module boundaries and coupling direction support the next 12 months of planned work? |\n| **security-reviewer** | Are trust boundaries enforced at every entry point in the system map? |\n| **performance-profiler** | Which architectural choices (N+1 patterns, sync chains, missing caches) cap throughput? |\n| **database-reviewer** | Does data ownership match module boundaries? Any schema shared by unrelated modules? |\n| **infra-reviewer** | Does the deploy topology match the code topology? Any single points of failure? |\n\nSkip a specialist only if their domain is absent (e.g., no database → no database-reviewer).\n\n### Step 4: Consolidate Findings with Evidence\n\nEvery finding must carry a file reference and a consequence:\n\n```markdown\n## Finding N: \u003Cone-line statement>\n\n**Evidence:** `path\u002Fto\u002Ffile.ts:12-40` — \u003Cwhat the code shows>\n**Consequence:** \u003Cwhat breaks, slows, or blocks because of this>\n**Effort to fix:** S \u002F M \u002F L\n**Risk if unfixed:** \u003Cconcrete scenario, not \"tech debt\">\n```\n\nFindings without evidence are deleted, not softened.\n\n### Step 5: Classify Severity\n\n| Severity | Criteria | Action |\n|----------|---------|--------|\n| **CRITICAL** | Data loss, security boundary bypass, or scaling wall within one milestone | Block feature work until addressed |\n| **HIGH** | Change amplification — routine features require touching 3+ modules | Schedule before next major feature |\n| **MEDIUM** | Coupling or duplication that slows work but doesn't block it | Backlog with owner |\n| **LOW** | Style-level structure issues | Note only |\n\n### Step 6: Verdict and Report\n\n```markdown\n## Architecture Audit — YYYY-MM-DD\n\n**Scope:** \u003Cwhat was audited>\n**System map:** (Step 1 output)\n**Findings:** N critical \u002F N high \u002F N medium \u002F N low\n**Verdict:** SOUND | SOUND-WITH-RISKS | INTERVENTION-REQUIRED\n\n**Top 3 actions:** (ordered by risk-to-effort ratio)\n```\n\n| Verdict | Criteria |\n|---------|---------|\n| **SOUND** | No critical or high findings — proceed with planned work |\n| **SOUND-WITH-RISKS** | High findings exist with agreed mitigation dates |\n| **INTERVENTION-REQUIRED** | Any critical finding — architecture work precedes feature work |\n\nFeed CRITICAL and HIGH findings into the **writing-plans** skill as remediation plans. Record accepted risks as ADRs via the **architect** agent so the next audit can check whether the risk materialised.\n\n## Rationalization Red Flags\n\n- \"The architecture is fine, the team just needs to be careful\" — change amplification is structural, not behavioural\n- \"We'll audit after this next feature ships\" — the next feature is built on the unaudited structure\n- \"The diagram in the wiki shows clean layers\" — audit the code, not the diagram\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Farchitecture-audit",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill architecture-audit",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill architecture-audit",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill architecture-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Farchitecture-audit\u002FSKILL.md",true,[],[69,79,87,95,103,111],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":78},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\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":73,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":78},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":78},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":78},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":78},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]