[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AXBMPQ39YJQB2JCP8QHR4G":3,"skill-same:01M7AXBMPQ39YJQB2JCP8QHR4G":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AXBMPQ39YJQB2JCP8QHR4G","new-service",null,"Use when scaffolding a new SPA + Hono Worker + D1 service, with or without a Tauri native shell.","kta\u002Fthe-services-template","kta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7880965?v=4","01M7AXBA4NE7SGSBH8FX71QT1H","Sakakibara","01M7AXBA5HX5WPKJD1T6W1Y9XJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkta\u002Fthe-services-template\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnew-service\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: new-service\ndescription: Use when scaffolding a new SPA + Hono Worker + D1 service, with or without a Tauri native shell.\n---\n\n# New service\n\nFollow `specs\u002FREADME.md` and `AGENTS.md`. If no service name was supplied, ask for it.\n\n## Required template choice\n\nBefore copying anything, ask the user to choose exactly one template and wait for the answer:\n\n- **Web only (recommended and default):** after this answer, copy `services\u002Fexample_service`.\n- **Web + Tauri:** after this answer, copy `services\u002Fexample_tauri_service`.\n\nDo not copy either template before the user answers. Do not infer Tauri from the product idea or silently keep\u002Fremove native assets after copying. If the answer is ambiguous, ask again. Confirm the implementation plan before large changes (absolute rule #10: no unapproved architecture or library decisions).\n\n## Web only branch\n\n1. Copy tracked source from `services\u002Fexample_service` to `services\u002F\u003Cservice-name>`, excluding `dist`, `node_modules`, `.wrangler`, `worker-configuration.d.ts`, generated coverage\u002FPlaywright output, local `.dev.vars`, and `migrations\u002F*`.\n2. Rename the package to `@app\u002F\u003Cservice-name>`, the D1 `database_name` to the underscored service name, the Wrangler Worker `name` to its hyphenated DNS-label form, storage keys, and dev\u002FE2E ports. Keep same-origin browser transport and session storage. The generated service must not contain `src-tauri`, `@tauri-apps\u002F*` dependencies, or `tauri` \u002F `tauri:*` \u002F `*:tauri` scripts.\n3. Register the service in root `service-catalog.json` with its directory\u002Fpackage, `templateKind: \"web\"`, and explicit deployable\u002Fnative flags. Worker-only entries stay outside the SPA array and use normalized `{ directory, package, deployable }` objects in `workerOnlyServices`. Run `node scripts\u002Fservice-catalog.mjs validate` so the workspace and catalog cannot drift.\n4. Verify this branch with:\n   - `pnpm --filter @app\u002F\u003Cservice-name> test:all`\n   - `pnpm --filter @app\u002F\u003Cservice-name> typecheck`\n   - `pnpm --filter @app\u002F\u003Cservice-name> e2e`\n   - `node scripts\u002Fcheck-tauri-boundary.mjs`\n\n## Web + Tauri branch\n\n1. Copy tracked source from `services\u002Fexample_tauri_service` to `services\u002F\u003Cservice-name>`, excluding `dist`, `node_modules`, `.wrangler`, `worker-configuration.d.ts`, generated coverage\u002FPlaywright output, local `.dev.vars`, `migrations\u002F*`, `src-tauri\u002Fgen`, and `src-tauri\u002Ftarget`.\n2. Rename every Web and native identity: package, D1, hyphenated Worker name, dev\u002FE2E ports, Tauri `productName` and `identifier`, Rust crate\u002Flibrary, fixed `TAURI_\u003CSERVICE>_API_ORIGIN` build variable and release allowlist, navigation guard, native\u002Fbrowser storage keys, capability description, and Android\u002FiOS\u002FmacOS overlays. Copy and rename `tauri-boundary.json`; explicitly review its `releaseOrigin` and every browser storage `path`, `tokenKey`, optional `organizationKey` \u002F `logoutIntentKey`, and service-specific `reason`. Do not leave template keys\u002Freasons, invent an implicit empty allowlist, or broaden the release-origin allowlist. Keep Vite `strictPort: true`; `TAURI_DEV_HOST` may affect development HMR only.\n3. Register the service in root `service-catalog.json` with its directory\u002Fpackage, `templateKind: \"tauri\"`, `native: true`, the reviewed deployable flag, and a unique `nativeWorkflow`. Copy and rename the example Tauri manual artifact workflow to that exact path. Run `node scripts\u002Fservice-catalog.mjs validate` and `node --test scripts\u002Fcheck-deploy-boundary.test.mjs` to prove CI Rust manifests, generic Make native targets, and artifact workflows match the validated catalog native set.\n4. Verify this branch with:\n   - `pnpm --filter @app\u002F\u003Cservice-name> test:all`\n   - `pnpm --filter @app\u002F\u003Cservice-name> typecheck`\n   - `pnpm --filter @app\u002F\u003Cservice-name> e2e`\n   - `cargo fmt --check --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml`\n   - `cargo test --locked --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml`\n   - `cargo clippy --all-targets --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml -- -D warnings`\n   - `make build\u002F\u003Cservice-name>\u002Ftauri`\n   - `node scripts\u002Fcheck-tauri-boundary.mjs`\n\n## Common service work\n\n1. **Specify first:** copy `specs\u002F_service-template` to `specs\u002F\u003Cservice-name>` and fill in `00_service-spec.md` (boundary, entity, API surface, owned D1).\n2. **Contract:** add and export `packages\u002Fcontracts\u002Fsrc\u002F\u003Cservice-name>.ts` using Zod as the single source.\n3. **Domain implementation:** replace the example item routes, Drizzle schema, and UI. Write tests first. A production domain receives `JWT_PUBLIC_KEY` only; admin retains `JWT_PRIVATE_KEY`. Keep `AUTH_DEV_PRIVATE_KEY` \u002F `AUTH_DEV_GRANT` local-only.\n4. **Local wiring:** add the service to `DEV_ALL_SERVICES`; retain `dev` and a regular `.dev.vars.example`; run `make dev-vars`, `make -n dev\u002F\u003Cservice-name>`, and `make -n dev\u002Fall`. `make dev-vars` discovers the new SPA from the validated catalog and distributes the admin-generated local RSA pair automatically; do not add a second hard-coded service list or copy keys by hand.\n5. **DB and UI:** generate\u002Fapply local migrations, add Terraform D1\u002Foutput, and follow `docs\u002Ffrontend\u002FDESIGN_RULE.md` before writing JSX.\n6. **Platform services:** register ops monitoring\u002Fbackups and add the admin production identity only for a catalog `deployable: true` domain. The identity follows one strict convention: catalog directory `booking_service`, Worker service `booking-service`, admin binding `BOOKING_SERVICE`, caller secret `ADMIN_TO_BOOKING_SERVICE_KEY`, and the matching `{directory,binding,secret}` entry in `ADMIN_DOMAIN_IDENTITIES`. Add the binding and secret to generated `Env` with `cf-typegen`. The non-deployable scaffold binding\u002Fkey stay dev\u002Ftest-only; when the catalog has no deployable domain, the production binding\u002Fsecret sets and identity array stay empty.\n7. **Repository wiring:** every SPA service goes in the root combined `test:all` chain and CI manual E2E matrix; every worker-only service uses the root `test` chain. If `deployable: true`, `node scripts\u002Fservice-catalog.mjs require-deployable \u003Cservice-name>` must pass before any bootstrap package selection or credential, and the service must appear exactly once in every ordered protected-main build, artifact verifier\u002Ftar\u002Finstall, config, migration (D1 services), deploy, D1\u002Fservice-binding\u002Fhealth\u002Fbackup, remote-secret, and bootstrap surface. If `deployable: false`, keep it out of all production surfaces. Never add a local production deploy or remote-migration entry point. Run `node scripts\u002Fservice-catalog.mjs validate-repository`; it parses actual workflow nodes and rejects omissions, extras, duplicates, comments used as registrations, and identity drift.\n8. **Final verification:** run `pnpm install`, the selected branch verification above, `node scripts\u002Fservice-catalog.mjs validate-repository`, and `pnpm check`.\n","# New service\n\nFollow `specs\u002FREADME.md` and `AGENTS.md`. If no service name was supplied, ask for it.\n\n## Required template choice\n\nBefore copying anything, ask the user to choose exactly one template and wait for the answer:\n\n- **Web only (recommended and default):** after this answer, copy `services\u002Fexample_service`.\n- **Web + Tauri:** after this answer, copy `services\u002Fexample_tauri_service`.\n\nDo not copy either template before the user answers. Do not infer Tauri from the product idea or silently keep\u002Fremove native assets after copying. If the answer is ambiguous, ask again. Confirm the implementation plan before large changes (absolute rule #10: no unapproved architecture or library decisions).\n\n## Web only branch\n\n1. Copy tracked source from `services\u002Fexample_service` to `services\u002F\u003Cservice-name>`, excluding `dist`, `node_modules`, `.wrangler`, `worker-configuration.d.ts`, generated coverage\u002FPlaywright output, local `.dev.vars`, and `migrations\u002F*`.\n2. Rename the package to `@app\u002F\u003Cservice-name>`, the D1 `database_name` to the underscored service name, the Wrangler Worker `name` to its hyphenated DNS-label form, storage keys, and dev\u002FE2E ports. Keep same-origin browser transport and session storage. The generated service must not contain `src-tauri`, `@tauri-apps\u002F*` dependencies, or `tauri` \u002F `tauri:*` \u002F `*:tauri` scripts.\n3. Register the service in root `service-catalog.json` with its directory\u002Fpackage, `templateKind: \"web\"`, and explicit deployable\u002Fnative flags. Worker-only entries stay outside the SPA array and use normalized `{ directory, package, deployable }` objects in `workerOnlyServices`. Run `node scripts\u002Fservice-catalog.mjs validate` so the workspace and catalog cannot drift.\n4. Verify this branch with:\n   - `pnpm --filter @app\u002F\u003Cservice-name> test:all`\n   - `pnpm --filter @app\u002F\u003Cservice-name> typecheck`\n   - `pnpm --filter @app\u002F\u003Cservice-name> e2e`\n   - `node scripts\u002Fcheck-tauri-boundary.mjs`\n\n## Web + Tauri branch\n\n1. Copy tracked source from `services\u002Fexample_tauri_service` to `services\u002F\u003Cservice-name>`, excluding `dist`, `node_modules`, `.wrangler`, `worker-configuration.d.ts`, generated coverage\u002FPlaywright output, local `.dev.vars`, `migrations\u002F*`, `src-tauri\u002Fgen`, and `src-tauri\u002Ftarget`.\n2. Rename every Web and native identity: package, D1, hyphenated Worker name, dev\u002FE2E ports, Tauri `productName` and `identifier`, Rust crate\u002Flibrary, fixed `TAURI_\u003CSERVICE>_API_ORIGIN` build variable and release allowlist, navigation guard, native\u002Fbrowser storage keys, capability description, and Android\u002FiOS\u002FmacOS overlays. Copy and rename `tauri-boundary.json`; explicitly review its `releaseOrigin` and every browser storage `path`, `tokenKey`, optional `organizationKey` \u002F `logoutIntentKey`, and service-specific `reason`. Do not leave template keys\u002Freasons, invent an implicit empty allowlist, or broaden the release-origin allowlist. Keep Vite `strictPort: true`; `TAURI_DEV_HOST` may affect development HMR only.\n3. Register the service in root `service-catalog.json` with its directory\u002Fpackage, `templateKind: \"tauri\"`, `native: true`, the reviewed deployable flag, and a unique `nativeWorkflow`. Copy and rename the example Tauri manual artifact workflow to that exact path. Run `node scripts\u002Fservice-catalog.mjs validate` and `node --test scripts\u002Fcheck-deploy-boundary.test.mjs` to prove CI Rust manifests, generic Make native targets, and artifact workflows match the validated catalog native set.\n4. Verify this branch with:\n   - `pnpm --filter @app\u002F\u003Cservice-name> test:all`\n   - `pnpm --filter @app\u002F\u003Cservice-name> typecheck`\n   - `pnpm --filter @app\u002F\u003Cservice-name> e2e`\n   - `cargo fmt --check --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml`\n   - `cargo test --locked --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml`\n   - `cargo clippy --all-targets --manifest-path services\u002F\u003Cservice-name>\u002Fsrc-tauri\u002FCargo.toml -- -D warnings`\n   - `make build\u002F\u003Cservice-name>\u002Ftauri`\n   - `node scripts\u002Fcheck-tauri-boundary.mjs`\n\n## Common service work\n\n1. **Specify first:** copy `specs\u002F_service-template` to `specs\u002F\u003Cservice-name>` and fill in `00_service-spec.md` (boundary, entity, API surface, owned D1).\n2. **Contract:** add and export `packages\u002Fcontracts\u002Fsrc\u002F\u003Cservice-name>.ts` using Zod as the single source.\n3. **Domain implementation:** replace the example item routes, Drizzle schema, and UI. Write tests first. A production domain receives `JWT_PUBLIC_KEY` only; admin retains `JWT_PRIVATE_KEY`. Keep `AUTH_DEV_PRIVATE_KEY` \u002F `AUTH_DEV_GRANT` local-only.\n4. **Local wiring:** add the service to `DEV_ALL_SERVICES`; retain `dev` and a regular `.dev.vars.example`; run `make dev-vars`, `make -n dev\u002F\u003Cservice-name>`, and `make -n dev\u002Fall`. `make dev-vars` discovers the new SPA from the validated catalog and distributes the admin-generated local RSA pair automatically; do not add a second hard-coded service list or copy keys by hand.\n5. **DB and UI:** generate\u002Fapply local migrations, add Terraform D1\u002Foutput, and follow `docs\u002Ffrontend\u002FDESIGN_RULE.md` before writing JSX.\n6. **Platform services:** register ops monitoring\u002Fbackups and add the admin production identity only for a catalog `deployable: true` domain. The identity follows one strict convention: catalog directory `booking_service`, Worker service `booking-service`, admin binding `BOOKING_SERVICE`, caller secret `ADMIN_TO_BOOKING_SERVICE_KEY`, and the matching `{directory,binding,secret}` entry in `ADMIN_DOMAIN_IDENTITIES`. Add the binding and secret to generated `Env` with `cf-typegen`. The non-deployable scaffold binding\u002Fkey stay dev\u002Ftest-only; when the catalog has no deployable domain, the production binding\u002Fsecret sets and identity array stay empty.\n7. **Repository wiring:** every SPA service goes in the root combined `test:all` chain and CI manual E2E matrix; every worker-only service uses the root `test` chain. If `deployable: true`, `node scripts\u002Fservice-catalog.mjs require-deployable \u003Cservice-name>` must pass before any bootstrap package selection or credential, and the service must appear exactly once in every ordered protected-main build, artifact verifier\u002Ftar\u002Finstall, config, migration (D1 services), deploy, D1\u002Fservice-binding\u002Fhealth\u002Fbackup, remote-secret, and bootstrap surface. If `deployable: false`, keep it out of all production surfaces. Never add a local production deploy or remote-migration entry point. Run `node scripts\u002Fservice-catalog.mjs validate-repository`; it parses actual workflow nodes and rejects omissions, extras, duplicates, comments used as registrations, and identity drift.\n8. **Final verification:** run `pnpm install`, the selected branch verification above, `node scripts\u002Fservice-catalog.mjs validate-repository`, and `pnpm check`.\n",{"name":5,"description":7},"main","c98b152fec99a506615fbcd7f15162627570fa09",".agents\u002Fskills\u002Fnew-service","https:\u002F\u002Fgithub.com\u002Fkta\u002Fthe-services-template","https:\u002F\u002Fgithub.com\u002Fkta","2026-08-31 16:54:07",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add kta\u002Fthe-services-template --skill new-service",{"tool":36,"command":37},"bunx","bunx skills add kta\u002Fthe-services-template --skill new-service",{"tool":39,"command":40},"pnpm","pnpm dlx skills add kta\u002Fthe-services-template --skill new-service","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkta\u002Fthe-services-template\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnew-service\u002FSKILL.md",true,[],[45,52],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7AXBHT16H9B7SD0J5SM904T","design-select","Use when creating a new screen or significantly changing a UI's look. Presents 2-3 design candidates as clickable HTML mockups in the user's browser (local preview server), lets the user pick one, then implements the winner per DESIGN_RULE.","https:\u002F\u002Fgithub.com\u002Fkta\u002Fthe-services-template\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdesign-select\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AXBG8EAXEMES5PZ17W9KX5","check","Run the full check (lint + typecheck + test with coverage) and fix failures until green.","https:\u002F\u002Fgithub.com\u002Fkta\u002Fthe-services-template\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcheck\u002FSKILL.md",[],[]]