[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TJ3P8VEC2ZM74M2XP7HAB":3,"skill-same:01M79TJ3P8VEC2ZM74M2XP7HAB":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TJ3P8VEC2ZM74M2XP7HAB","fastify-architect",null,"Architect-level Fastify guidance — schema-first routing and validation, plugin encapsulation boundaries, hook lifecycle ownership, serialisation performance, and the TypeScript typing patterns that keep schemas and handlers in sync. Use when choosing or reviewing Fastify for a Node API.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Ffastify-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fastify-architect\ndescription: Architect-level Fastify guidance — schema-first routing and validation, plugin encapsulation boundaries, hook lifecycle ownership, serialisation performance, and the TypeScript typing patterns that keep schemas and handlers in sync. Use when choosing or reviewing Fastify for a Node API.\nlicense: MIT\ncompatibility: Fastify 4\u002F5; Node 20+\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Ffastify-architect\n  crusor-origin: original\n  crusor-sources: \"fastify.dev\u002Fdocs\u002Flatest; json-schema.org\"\n  crusor-triggers: \"fastify, fastify schema, fastify plugin, schema serializer, fastify hooks, json schema route, encapsulation\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Fastify Architect\n\nFastify's advantages are **schemas** and **encapsulation**. Use it without them\nand you have paid the learning curve for an Express clone.\n\n## When to use\n\n- JSON APIs where request\u002Fresponse schemas are the contract.\n- Services where throughput and validation speed matter.\n- Codebases that benefit from plugin-scoped encapsulation instead of global\n  middleware.\n\n## When NOT to use\n\n- Heavy server-rendered pages — an MVC framework is the better tool.\n- A team that will not maintain JSON schemas; then schema-first is a liability.\n\n## Decision 1 — Schemas are the contract\n\n- Every route declares `schema.body`, `querystring`, `params`, `response`.\n- Response schemas are not optional: they drive fast serialisation **and**\n  prevent accidental field leakage.\n- Schema → TypeScript types via `json-schema-to-ts` or `typebox`, so a schema\n  change breaks compilation, not production.\n- Validation errors are mapped once (`setErrorHandler`) into your envelope.\n\n## Decision 2 — Plugins and encapsulation\n\n```\napp.ts           register plugins, no routes\n  plugins\u002Fdb.ts  fastify-plugin (decorates, shares)\n    routes\u002Fv1\u002F*.ts  encapsulated routers\n```\n\n- `fastify-plugin` breaks encapsulation deliberately — use it only for\n  infrastructure that must decorate the root (db, config, auth).\n- Feature plugins stay encapsulated: their decorators\u002Fhooks do not leak.\n- Register order matters; document it (config → db → auth → routes).\n\n## Decision 3 — Lifecycle hooks\n\n| Hook | Use |\n|---|---|\n| `onRequest` | request id, rate limit |\n| `preValidation` | raw body checks |\n| `preHandler` | auth\u002Fauthorisation, load entity |\n| `onSend` | response headers, mapping |\n| `onClose` | release resources |\n\n- Hooks are applied at the narrowest scope that needs them; a root-level hook\n  affects every route including health checks — usually wrong.\n- Async hooks must be awaited: a forgotten `await` reorders the pipeline.\n- Auth via `decorate` + `preHandler`, and skip explicit for public routes.\n\n## Decision 4 — Performance and deployment\n\n- `pino` logging with redaction; request ids in every line.\n- Keep the event loop clean: no sync fs\u002Fcrypto in handlers, offload CPU work to\n  workers.\n- `connectionTimeout`\u002F`requestTimeout` set explicitly; defaults are generous.\n- Graceful shutdown on `SIGTERM`: `fastify.close()` after draining.\n\n## Failure modes at scale\n\n- Schemas declared for requests but not responses → leaks and slow serialisation.\n- `fastify-plugin` used everywhere, encapsulation gone, root decorated by five\n  features.\n- Root-level auth hook plus a growing `if (route === ...)` exception list.\n- Schema drift from TS types discovered at runtime.\n- Error handler that returns 200 with an error body.\n\n## Verification receipts\n\n1. Every route has body + response schemas (script-checked).\n2. Validation rejection test: extra field, wrong type, oversized payload.\n3. Response test: no field outside the schema is serialised.\n4. Hook scope review: which hooks are root-level and why.\n5. Load test: throughput and p95 with the real schema set.\n","# Fastify Architect\n\nFastify's advantages are **schemas** and **encapsulation**. Use it without them\nand you have paid the learning curve for an Express clone.\n\n## When to use\n\n- JSON APIs where request\u002Fresponse schemas are the contract.\n- Services where throughput and validation speed matter.\n- Codebases that benefit from plugin-scoped encapsulation instead of global\n  middleware.\n\n## When NOT to use\n\n- Heavy server-rendered pages — an MVC framework is the better tool.\n- A team that will not maintain JSON schemas; then schema-first is a liability.\n\n## Decision 1 — Schemas are the contract\n\n- Every route declares `schema.body`, `querystring`, `params`, `response`.\n- Response schemas are not optional: they drive fast serialisation **and**\n  prevent accidental field leakage.\n- Schema → TypeScript types via `json-schema-to-ts` or `typebox`, so a schema\n  change breaks compilation, not production.\n- Validation errors are mapped once (`setErrorHandler`) into your envelope.\n\n## Decision 2 — Plugins and encapsulation\n\n```\napp.ts           register plugins, no routes\n  plugins\u002Fdb.ts  fastify-plugin (decorates, shares)\n    routes\u002Fv1\u002F*.ts  encapsulated routers\n```\n\n- `fastify-plugin` breaks encapsulation deliberately — use it only for\n  infrastructure that must decorate the root (db, config, auth).\n- Feature plugins stay encapsulated: their decorators\u002Fhooks do not leak.\n- Register order matters; document it (config → db → auth → routes).\n\n## Decision 3 — Lifecycle hooks\n\n| Hook | Use |\n|---|---|\n| `onRequest` | request id, rate limit |\n| `preValidation` | raw body checks |\n| `preHandler` | auth\u002Fauthorisation, load entity |\n| `onSend` | response headers, mapping |\n| `onClose` | release resources |\n\n- Hooks are applied at the narrowest scope that needs them; a root-level hook\n  affects every route including health checks — usually wrong.\n- Async hooks must be awaited: a forgotten `await` reorders the pipeline.\n- Auth via `decorate` + `preHandler`, and skip explicit for public routes.\n\n## Decision 4 — Performance and deployment\n\n- `pino` logging with redaction; request ids in every line.\n- Keep the event loop clean: no sync fs\u002Fcrypto in handlers, offload CPU work to\n  workers.\n- `connectionTimeout`\u002F`requestTimeout` set explicitly; defaults are generous.\n- Graceful shutdown on `SIGTERM`: `fastify.close()` after draining.\n\n## Failure modes at scale\n\n- Schemas declared for requests but not responses → leaks and slow serialisation.\n- `fastify-plugin` used everywhere, encapsulation gone, root decorated by five\n  features.\n- Root-level auth hook plus a growing `if (route === ...)` exception list.\n- Schema drift from TS types discovered at runtime.\n- Error handler that returns 200 with an error body.\n\n## Verification receipts\n\n1. Every route has body + response schemas (script-checked).\n2. Validation rejection test: extra field, wrong type, oversized payload.\n3. Response test: no field outside the schema is serialised.\n4. Hook scope review: which hooks are root-level and why.\n5. Load test: throughput and p95 with the real schema set.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Ffastify-architect","website-architect","original","fastify.dev\u002Fdocs\u002Flatest; json-schema.org","fastify, fastify schema, fastify plugin, schema serializer, fastify hooks, json schema route, encapsulation","2026-10-30","Fastify 4\u002F5; Node 20+","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Ffastify-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill fastify-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill fastify-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill fastify-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Ffastify-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]