[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6VRF798DN7SS9FTZXT5TS":3,"skill-same:01M7F6VRF798DN7SS9FTZXT5TS":93},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7F6VRF798DN7SS9FTZXT5TS","onion-architecture",null,"Onion (ports-and-adapters) architecture for a TypeScript backend (Fastify, Drizzle\u002FPostgres, Zod, a hand-written DI container, adapters). Decides which layer a piece of backend code belongs to, which way a dependency may point, where a port interface lives, how a service gets its dependencies, where transactions start, where Zod parses, and how dependency-cruiser can enforce all of it. Use when adding or moving a route, service, repository, adapter, port or domain rule in a backend; when a service needs the database, an external API or an LLM; when reviewing a backend diff for layering; or when an architecture check fails. Does not cover Fastify, Drizzle or Zod API usage — use fastify-best-practices, drizzle-orm-patterns and zod for that.","yrazub\u002Fgen-bin","yrazub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3244321?v=4","01M7F6TT4HKB003QGEXJTY5G5V","Iurii Razubaiev","01M7F6TT55ZA0E2G698HA8T0E9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: onion-architecture\ndescription: \"Onion (ports-and-adapters) architecture for a TypeScript backend (Fastify, Drizzle\u002FPostgres, Zod, a hand-written DI container, adapters). Decides which layer a piece of backend code belongs to, which way a dependency may point, where a port interface lives, how a service gets its dependencies, where transactions start, where Zod parses, and how dependency-cruiser can enforce all of it. Use when adding or moving a route, service, repository, adapter, port or domain rule in a backend; when a service needs the database, an external API or an LLM; when reviewing a backend diff for layering; or when an architecture check fails. Does not cover Fastify, Drizzle or Zod API usage — use fastify-best-practices, drizzle-orm-patterns and zod for that.\"\nmetadata:\n  version: \"1.0.0\"\n  updated: \"2026-09-27\"\n---\n\n# Onion architecture — TypeScript backend\n\nThe domain sits in the middle; everything that talks to the outside world sits on the edge; and\n**source-code dependencies point inward only**. An inner layer never names anything from an outer\none (Palermo's first tenet, Martin's Dependency Rule). The database, Fastify, GitHub and the LLM\nare details at the edge.\n\n**The project's documents win.** The project's own `CLAUDE.md` files, architecture documents and\nspecs override this skill where they speak. The paths below (`modules\u002F\u003Cm>\u002F…`, `src\u002Fadapters\u002F…`,\n`platform\u002F…`) are the layout this skill assumes; map them to the project's equivalents.\n\n## The layers\n\n| Layer (inner → outer) | Typical location | May import |\n|---|---|---|\n| **Domain** | the shared Zod contracts package · `modules\u002F\u003Cm>\u002Fdomain.ts` · a pure engine package, if the project has one | other domain code, `zod` |\n| **Ports** | external-world ports in the shared contracts package (`LLMProvider`, `GitHubClient`, …) · persistence ports in `modules\u002F\u003Cm>\u002Fports.ts` | domain |\n| **Application** (use cases) | `modules\u002F\u003Cm>\u002Fservice.ts` and other orchestrators | domain, ports, `platform\u002Ferrors.ts`, `platform\u002Flogger.ts` |\n| **Edge \u002F infrastructure** | `modules\u002F\u003Cm>\u002Froutes.ts` (Fastify) · `modules\u002F\u003Cm>\u002Frepository.ts`, `repository\u002F` (Drizzle) · `src\u002Fadapters\u002F*` · `src\u002Fdb\u002F` · `platform\u002Fconfig.ts` | anything inward |\n| **Composition root** | `platform\u002Fcontainer.ts`, `src\u002Fapp.ts`, `src\u002Fserver.ts`; a module's `routes.ts` for its own wiring | everything |\n\n## Where does this code go?\n\nStop at the first *yes*.\n\n| # | Question | Put it… |\n|---|---|---|\n| 1 | Does it construct an adapter, a repository or a service? | in the composition root: `container.ts` if several modules share it, else the module's `routes.ts` |\n| 2 | Does it know about HTTP — `req`, `reply`, status codes, schemas on a route? | `routes.ts` |\n| 3 | Does it build a query, touch `db`, a table or a Drizzle row type? | `repository.ts` \u002F `repository\u002F\u003Caggregate>.repo.ts` |\n| 4 | Does it call an SDK (octokit, openai, simple-git, ast-grep, fs, child_process)? | an adapter in `src\u002Fadapters\u002F\u003Cx>\u002F` behind a port |\n| 5 | Is it the *shape* of something another package also sees? | a Zod contract in the shared contracts package |\n| 6 | Is it a rule that decides something from data alone (no I\u002FO)? | `modules\u002F\u003Cm>\u002Fdomain.ts`; if two modules need it, the shared contracts package |\n| 7 | Does it sequence I\u002FO steps — load, decide, persist, emit? | `service.ts` (or a named orchestrator next to it) |\n\nDefaults:\n- New services get **narrow dependencies** rather than `Container`. Existing services are left as they are until a task touches them.\n- A service gets a **`ports.ts` interface** for its store only when it holds logic worth unit-testing without Postgres. A thin pass-through may use the concrete repository.\n- Machine enforcement is **dependency-cruiser with a baseline**, if the project has one (see Enforcement).\n\n## Rules\n\nImpact: **CRITICAL** breaks the architecture · **HIGH** erodes it · **MEDIUM** hurts clarity.\nIDs in `code` are also suggested rule names for the project's dependency-cruiser config where they\nare machine-checkable (✓).\n\n### Dependency direction — [layers-and-dependency-rule.md](references\u002Flayers-and-dependency-rule.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `dep-inward-only` | An inner layer never imports from an outer one | CRITICAL | partly |\n| `dep-domain-framework-free` | Domain and ports import no Fastify, Drizzle, SDK, `src\u002Fdb`, `platform` or `adapters` | CRITICAL | ✓ |\n| `dep-no-cross-module` | `modules\u002Fa` never imports `modules\u002Fb`; shared rules move inward | HIGH | ✓ |\n| `no-circular` | No import cycles | HIGH | ✓ |\n| `dep-proportionate` | Add a layer or an interface only when logic or a test needs it | MEDIUM | — |\n\n### Fastify at the edge — [fastify-edge.md](references\u002Ffastify-edge.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `edge-thin-routes` | A handler takes parsed input, calls one use case, returns a contract | CRITICAL | via `db-only-in-repository` |\n| `edge-fastify-in-routes-only` | Only `routes.ts` and `modules\u002F_shared\u002F` import Fastify | HIGH | ✓ |\n| `edge-errors-mapped-at-edge` | Services throw `AppError` subclasses; the shared handler renders them | HIGH | — |\n| `edge-schema-first` | Zod `params`\u002F`body`\u002F`response` on the route, never `Schema.parse(req.body)` | HIGH | — |\n| `edge-hooks-no-logic` | Hooks do cross-cutting work only (auth, context, logging) | MEDIUM | — |\n\n### Drizzle as infrastructure — [drizzle-persistence.md](references\u002Fdrizzle-persistence.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `db-only-in-repository` | `src\u002Fdb\u002F` and Drizzle are imported only by repositories and the composition root | CRITICAL | ✓ |\n| `db-return-domain-types` | A repository returns contracts\u002Fdomain types, never `$inferSelect` rows | HIGH | — |\n| `db-tx-owned-by-use-case` | The service decides the transaction boundary; repositories accept an executor | HIGH | — |\n| `db-no-query-leak` | A repository returns finished results, never a query builder | MEDIUM | — |\n\n### Zod and contracts — [zod-contracts-boundaries.md](references\u002Fzod-contracts-boundaries.md)\n\n| ID | Rule | Impact |\n|---|---|---|\n| `zod-parse-at-boundary` | Parse every input where it enters: HTTP, LLM output, GitHub, config, secrets, JSON columns | CRITICAL |\n| `zod-contract-once` | A shape crossing a package boundary is defined only in the shared contracts package | HIGH |\n| `zod-trust-inside` | Past the boundary, code trusts its types; no defensive re-parsing | MEDIUM |\n| `zod-domain-vs-wire` | A separate domain type only when it really differs from the contract | MEDIUM |\n\n### DI and the composition root — [composition-root-di.md](references\u002Fcomposition-root-di.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `di-composition-root-only` | `new SomeAdapter()` \u002F `new SomeRepository()` only in a composition root or a test | CRITICAL | — |\n| `di-narrow-deps` | A new service receives the ports it uses, not `Container` | HIGH | ✓ |\n| `di-lazy-secrets` | Secret-backed clients stay lazy and async; the server boots with no keys | HIGH | — |\n| `platform-no-modules` | `platform\u002F` never imports a module, except the container | HIGH | ✓ |\n\n### Adapters — [adapters.md](references\u002Fadapters.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `adapter-implements-port` | Every adapter implements a port; its mock in `mocks.ts` implements the same one | CRITICAL | — |\n| `adapter-no-app-layers` | An adapter never imports a module | HIGH | ✓ |\n| `adapter-no-business-rules` | An adapter translates (SDK ↔ port, SDK error ↔ `AppError`) and decides nothing | HIGH | — |\n\n### A pure engine package — [pure-engine.md](references\u002Fpure-engine.md)\n\nApplies when the project keeps its domain logic in a separate package (an engine, a core library).\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `core-stays-pure` | No server code and no SDK in the engine, except its LLM transport folder; the only side effect is the injected `LLMProvider` | CRITICAL | ✓ |\n| `core-no-node-io` | No `fs`, `child_process`, `net`, `http`; no `process.env` | CRITICAL | ✓ (not `process.env`) |\n| `core-public-api-only` | The server imports the engine through its public entry point (`src\u002Findex.ts`) only | HIGH | ✓ |\n\n### Tests by layer — [testing-by-layer.md](references\u002Ftesting-by-layer.md)\n\nDomain: plain unit tests, no doubles. Service: fake ports. Repository: integration test on a real\nPostgres. Route: `app.inject` with container overrides. Follow the project's own test layout and naming.\n\n### Enforcement — [enforcement-dependency-cruiser.md](references\u002Fenforcement-dependency-cruiser.md)\n\nIf the project has an architecture check (dependency-cruiser or similar), run it and make sure CI\nruns it. If it keeps a baseline of known violations, only **new** ones may fail. Never re-baseline\nto silence a new violation.\n\n## How to apply\n\n- **Writing code:** walk the table in \"Where does this code go?\" before creating a file. Then run the project's architecture check, if it has one.\n- **Reviewing:** check the CRITICAL and HIGH rules first, and cite the ID and file. For example: \"`db-only-in-repository`: `pulls\u002Froutes.ts` queries `t.repos` directly.\"\n- **Touching legacy code:** code already in the baseline may stay as it is. Do not *add* a new leak next to it. Do not refactor unrelated leaks in a feature PR. If a task fixes one, run the project's baseline-update command in the same PR so the baseline shrinks.\n- **Unsure between two layers:** pick the outer one. Moving code inward later is cheap. Undoing a domain that imports Drizzle is not.\n\nSources for every rule: [references\u002Fsources.md](references\u002Fsources.md).\n","# Onion architecture — TypeScript backend\n\nThe domain sits in the middle; everything that talks to the outside world sits on the edge; and\n**source-code dependencies point inward only**. An inner layer never names anything from an outer\none (Palermo's first tenet, Martin's Dependency Rule). The database, Fastify, GitHub and the LLM\nare details at the edge.\n\n**The project's documents win.** The project's own `CLAUDE.md` files, architecture documents and\nspecs override this skill where they speak. The paths below (`modules\u002F\u003Cm>\u002F…`, `src\u002Fadapters\u002F…`,\n`platform\u002F…`) are the layout this skill assumes; map them to the project's equivalents.\n\n## The layers\n\n| Layer (inner → outer) | Typical location | May import |\n|---|---|---|\n| **Domain** | the shared Zod contracts package · `modules\u002F\u003Cm>\u002Fdomain.ts` · a pure engine package, if the project has one | other domain code, `zod` |\n| **Ports** | external-world ports in the shared contracts package (`LLMProvider`, `GitHubClient`, …) · persistence ports in `modules\u002F\u003Cm>\u002Fports.ts` | domain |\n| **Application** (use cases) | `modules\u002F\u003Cm>\u002Fservice.ts` and other orchestrators | domain, ports, `platform\u002Ferrors.ts`, `platform\u002Flogger.ts` |\n| **Edge \u002F infrastructure** | `modules\u002F\u003Cm>\u002Froutes.ts` (Fastify) · `modules\u002F\u003Cm>\u002Frepository.ts`, `repository\u002F` (Drizzle) · `src\u002Fadapters\u002F*` · `src\u002Fdb\u002F` · `platform\u002Fconfig.ts` | anything inward |\n| **Composition root** | `platform\u002Fcontainer.ts`, `src\u002Fapp.ts`, `src\u002Fserver.ts`; a module's `routes.ts` for its own wiring | everything |\n\n## Where does this code go?\n\nStop at the first *yes*.\n\n| # | Question | Put it… |\n|---|---|---|\n| 1 | Does it construct an adapter, a repository or a service? | in the composition root: `container.ts` if several modules share it, else the module's `routes.ts` |\n| 2 | Does it know about HTTP — `req`, `reply`, status codes, schemas on a route? | `routes.ts` |\n| 3 | Does it build a query, touch `db`, a table or a Drizzle row type? | `repository.ts` \u002F `repository\u002F\u003Caggregate>.repo.ts` |\n| 4 | Does it call an SDK (octokit, openai, simple-git, ast-grep, fs, child_process)? | an adapter in `src\u002Fadapters\u002F\u003Cx>\u002F` behind a port |\n| 5 | Is it the *shape* of something another package also sees? | a Zod contract in the shared contracts package |\n| 6 | Is it a rule that decides something from data alone (no I\u002FO)? | `modules\u002F\u003Cm>\u002Fdomain.ts`; if two modules need it, the shared contracts package |\n| 7 | Does it sequence I\u002FO steps — load, decide, persist, emit? | `service.ts` (or a named orchestrator next to it) |\n\nDefaults:\n- New services get **narrow dependencies** rather than `Container`. Existing services are left as they are until a task touches them.\n- A service gets a **`ports.ts` interface** for its store only when it holds logic worth unit-testing without Postgres. A thin pass-through may use the concrete repository.\n- Machine enforcement is **dependency-cruiser with a baseline**, if the project has one (see Enforcement).\n\n## Rules\n\nImpact: **CRITICAL** breaks the architecture · **HIGH** erodes it · **MEDIUM** hurts clarity.\nIDs in `code` are also suggested rule names for the project's dependency-cruiser config where they\nare machine-checkable (✓).\n\n### Dependency direction — [layers-and-dependency-rule.md](references\u002Flayers-and-dependency-rule.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `dep-inward-only` | An inner layer never imports from an outer one | CRITICAL | partly |\n| `dep-domain-framework-free` | Domain and ports import no Fastify, Drizzle, SDK, `src\u002Fdb`, `platform` or `adapters` | CRITICAL | ✓ |\n| `dep-no-cross-module` | `modules\u002Fa` never imports `modules\u002Fb`; shared rules move inward | HIGH | ✓ |\n| `no-circular` | No import cycles | HIGH | ✓ |\n| `dep-proportionate` | Add a layer or an interface only when logic or a test needs it | MEDIUM | — |\n\n### Fastify at the edge — [fastify-edge.md](references\u002Ffastify-edge.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `edge-thin-routes` | A handler takes parsed input, calls one use case, returns a contract | CRITICAL | via `db-only-in-repository` |\n| `edge-fastify-in-routes-only` | Only `routes.ts` and `modules\u002F_shared\u002F` import Fastify | HIGH | ✓ |\n| `edge-errors-mapped-at-edge` | Services throw `AppError` subclasses; the shared handler renders them | HIGH | — |\n| `edge-schema-first` | Zod `params`\u002F`body`\u002F`response` on the route, never `Schema.parse(req.body)` | HIGH | — |\n| `edge-hooks-no-logic` | Hooks do cross-cutting work only (auth, context, logging) | MEDIUM | — |\n\n### Drizzle as infrastructure — [drizzle-persistence.md](references\u002Fdrizzle-persistence.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `db-only-in-repository` | `src\u002Fdb\u002F` and Drizzle are imported only by repositories and the composition root | CRITICAL | ✓ |\n| `db-return-domain-types` | A repository returns contracts\u002Fdomain types, never `$inferSelect` rows | HIGH | — |\n| `db-tx-owned-by-use-case` | The service decides the transaction boundary; repositories accept an executor | HIGH | — |\n| `db-no-query-leak` | A repository returns finished results, never a query builder | MEDIUM | — |\n\n### Zod and contracts — [zod-contracts-boundaries.md](references\u002Fzod-contracts-boundaries.md)\n\n| ID | Rule | Impact |\n|---|---|---|\n| `zod-parse-at-boundary` | Parse every input where it enters: HTTP, LLM output, GitHub, config, secrets, JSON columns | CRITICAL |\n| `zod-contract-once` | A shape crossing a package boundary is defined only in the shared contracts package | HIGH |\n| `zod-trust-inside` | Past the boundary, code trusts its types; no defensive re-parsing | MEDIUM |\n| `zod-domain-vs-wire` | A separate domain type only when it really differs from the contract | MEDIUM |\n\n### DI and the composition root — [composition-root-di.md](references\u002Fcomposition-root-di.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `di-composition-root-only` | `new SomeAdapter()` \u002F `new SomeRepository()` only in a composition root or a test | CRITICAL | — |\n| `di-narrow-deps` | A new service receives the ports it uses, not `Container` | HIGH | ✓ |\n| `di-lazy-secrets` | Secret-backed clients stay lazy and async; the server boots with no keys | HIGH | — |\n| `platform-no-modules` | `platform\u002F` never imports a module, except the container | HIGH | ✓ |\n\n### Adapters — [adapters.md](references\u002Fadapters.md)\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `adapter-implements-port` | Every adapter implements a port; its mock in `mocks.ts` implements the same one | CRITICAL | — |\n| `adapter-no-app-layers` | An adapter never imports a module | HIGH | ✓ |\n| `adapter-no-business-rules` | An adapter translates (SDK ↔ port, SDK error ↔ `AppError`) and decides nothing | HIGH | — |\n\n### A pure engine package — [pure-engine.md](references\u002Fpure-engine.md)\n\nApplies when the project keeps its domain logic in a separate package (an engine, a core library).\n\n| ID | Rule | Impact | ✓ |\n|---|---|---|---|\n| `core-stays-pure` | No server code and no SDK in the engine, except its LLM transport folder; the only side effect is the injected `LLMProvider` | CRITICAL | ✓ |\n| `core-no-node-io` | No `fs`, `child_process`, `net`, `http`; no `process.env` | CRITICAL | ✓ (not `process.env`) |\n| `core-public-api-only` | The server imports the engine through its public entry point (`src\u002Findex.ts`) only | HIGH | ✓ |\n\n### Tests by layer — [testing-by-layer.md](references\u002Ftesting-by-layer.md)\n\nDomain: plain unit tests, no doubles. Service: fake ports. Repository: integration test on a real\nPostgres. Route: `app.inject` with container overrides. Follow the project's own test layout and naming.\n\n### Enforcement — [enforcement-dependency-cruiser.md](references\u002Fenforcement-dependency-cruiser.md)\n\nIf the project has an architecture check (dependency-cruiser or similar), run it and make sure CI\nruns it. If it keeps a baseline of known violations, only **new** ones may fail. Never re-baseline\nto silence a new violation.\n\n## How to apply\n\n- **Writing code:** walk the table in \"Where does this code go?\" before creating a file. Then run the project's architecture check, if it has one.\n- **Reviewing:** check the CRITICAL and HIGH rules first, and cite the ID and file. For example: \"`db-only-in-repository`: `pulls\u002Froutes.ts` queries `t.repos` directly.\"\n- **Touching legacy code:** code already in the baseline may stay as it is. Do not *add* a new leak next to it. Do not refactor unrelated leaks in a feature PR. If a task fixes one, run the project's baseline-update command in the same PR so the baseline shrinks.\n- **Unsure between two layers:** pick the outer one. Moving code inward later is cheap. Undoing a domain that imports Drizzle is not.\n\nSources for every rule: [references\u002Fsources.md](references\u002Fsources.md).\n",{"name":5,"metadata":24,"description":7},{"updated":25,"version":26},"2026-09-27","1.0.0","main","fe6b8af9977e97284d18d1179d55c021dd0a4a0a","plugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin","https:\u002F\u002Fgithub.com\u002Fyrazub","2026-11-05 19:09:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add yrazub\u002Fgen-bin --skill onion-architecture",{"tool":39,"command":40},"bunx","bunx skills add yrazub\u002Fgen-bin --skill onion-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yrazub\u002Fgen-bin --skill onion-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002FSKILL.md",true,[47,53,57,61,65,69,73,77,81,85,89],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",3140,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fadapters.md",2652,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fadapters.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcomposition-root-di.md",3743,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fcomposition-root-di.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdrizzle-persistence.md",4217,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fdrizzle-persistence.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fenforcement-dependency-cruiser.md",3263,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fenforcement-dependency-cruiser.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ffastify-edge.md",3674,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Ffastify-edge.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Flayers-and-dependency-rule.md",4452,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Flayers-and-dependency-rule.md",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fpure-engine.md",2231,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fpure-engine.md",{"path":82,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fsources.md",4639,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fsources.md",{"path":86,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Ftesting-by-layer.md",1706,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Ftesting-by-layer.md",{"path":90,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fzod-contracts-boundaries.md",2175,"https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fonion-architecture\u002Freferences\u002Fzod-contracts-boundaries.md",[94,100,107,114,120,126],{"skillNo":95,"name":96,"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":97,"categories":98,"keywords":99,"publishedAt":19},"01M7F6Y3T2E5DXEPZ71KC9GX2N","s","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Fmissing-description\u002Fplugins\u002Fa\u002Fskills\u002Fs\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7F6Y2JH0M9YW9194HT28S92","talk","Says a lot.","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Flong-description\u002Fplugins\u002Fwordy\u002Fskills\u002Ftalk\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"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},"01M7F6Y02Z4197HV8ANJYP8WK3","review","Review code in the beta plugin.","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Fduplicates\u002Fplugins\u002Fbeta\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":115,"name":109,"nameZh":6,"description":116,"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},"01M7F6XZ3Z4M2YTEKZJYN5MBYJ","Review code in the alpha plugin.","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Fduplicates\u002Fplugins\u002Falpha\u002Fskills\u002Freview\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},"01M7F6XY9V4HSXSVD348E52GEK","bad","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Fbroken-yaml\u002Fplugins\u002Fbroken\u002Fskills\u002Fbad\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7F6XW4C3V6VHDK6ZHKNXSC3","execute-plan","Executes an approved implementation plan phase by phase with the project agents.","https:\u002F\u002Fgithub.com\u002Fyrazub\u002Fgen-bin\u002Fblob\u002Fmain\u002Fsite\u002Ftest\u002Ffixtures\u002Fbasic\u002Fplugins\u002Fsdd-workflow\u002Fskills\u002Fexecute-plan\u002FSKILL.md",[],[]]