[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABJCPC7BRZ2R6ZY2M4E1XB":3,"skill-same:01M7ABJCPC7BRZ2R6ZY2M4E1XB":58},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7ABJCPC7BRZ2R6ZY2M4E1XB","nodejs-best-practices",null,"Node.js backend conventions — framework selection, API layering, error propagation, async performance, boundary validation, testing, security, and production gates. Use when architecting, building, reviewing, or deploying Node.js backend services. Not for browser\u002Ffrontend JavaScript.","j0hanz\u002Fj0hanz-marketplace","j0hanz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159924955?v=4","01M7ABFK415CKHXYV9GZRJ16T7","Linus Johansson","01M7ABFK52FCPP2PNBH1YR7ZPA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fnodejs\u002Fskills\u002Fnodejs-best-practices\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nodejs-best-practices\ndescription: 'Node.js backend conventions — framework selection, API layering, error propagation, async performance, boundary validation, testing, security, and production gates. Use when architecting, building, reviewing, or deploying Node.js backend services. Not for browser\u002Ffrontend JavaScript.'\nmetadata:\n  category: reference\n---\n\n# Node.js Best Practices\n\nEvaluate project constraints and select explicit matches. For security-sensitive surfaces (auth, payments, user data, public traffic), load [SECURITY.md](SECURITY.md). Prior to deployment or containerization, load [PRODUCTION.md](PRODUCTION.md). Applying a section means every checklist item in it is accounted for: applied, or skipped with a stated reason.\n\n## 1. Framework\n\nDefault: **Fastify** (high throughput, schema-first validation, native TypeScript). Select alternatives when constraints match:\n\n| Condition                                                  | Choice                                                                          | Rationale                                                                                                    |\n| :--------------------------------------------------------- | :------------------------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------- |\n| Edge\u002Fserverless, or minimal-footprint general Node service | **Hono**                                                                        | ~14KB, web-standard Request\u002FResponse; identical code on Node (`@hono\u002Fnode-server`), Bun, Deno, edge runtimes |\n| Enterprise codebases requiring structured DI               | **NestJS**                                                                      | Enforced modular conventions across teams (Express 5 by default; swap in the Fastify adapter for throughput) |\n| Codebase with an established Express middleware ecosystem  | **Express**                                                                     | Express 5.x is stable; ecosystem compatibility                                                               |\n| Type-safe full-stack RPC API                               | **tRPC** (internal TS monorepo) or **oRPC** (adds OpenAPI + REST compatibility) | Shared end-to-end TypeScript types                                                                           |\n\n## 2. Runtime and modules\n\n- **Runtime**: Node.js Active LTS pinned via `.nvmrc` and `package.json#engines`. Use native `node --watch` for local development hot-reloading (eliminating nodemon). (Bun\u002FDeno reserved for dedicated standalone tooling).\n- **TypeScript**: Use Node built-in type stripping (`--experimental-strip-types` since 22.6, unflagged since 23.6, stable since 24) for lightweight scripts and small services adhering to erasable syntax (interfaces, type aliases, type-only imports; enums, namespaces, and parameter properties need `--experimental-transform-types` instead of the stable stripper). Enforce with TypeScript's `erasableSyntaxOnly` compiler option (TS 5.8+) so the codebase never silently drifts onto non-erasable syntax. Use standard build tools (`tsc`, `tsup`, `tsx`, `esbuild`) for production services and decorator-heavy frameworks (NestJS).\n- **Modules**: ESM (`import`\u002F`export`) by default. Import built-ins with explicit `node:` prefix (`node:fs\u002Fpromises`, `node:crypto`).\n\n## 3. Architecture\n\nOrganize by **business domain module** (`users\u002F`, `orders\u002F`, `billing\u002F`), each internally layered:\n\n```\nmodule\u002F\n├── routes\u002Fcontroller  — HTTP transport, parameter extraction, boundary validation\n├── service            — business logic, framework-agnostic\n└── repository         — data access, database queries, ORM entities\n```\n\nConfiguration resolves hierarchically: defaults \u003C `.env` (loaded natively via `node --env-file=.env`) \u003C environment variables. Load secrets strictly from environment variables or a secret manager.\n\n## 4. Errors\n\nSplit errors into two distinct lifecycles:\n\n- **Operational errors** (invalid input, resource not found, upstream timeout): Return structured HTTP responses and maintain continuous uptime.\n- **Programmer errors** (unhandled exceptions, null dereferences): Log error context, stop accepting new connections, drain active requests, and forcefully terminate (`process.exit(1)`) to let the container orchestrator restart a clean instance.\n\nHandling rules:\n\n- Throw custom domain error classes carrying HTTP status codes and machine-readable `code` identifiers.\n- Consolidate error mapping in a single central error middleware at application root.\n- Server logs receive stack trace, request parameters, and correlation ID; HTTP responses receive only user-safe message, status, and code.\n- Return or `await` all promises inside async handlers to preserve full asynchronous stack traces.\n- Attach error event listeners to streams, event emitters, and process unhandled rejection hooks.\n\n## 5. Async and the event loop\n\n- Execute independent asynchronous operations concurrently with `Promise.all` or `Promise.allSettled`.\n- Offload CPU-bound tasks (cryptography, image transformations, heavy parsing) to worker threads, background queues, or dedicated services.\n- Use `node:fs\u002Fpromises` in request execution paths; reserve synchronous `fs` methods exclusively for startup initialization.\n- Stream large file payloads and database query results rather than buffering in memory.\n- Prefer modern built-in APIs over third-party packages: `node:crypto.randomUUID()`, `structuredClone()`, global `fetch`\u002F`Request`\u002F`Response`, `node:util.parseArgs()`, `AsyncLocalStorage` (`node:async_hooks`) for request context propagation, and `performance.eventLoopUtilization()` (`node:perf_hooks`) for event loop health.\n\n## 6. Validation\n\nValidate all external inputs at the boundary: request body, query params, headers, environment variables, and third-party API responses.\n\nDefault: **Zod v4** (2.3× smaller core bundle, up to 14× faster parsing, ~100× faster type instantiation than v3 — confirm the lockfile resolves v4, not legacy v3). Switch when constraints match: edge bundle size $\\rightarrow$ **Valibot**, or `zod\u002Fmini` (~1.9KB) to stay on the Zod ecosystem; hot-path throughput $\\rightarrow$ **ArkType** (Zod v4 has narrowed this gap significantly — benchmark before switching). Reject invalid payloads immediately at the route boundary before passing to domain services.\n\n## 7. Security\n\nBaseline requirements for every service (full hardening checklist: [SECURITY.md](SECURITY.md) — load for auth, payment, public-facing, or compliance-sensitive work):\n\n- Validate all boundary inputs with strict schemas; parameterize all database queries.\n- Hash passwords with `argon2id`; pin JWT algorithms and verify signature and expiration.\n- Apply rate limiting on public and auth endpoints; enforce payload size caps.\n- Enable security headers via `helmet`; configure explicit CORS allowed domain origins.\n- Load secrets strictly from environment\u002Fsecret managers; enforce committed lockfile via `npm ci --ignore-scripts`, and verify package provenance\u002Fsignatures (`npm audit signatures`) for critical dependencies.\n- Check regular expressions for ReDoS vulnerabilities to protect the single-threaded event loop.\n\n## 8. Testing\n\nDefault runner: built-in `node --test` with `node:assert` — stable, with built-in mocking (`mock.fn`, `mock.module`, `mock.timers`), coverage, and watch mode. Switch to **Vitest** for snapshot testing (`node:test`'s one missing feature), richer mocking ergonomics, or Jest compatibility. API integration tests via **Supertest** or native `fetch` against the test server instance.\n\nExecution standards:\n\n- Structure test cases with explicit context and expected outcome; organize bodies into **Arrange–Act–Assert**.\n- Provide isolated database records per test case; mock external third-party HTTP dependencies.\n- For critical paths (auth, billing, transactional workflows), assert all applicable side effects: response payload, database state mutations, outbound HTTP calls, queued jobs, and emitted telemetry.\n\n## 9. Production\n\nPre-deploy baseline (full production and Docker checklist: [PRODUCTION.md](PRODUCTION.md) — load before deployment, containerization, or scaling work):\n\n- Set `NODE_ENV=production`, pin Active LTS Node, and execute `npm ci` from committed lockfile.\n- Stream structured JSON logs directly to `stdout` with request correlation IDs via Pino.\n- Instrument distributed tracing and metrics with OpenTelemetry (`@opentelemetry\u002Fsdk-node` + auto-instrumentations, bootstrapped via `node --import`), correlated with Pino logs through shared trace\u002Fspan IDs.\n- Maintain stateless processes; delegate TLS termination, compression, and static assets to a reverse proxy.\n- Implement graceful shutdown on `SIGTERM` with active connection draining and hard exit timeout.\n\n## Decision checklist\n\nAccount for each item before completing implementation; clarify ambiguous constraints with the user:\n\n- [ ] Framework selected according to routing and runtime requirements.\n- [ ] Active LTS Node version pinned in `.nvmrc` and `package.json`.\n- [ ] Codebase structured into domain modules with route, service, and repository layers.\n- [ ] Central error-handling middleware registered with operational vs programmer error branching.\n- [ ] Asynchronous request paths free of blocking synchronous calls or unhandled promise rejections.\n- [ ] Input validation schemas attached to all route handlers and environment variables.\n- [ ] Integration tests verify response payload and persistent state mutations for critical flows.\n- [ ] Loaded [SECURITY.md](SECURITY.md) for public, auth, or sensitive data surfaces.\n- [ ] Loaded [PRODUCTION.md](PRODUCTION.md) prior to containerization and deployment.\n","# Node.js Best Practices\n\nEvaluate project constraints and select explicit matches. For security-sensitive surfaces (auth, payments, user data, public traffic), load [SECURITY.md](SECURITY.md). Prior to deployment or containerization, load [PRODUCTION.md](PRODUCTION.md). Applying a section means every checklist item in it is accounted for: applied, or skipped with a stated reason.\n\n## 1. Framework\n\nDefault: **Fastify** (high throughput, schema-first validation, native TypeScript). Select alternatives when constraints match:\n\n| Condition                                                  | Choice                                                                          | Rationale                                                                                                    |\n| :--------------------------------------------------------- | :------------------------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------- |\n| Edge\u002Fserverless, or minimal-footprint general Node service | **Hono**                                                                        | ~14KB, web-standard Request\u002FResponse; identical code on Node (`@hono\u002Fnode-server`), Bun, Deno, edge runtimes |\n| Enterprise codebases requiring structured DI               | **NestJS**                                                                      | Enforced modular conventions across teams (Express 5 by default; swap in the Fastify adapter for throughput) |\n| Codebase with an established Express middleware ecosystem  | **Express**                                                                     | Express 5.x is stable; ecosystem compatibility                                                               |\n| Type-safe full-stack RPC API                               | **tRPC** (internal TS monorepo) or **oRPC** (adds OpenAPI + REST compatibility) | Shared end-to-end TypeScript types                                                                           |\n\n## 2. Runtime and modules\n\n- **Runtime**: Node.js Active LTS pinned via `.nvmrc` and `package.json#engines`. Use native `node --watch` for local development hot-reloading (eliminating nodemon). (Bun\u002FDeno reserved for dedicated standalone tooling).\n- **TypeScript**: Use Node built-in type stripping (`--experimental-strip-types` since 22.6, unflagged since 23.6, stable since 24) for lightweight scripts and small services adhering to erasable syntax (interfaces, type aliases, type-only imports; enums, namespaces, and parameter properties need `--experimental-transform-types` instead of the stable stripper). Enforce with TypeScript's `erasableSyntaxOnly` compiler option (TS 5.8+) so the codebase never silently drifts onto non-erasable syntax. Use standard build tools (`tsc`, `tsup`, `tsx`, `esbuild`) for production services and decorator-heavy frameworks (NestJS).\n- **Modules**: ESM (`import`\u002F`export`) by default. Import built-ins with explicit `node:` prefix (`node:fs\u002Fpromises`, `node:crypto`).\n\n## 3. Architecture\n\nOrganize by **business domain module** (`users\u002F`, `orders\u002F`, `billing\u002F`), each internally layered:\n\n```\nmodule\u002F\n├── routes\u002Fcontroller  — HTTP transport, parameter extraction, boundary validation\n├── service            — business logic, framework-agnostic\n└── repository         — data access, database queries, ORM entities\n```\n\nConfiguration resolves hierarchically: defaults \u003C `.env` (loaded natively via `node --env-file=.env`) \u003C environment variables. Load secrets strictly from environment variables or a secret manager.\n\n## 4. Errors\n\nSplit errors into two distinct lifecycles:\n\n- **Operational errors** (invalid input, resource not found, upstream timeout): Return structured HTTP responses and maintain continuous uptime.\n- **Programmer errors** (unhandled exceptions, null dereferences): Log error context, stop accepting new connections, drain active requests, and forcefully terminate (`process.exit(1)`) to let the container orchestrator restart a clean instance.\n\nHandling rules:\n\n- Throw custom domain error classes carrying HTTP status codes and machine-readable `code` identifiers.\n- Consolidate error mapping in a single central error middleware at application root.\n- Server logs receive stack trace, request parameters, and correlation ID; HTTP responses receive only user-safe message, status, and code.\n- Return or `await` all promises inside async handlers to preserve full asynchronous stack traces.\n- Attach error event listeners to streams, event emitters, and process unhandled rejection hooks.\n\n## 5. Async and the event loop\n\n- Execute independent asynchronous operations concurrently with `Promise.all` or `Promise.allSettled`.\n- Offload CPU-bound tasks (cryptography, image transformations, heavy parsing) to worker threads, background queues, or dedicated services.\n- Use `node:fs\u002Fpromises` in request execution paths; reserve synchronous `fs` methods exclusively for startup initialization.\n- Stream large file payloads and database query results rather than buffering in memory.\n- Prefer modern built-in APIs over third-party packages: `node:crypto.randomUUID()`, `structuredClone()`, global `fetch`\u002F`Request`\u002F`Response`, `node:util.parseArgs()`, `AsyncLocalStorage` (`node:async_hooks`) for request context propagation, and `performance.eventLoopUtilization()` (`node:perf_hooks`) for event loop health.\n\n## 6. Validation\n\nValidate all external inputs at the boundary: request body, query params, headers, environment variables, and third-party API responses.\n\nDefault: **Zod v4** (2.3× smaller core bundle, up to 14× faster parsing, ~100× faster type instantiation than v3 — confirm the lockfile resolves v4, not legacy v3). Switch when constraints match: edge bundle size $\\rightarrow$ **Valibot**, or `zod\u002Fmini` (~1.9KB) to stay on the Zod ecosystem; hot-path throughput $\\rightarrow$ **ArkType** (Zod v4 has narrowed this gap significantly — benchmark before switching). Reject invalid payloads immediately at the route boundary before passing to domain services.\n\n## 7. Security\n\nBaseline requirements for every service (full hardening checklist: [SECURITY.md](SECURITY.md) — load for auth, payment, public-facing, or compliance-sensitive work):\n\n- Validate all boundary inputs with strict schemas; parameterize all database queries.\n- Hash passwords with `argon2id`; pin JWT algorithms and verify signature and expiration.\n- Apply rate limiting on public and auth endpoints; enforce payload size caps.\n- Enable security headers via `helmet`; configure explicit CORS allowed domain origins.\n- Load secrets strictly from environment\u002Fsecret managers; enforce committed lockfile via `npm ci --ignore-scripts`, and verify package provenance\u002Fsignatures (`npm audit signatures`) for critical dependencies.\n- Check regular expressions for ReDoS vulnerabilities to protect the single-threaded event loop.\n\n## 8. Testing\n\nDefault runner: built-in `node --test` with `node:assert` — stable, with built-in mocking (`mock.fn`, `mock.module`, `mock.timers`), coverage, and watch mode. Switch to **Vitest** for snapshot testing (`node:test`'s one missing feature), richer mocking ergonomics, or Jest compatibility. API integration tests via **Supertest** or native `fetch` against the test server instance.\n\nExecution standards:\n\n- Structure test cases with explicit context and expected outcome; organize bodies into **Arrange–Act–Assert**.\n- Provide isolated database records per test case; mock external third-party HTTP dependencies.\n- For critical paths (auth, billing, transactional workflows), assert all applicable side effects: response payload, database state mutations, outbound HTTP calls, queued jobs, and emitted telemetry.\n\n## 9. Production\n\nPre-deploy baseline (full production and Docker checklist: [PRODUCTION.md](PRODUCTION.md) — load before deployment, containerization, or scaling work):\n\n- Set `NODE_ENV=production`, pin Active LTS Node, and execute `npm ci` from committed lockfile.\n- Stream structured JSON logs directly to `stdout` with request correlation IDs via Pino.\n- Instrument distributed tracing and metrics with OpenTelemetry (`@opentelemetry\u002Fsdk-node` + auto-instrumentations, bootstrapped via `node --import`), correlated with Pino logs through shared trace\u002Fspan IDs.\n- Maintain stateless processes; delegate TLS termination, compression, and static assets to a reverse proxy.\n- Implement graceful shutdown on `SIGTERM` with active connection draining and hard exit timeout.\n\n## Decision checklist\n\nAccount for each item before completing implementation; clarify ambiguous constraints with the user:\n\n- [ ] Framework selected according to routing and runtime requirements.\n- [ ] Active LTS Node version pinned in `.nvmrc` and `package.json`.\n- [ ] Codebase structured into domain modules with route, service, and repository layers.\n- [ ] Central error-handling middleware registered with operational vs programmer error branching.\n- [ ] Asynchronous request paths free of blocking synchronous calls or unhandled promise rejections.\n- [ ] Input validation schemas attached to all route handlers and environment variables.\n- [ ] Integration tests verify response payload and persistent state mutations for critical flows.\n- [ ] Loaded [SECURITY.md](SECURITY.md) for public, auth, or sensitive data surfaces.\n- [ ] Loaded [PRODUCTION.md](PRODUCTION.md) prior to containerization and deployment.\n",{"name":5,"metadata":24,"description":7},{"category":25},"reference","main","534498267dccbe415f22f31fceac9da6771c195f","plugins\u002Fnodejs\u002Fskills\u002Fnodejs-best-practices","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace","https:\u002F\u002Fj0hanz-marketplace.vercel.app","https:\u002F\u002Fgithub.com\u002Fj0hanz","linus-johansson-cv-d308be9b73e1.herokuapp.com","2026-11-15 02:42:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add j0hanz\u002Fj0hanz-marketplace --skill nodejs-best-practices",{"tool":40,"command":41},"bunx","bunx skills add j0hanz\u002Fj0hanz-marketplace --skill nodejs-best-practices",{"tool":43,"command":44},"pnpm","pnpm dlx skills add j0hanz\u002Fj0hanz-marketplace --skill nodejs-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fnodejs\u002Fskills\u002Fnodejs-best-practices\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"PRODUCTION.md","REFERENCE","参考文档",4070,"https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fnodejs\u002Fskills\u002Fnodejs-best-practices\u002FPRODUCTION.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"SECURITY.md",4374,"https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fnodejs\u002Fskills\u002Fnodejs-best-practices\u002FSECURITY.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7ABP78JFYBMCXJ9GMETCYZM","unslop","Use when writing or editing prose a person will read, or when text sounds AI-generated.","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwriteup\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"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":19},"01M7ABP52BNV7NRPNBR6PCNZWC","show-me","Use when asked to show, diagram, or walk through how code fits together or what a change does, or before explaining a multi-file flow in prose.","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwriteup\u002Fskills\u002Fshow-me\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":19},"01M7ABP3EPN4KFB4HPJNMY31NR","pr","Use when writing or updating a pull request description, or before running `gh pr create`.","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwriteup\u002Fskills\u002Fpr\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":19},"01M7ABP08MXTHPZYTG4HKEP7WQ","commit","Use when writing a commit message, or before running `git commit`.","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwriteup\u002Fskills\u002Fcommit\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":19},"01M7ABNV9J7DN1AFRBGDBHVBY2","write-specs","Spec a feature's observable behavior. Use when asked for requirements, when a request says what the system should do but not how, or to capture what a built system already guarantees. Not for how to build it (write-plan).","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbench\u002Fskills\u002Fwrite-specs\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":19},"01M7ABNPK2GVG8EB3SSEAMK4FZ","write-skills","Write, fix, or audit a skill's frontmatter, trigger description, and body. Use when a skill is asked for, never fires, or fires at the wrong moment. Not for a hook (write-hooks) or the plugin manifest and catalog.","https:\u002F\u002Fgithub.com\u002Fj0hanz\u002Fj0hanz-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbench\u002Fskills\u002Fwrite-skills\u002FSKILL.md",[],[]]