[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74EQNZ9MBJW82HDD2A7ZX0T":3,"skill-same:01M74EQNZ9MBJW82HDD2A7ZX0T":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M74EQNZ9MBJW82HDD2A7ZX0T","gear-creator",null,"Interactive workflow for creating new ToolKit gears and editing existing ones. Use when adding a new gear to the platform, adding features to an existing gear (REST endpoints, DB entities, OData filtering, plugins, lifecycle\u002Fbackground tasks, SSE events, error types), refactoring gear layer structure, or creating SDK crates. Covers the full DDD-light stack — SDK pattern, contract\u002FAPI\u002Fdomain\u002Finfra layers, OperationBuilder, SecureORM, ClientHub, error handling, and testing.","constructorfabric\u002Fgears-rust","constructorfabric","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286363322?v=4","01M74EHWDT73DH7WYE949KK2Y7","Constructor Fabric","01M74EPJ34TDGPGD0784ZYEADV",48,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgear-creator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gear-creator\ndescription: Interactive workflow for creating new ToolKit gears and editing existing ones. Use when adding a new gear to the platform, adding features to an existing gear (REST endpoints, DB entities, OData filtering, plugins, lifecycle\u002Fbackground tasks, SSE events, error types), refactoring gear layer structure, or creating SDK crates. Covers the full DDD-light stack — SDK pattern, contract\u002FAPI\u002Fdomain\u002Finfra layers, OperationBuilder, SecureORM, ClientHub, error handling, and testing.\nuser-invocable: true\n---\n\n# ToolKit Gear Creator\n\nInteractive workflow for creating and editing ToolKit gears.\n\n## Canonical example\n\n**`examples\u002Ftoolkit\u002Fusers-info\u002F`** is the reference implementation. When unsure about patterns, read the corresponding file in users-info first.\n\n- SDK crate: `examples\u002Ftoolkit\u002Fusers-info\u002Fusers-info-sdk\u002Fsrc\u002F`\n- Gear crate: `examples\u002Ftoolkit\u002Fusers-info\u002Fusers-info\u002Fsrc\u002F`\n\n## Document routing\n\nRead the minimum set of docs needed for the task. Start with the routing table below; do NOT load all docs at once.\n\n| When you need to... | Read this |\n|---|---|\n| Understand ToolKit concepts, golden path | `docs\u002Ftoolkit_unified_system\u002F01_overview.md` |\n| Create gear structure, SDK crate, naming, layers | `docs\u002Ftoolkit_unified_system\u002F02_gear_layout_and_sdk_pattern.md` |\n| Wire ClientHub, inter-gear clients, plugins | `docs\u002Ftoolkit_unified_system\u002F03_clienthub_and_plugins.md` |\n| Add REST endpoints, OperationBuilder, SSE, auth | `docs\u002Ftoolkit_unified_system\u002F04_rest_operation_builder.md` |\n| Implement errors, RFC-9457 Problem, From impls | `docs\u002Ftoolkit_unified_system\u002F05_errors_rfc9457.md` |\n| Add DB entities, SecureORM, AuthZ PEP | `docs\u002Ftoolkit_unified_system\u002F06_authn_authz_secure_orm.md` |\n| Add repositories, migrations, transactions | `docs\u002Ftoolkit_unified_system\u002F11_database_patterns.md` |\n| Add OData filtering, pagination, $select, $orderby | `docs\u002Ftoolkit_unified_system\u002F07_odata_pagination_select_filter.md` |\n| Configure lifecycle, background tasks, cancellation | `docs\u002Ftoolkit_unified_system\u002F08_lifecycle_stateful_tasks.md` |\n| Create out-of-process gear, gRPC, OoP SDK | `docs\u002Ftoolkit_unified_system\u002F09_oop_grpc_sdk_pattern.md` |\n| Get checklists, code templates, test patterns | `docs\u002Ftoolkit_unified_system\u002F10_checklists_and_templates.md` |\n| Write unit tests, test file layout, mocks, fixtures | `docs\u002Ftoolkit_unified_system\u002F12_unit_testing.md` |\n| Write E2E tests, cross-gear integration tests | `docs\u002Ftoolkit_unified_system\u002F13_e2e_testing.md` |\n\n## Workflow: Create a new gear\n\n### Phase 1 — Requirements gathering\n\nAsk the user (one message, not a wall of questions) or infer from the task or design documents:\n\n1. **Gear name** (kebab-case, e.g. `file-storage`)\n2. **Purpose** — what does this gear do?\n3. **Capabilities needed** — which apply: `db`, `rest`, `stateful`?\n4. **Dependencies** — does it depend on other gears? (e.g. `authz-resolver`)\n5. **SDK needed?** — will other gears consume its API?\n\nUse the answers to determine which docs to load next.\n\n### Phase 2 — Design\n\n1. Read `docs\u002Ftoolkit_unified_system\u002F02_gear_layout_and_sdk_pattern.md`\n2. Read `docs\u002Ftoolkit_unified_system\u002F10_checklists_and_templates.md` — use the \"Adding a New Gear\" checklist\n3. If capabilities include `rest` — also read `docs\u002Ftoolkit_unified_system\u002F04_rest_operation_builder.md`\n4. If capabilities include `db` — also read `docs\u002Ftoolkit_unified_system\u002F06_authn_authz_secure_orm.md` and `docs\u002Ftoolkit_unified_system\u002F11_database_patterns.md`\n5. Study corresponding files in `examples\u002Ftoolkit\u002Fusers-info\u002F` for the layers being created\n\nPresent to the user:\n- Proposed directory structure\n- SDK trait definition (if SDK needed)\n- Domain model outline\n- REST endpoints list (if rest capability)\n- DB entities list (if db capability)\n\nGet approval before writing code.\n\n### Phase 3 — Scaffold\n\nCreate files in this order (each layer builds on the previous):\n\n1. **SDK crate** (if needed): `\u003Cgear>-sdk\u002F` with `Cargo.toml`, `src\u002Flib.rs`, `src\u002Fclient.rs`, `src\u002Fmodels.rs`, `src\u002Ferrors.rs`\n2. **Gear crate**: `\u003Cgear>\u002FCargo.toml`, `src\u002Flib.rs`, `src\u002Fgear.rs`, `src\u002Fconfig.rs`\n3. **Contract layer**: `src\u002Fcontract\u002F` — re-export from SDK or define inline\n4. **Domain layer**: `src\u002Fdomain\u002Ferror.rs`, `src\u002Fdomain\u002Fservice\u002F`, `src\u002Fdomain\u002Frepos\u002F`\n5. **Infra layer** (if db): `src\u002Finfra\u002Fstorage\u002Fentity\u002F`, `src\u002Finfra\u002Fstorage\u002Fmapper.rs`, `src\u002Finfra\u002Fstorage\u002Fmigrations\u002F`\n6. **API layer** (if rest): `src\u002Fapi\u002Frest\u002Fdto.rs`, `src\u002Fapi\u002Frest\u002Fhandlers\u002F`, `src\u002Fapi\u002Frest\u002Froutes\u002F`, `src\u002Fapi\u002Frest\u002Ferror.rs`\n7. **Local client**: `src\u002Fdomain\u002Flocal_client\u002F`\n\n### Phase 4 — Wire and register\n\n1. Add gear crate(s) to workspace `Cargo.toml`\n2. Register gear in `apps\u002Fcf-gears-example-server\u002Fsrc\u002Fmain.rs`\n3. Register client in `init()` via ClientHub\n4. Add feature flag if needed (see existing `static-authn` \u002F `static-authz` pattern)\n\n### Phase 5 — Verify\n\n1. `cargo build -p \u003Cgear-crate>` — must compile\n2. `cargo clippy -p \u003Cgear-crate>` — no warnings\n3. `cargo gears lint --dylint` — architecture lints pass\n4. `cargo test -p \u003Cgear-crate>` — tests pass\n\n## Workflow: Edit an existing gear\n\n### Step 1 — Understand scope\n\nAsk the user what they want to change. Common tasks:\n\n- Add a new REST endpoint\n- Add a new DB entity\n- Add OData filtering to an existing endpoint\n- Add a new domain service method\n- Add error variants\n- Add lifecycle\u002Fbackground task\n- Add plugin support\n\n### Step 2 — Load relevant docs\n\nUse the document routing table above. Load only what's needed for the specific change.\n\n### Step 3 — Study existing code\n\nRead the gear's current implementation. Compare with `examples\u002Ftoolkit\u002Fusers-info\u002F` for the same layer.\n\n### Step 4 — Implement\n\nFollow the DDD-light layer rules:\n\n- **Contract**: NO serde, NO utoipa, NO HTTP types\n- **API\u002FREST DTOs**: MUST have `Serialize`, `Deserialize`, `ToSchema`; MUST be in `api\u002Frest\u002F`\n- **Domain**: All non-module-private structs\u002Fenums (`pub`\u002F`pub(crate)`\u002F`pub(super)`) MUST have `#[domain_model]` (strictly module-private helpers are exempt)\n- **Entities**: Use `#[derive(Scopable)]` with `#[secure(tenant_col = \"...\")]`\n- **Endpoints**: MUST follow `\u002F{service-name}\u002Fv{N}\u002F{resource}` pattern\n- **Errors**: Use `Problem` (RFC-9457), implement `From\u003CDomainError> for Problem`\n\n### Step 5 — Verify\n\nSame as Phase 5 of the create workflow.\n\n## Key invariants\n\nThese rules apply to ALL gear work. Violating them will fail CI:\n\n- SDK pattern is the public API — use `\u003Cgear>-sdk` crate\n- `SecureConn` + `AccessScope` for all DB access — no raw connections\n- `OperationBuilder` for all REST routes — with `.authenticated()` and `.standard_errors()`\n- `#[domain_model]` on all non-module-private domain structs\u002Fenums (DE0309 lint; strictly private helpers exempt)\n- No `unwrap()` \u002F `expect()` — use proper Result types\n- AuthZ via `PolicyEnforcer` PEP pattern — never construct `AccessScope` manually\n","# ToolKit Gear Creator\n\nInteractive workflow for creating and editing ToolKit gears.\n\n## Canonical example\n\n**`examples\u002Ftoolkit\u002Fusers-info\u002F`** is the reference implementation. When unsure about patterns, read the corresponding file in users-info first.\n\n- SDK crate: `examples\u002Ftoolkit\u002Fusers-info\u002Fusers-info-sdk\u002Fsrc\u002F`\n- Gear crate: `examples\u002Ftoolkit\u002Fusers-info\u002Fusers-info\u002Fsrc\u002F`\n\n## Document routing\n\nRead the minimum set of docs needed for the task. Start with the routing table below; do NOT load all docs at once.\n\n| When you need to... | Read this |\n|---|---|\n| Understand ToolKit concepts, golden path | `docs\u002Ftoolkit_unified_system\u002F01_overview.md` |\n| Create gear structure, SDK crate, naming, layers | `docs\u002Ftoolkit_unified_system\u002F02_gear_layout_and_sdk_pattern.md` |\n| Wire ClientHub, inter-gear clients, plugins | `docs\u002Ftoolkit_unified_system\u002F03_clienthub_and_plugins.md` |\n| Add REST endpoints, OperationBuilder, SSE, auth | `docs\u002Ftoolkit_unified_system\u002F04_rest_operation_builder.md` |\n| Implement errors, RFC-9457 Problem, From impls | `docs\u002Ftoolkit_unified_system\u002F05_errors_rfc9457.md` |\n| Add DB entities, SecureORM, AuthZ PEP | `docs\u002Ftoolkit_unified_system\u002F06_authn_authz_secure_orm.md` |\n| Add repositories, migrations, transactions | `docs\u002Ftoolkit_unified_system\u002F11_database_patterns.md` |\n| Add OData filtering, pagination, $select, $orderby | `docs\u002Ftoolkit_unified_system\u002F07_odata_pagination_select_filter.md` |\n| Configure lifecycle, background tasks, cancellation | `docs\u002Ftoolkit_unified_system\u002F08_lifecycle_stateful_tasks.md` |\n| Create out-of-process gear, gRPC, OoP SDK | `docs\u002Ftoolkit_unified_system\u002F09_oop_grpc_sdk_pattern.md` |\n| Get checklists, code templates, test patterns | `docs\u002Ftoolkit_unified_system\u002F10_checklists_and_templates.md` |\n| Write unit tests, test file layout, mocks, fixtures | `docs\u002Ftoolkit_unified_system\u002F12_unit_testing.md` |\n| Write E2E tests, cross-gear integration tests | `docs\u002Ftoolkit_unified_system\u002F13_e2e_testing.md` |\n\n## Workflow: Create a new gear\n\n### Phase 1 — Requirements gathering\n\nAsk the user (one message, not a wall of questions) or infer from the task or design documents:\n\n1. **Gear name** (kebab-case, e.g. `file-storage`)\n2. **Purpose** — what does this gear do?\n3. **Capabilities needed** — which apply: `db`, `rest`, `stateful`?\n4. **Dependencies** — does it depend on other gears? (e.g. `authz-resolver`)\n5. **SDK needed?** — will other gears consume its API?\n\nUse the answers to determine which docs to load next.\n\n### Phase 2 — Design\n\n1. Read `docs\u002Ftoolkit_unified_system\u002F02_gear_layout_and_sdk_pattern.md`\n2. Read `docs\u002Ftoolkit_unified_system\u002F10_checklists_and_templates.md` — use the \"Adding a New Gear\" checklist\n3. If capabilities include `rest` — also read `docs\u002Ftoolkit_unified_system\u002F04_rest_operation_builder.md`\n4. If capabilities include `db` — also read `docs\u002Ftoolkit_unified_system\u002F06_authn_authz_secure_orm.md` and `docs\u002Ftoolkit_unified_system\u002F11_database_patterns.md`\n5. Study corresponding files in `examples\u002Ftoolkit\u002Fusers-info\u002F` for the layers being created\n\nPresent to the user:\n- Proposed directory structure\n- SDK trait definition (if SDK needed)\n- Domain model outline\n- REST endpoints list (if rest capability)\n- DB entities list (if db capability)\n\nGet approval before writing code.\n\n### Phase 3 — Scaffold\n\nCreate files in this order (each layer builds on the previous):\n\n1. **SDK crate** (if needed): `\u003Cgear>-sdk\u002F` with `Cargo.toml`, `src\u002Flib.rs`, `src\u002Fclient.rs`, `src\u002Fmodels.rs`, `src\u002Ferrors.rs`\n2. **Gear crate**: `\u003Cgear>\u002FCargo.toml`, `src\u002Flib.rs`, `src\u002Fgear.rs`, `src\u002Fconfig.rs`\n3. **Contract layer**: `src\u002Fcontract\u002F` — re-export from SDK or define inline\n4. **Domain layer**: `src\u002Fdomain\u002Ferror.rs`, `src\u002Fdomain\u002Fservice\u002F`, `src\u002Fdomain\u002Frepos\u002F`\n5. **Infra layer** (if db): `src\u002Finfra\u002Fstorage\u002Fentity\u002F`, `src\u002Finfra\u002Fstorage\u002Fmapper.rs`, `src\u002Finfra\u002Fstorage\u002Fmigrations\u002F`\n6. **API layer** (if rest): `src\u002Fapi\u002Frest\u002Fdto.rs`, `src\u002Fapi\u002Frest\u002Fhandlers\u002F`, `src\u002Fapi\u002Frest\u002Froutes\u002F`, `src\u002Fapi\u002Frest\u002Ferror.rs`\n7. **Local client**: `src\u002Fdomain\u002Flocal_client\u002F`\n\n### Phase 4 — Wire and register\n\n1. Add gear crate(s) to workspace `Cargo.toml`\n2. Register gear in `apps\u002Fcf-gears-example-server\u002Fsrc\u002Fmain.rs`\n3. Register client in `init()` via ClientHub\n4. Add feature flag if needed (see existing `static-authn` \u002F `static-authz` pattern)\n\n### Phase 5 — Verify\n\n1. `cargo build -p \u003Cgear-crate>` — must compile\n2. `cargo clippy -p \u003Cgear-crate>` — no warnings\n3. `cargo gears lint --dylint` — architecture lints pass\n4. `cargo test -p \u003Cgear-crate>` — tests pass\n\n## Workflow: Edit an existing gear\n\n### Step 1 — Understand scope\n\nAsk the user what they want to change. Common tasks:\n\n- Add a new REST endpoint\n- Add a new DB entity\n- Add OData filtering to an existing endpoint\n- Add a new domain service method\n- Add error variants\n- Add lifecycle\u002Fbackground task\n- Add plugin support\n\n### Step 2 — Load relevant docs\n\nUse the document routing table above. Load only what's needed for the specific change.\n\n### Step 3 — Study existing code\n\nRead the gear's current implementation. Compare with `examples\u002Ftoolkit\u002Fusers-info\u002F` for the same layer.\n\n### Step 4 — Implement\n\nFollow the DDD-light layer rules:\n\n- **Contract**: NO serde, NO utoipa, NO HTTP types\n- **API\u002FREST DTOs**: MUST have `Serialize`, `Deserialize`, `ToSchema`; MUST be in `api\u002Frest\u002F`\n- **Domain**: All non-module-private structs\u002Fenums (`pub`\u002F`pub(crate)`\u002F`pub(super)`) MUST have `#[domain_model]` (strictly module-private helpers are exempt)\n- **Entities**: Use `#[derive(Scopable)]` with `#[secure(tenant_col = \"...\")]`\n- **Endpoints**: MUST follow `\u002F{service-name}\u002Fv{N}\u002F{resource}` pattern\n- **Errors**: Use `Problem` (RFC-9457), implement `From\u003CDomainError> for Problem`\n\n### Step 5 — Verify\n\nSame as Phase 5 of the create workflow.\n\n## Key invariants\n\nThese rules apply to ALL gear work. Violating them will fail CI:\n\n- SDK pattern is the public API — use `\u003Cgear>-sdk` crate\n- `SecureConn` + `AccessScope` for all DB access — no raw connections\n- `OperationBuilder` for all REST routes — with `.authenticated()` and `.standard_errors()`\n- `#[domain_model]` on all non-module-private domain structs\u002Fenums (DE0309 lint; strictly private helpers exempt)\n- No `unwrap()` \u002F `expect()` — use proper Result types\n- AuthZ via `PolicyEnforcer` PEP pattern — never construct `AccessScope` manually\n",{"name":5,"description":7,"user-invocable":24},true,"main","d2ba1a2b858d1ef133042da64f9cf0e4b836b698",".claude\u002Fskills\u002Fgear-creator",52,"https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust","https:\u002F\u002Fwww.constructorfabric.org","https:\u002F\u002Fgithub.com\u002Fconstructorfabric","https:\u002F\u002Fconstructorfabric.org","A unified fabric that automates the entire XaaS software development lifecycle  from planning to building to running services in prod","2026-11-12 06:13:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":24},[37,40,43],{"tool":38,"command":39},"npx","npx skills add constructorfabric\u002Fgears-rust --skill gear-creator",{"tool":41,"command":42},"bunx","bunx skills add constructorfabric\u002Fgears-rust --skill gear-creator",{"tool":44,"command":45},"pnpm","pnpm dlx skills add constructorfabric\u002Fgears-rust --skill gear-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgear-creator\u002FSKILL.md",[],[49,56,63],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M74EQXWE7S8NAECAK848E1F8","toolkit-pr-review","Review Rust changes against idiomatic Rust guidelines and ToolKit framework rules. PR mode posts inline comments on GitHub; local mode reviews a branch against main and writes a markdown report.","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftoolkit-pr-review\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M74EQSPA2TPGNCHZ4D9RZF2C","gts-analyze","Analyze how the GTS (Global Type System) is used in a Gear — defined types, declared instances, and references across sdk \u002F main \u002F plugin \u002F docs. Thin wrapper around the `gts-analyze` CLI under tools\u002F.","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgts-analyze\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"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":66,"categories":67,"keywords":68,"publishedAt":19},"01M74EQMKC5BCX7GYTY7TXT4M4","config","https:\u002F\u002Fgithub.com\u002Fconstructorfabric\u002Fgears-rust\u002Fblob\u002Fmain\u002F.cf-studio\u002Fconfig\u002FSKILL.md",[],[]]