[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79THWQJ3EB9GTMF42CDGNB1":3,"skill-same:01M79THWQJ3EB9GTMF42CDGNB1":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},"01M79THWQJ3EB9GTMF42CDGNB1","express-architect",null,"Architect-level Express guidance — router\u002Fmiddleware layering, error-handling contracts, validation and auth placement, async handler safety, and the deployment model for a stateless Node service. Use when designing or reviewing an Express 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\u002Fexpress-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: express-architect\ndescription: Architect-level Express guidance — router\u002Fmiddleware layering, error-handling contracts, validation and auth placement, async handler safety, and the deployment model for a stateless Node service. Use when designing or reviewing an Express API.\nlicense: MIT\ncompatibility: Express 4\u002F5; Node 20+\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Fexpress-architect\n  crusor-origin: original\n  crusor-sources: \"expressjs.com\u002Fen\u002Fguide; nodejs.org\u002Fapi\u002Fhttp\"\n  crusor-triggers: \"express, expressjs, express router, express middleware, node http, req res next\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Express Architect\n\nExpress gives you a middleware chain and nothing else. Architecture is the\n**order of that chain** and what is allowed to know what.\n\n## When to use\n\n- A Node HTTP API where you want explicit control and minimal surface.\n- Existing Express app that has become a pile of `app.use`.\n- A service small enough that a framework's conventions would be overhead.\n\n## When NOT to use\n\n- Structured, DI-heavy, TypeScript-first service (see `nestjs-architect`).\n- Throughput-critical JSON APIs where schema-first speed matters\n  (`fastify-architect`).\n- Anything needing async-by-default semantics — Express 4 is callback\u002Fpromise\n  land; misconfigured async handlers crash or hang.\n\n## Decision 1 — Chain order (fixed, documented)\n\n```\nrequest id → logging → body limit → security headers → cors\n  → auth (router-scoped) → validation → handler → error handler\n```\n\n- Error handler is **last** and has 4 args; it is the only place that formats\n  errors.\n- Auth is applied per router, not globally, so public routes are explicit.\n- Body size limits before any parsing of untrusted input.\n\n## Decision 2 — Layering\n\n```\nroutes\u002F      express.Router(), path + validation wiring\n  controllers\u002F parse req -> call service -> res\n    services\u002F  use-cases, no req\u002Fres\n      repos\u002F   DB\u002Fqueue\n```\n\n- Controllers never contain SQL; services never touch `req`.\n- Mount routers by bounded context (`\u002Fv1\u002Forders`, `\u002Fv1\u002Fauth`).\n- Async errors: wrap handlers (`asyncHandler`) so rejections reach the error\n  middleware — an unhandled rejection in Express 4 is a silent hang.\n\n## Decision 3 — Contracts\n\n- One error envelope: `{error: {code, message, details?}}` for every failure.\n- Validation at the edge (zod\u002Fjoi), typed thereafter; never trust `req.body`.\n- 404 handler for unmatched routes; 405 where methods differ.\n- Pagination\u002Ffiltering parameters validated and capped.\n\n## Decision 4 — Runtime and deployment\n\n- Stateless processes; sessions in a store, never in memory.\n- `trust proxy` set correctly behind a load balancer, or rate limits and IPs\n  lie.\n- Graceful shutdown: stop accepting, drain, close DB pool.\n- Health endpoints separate liveness from readiness.\n\n## Failure modes at scale\n\n- Middleware added \"temporarily\" that mutates `req` for everyone.\n- Async handler throwing → request hangs until timeout.\n- Global `app.use(auth)` with a growing exception list.\n- Error messages leaking stack traces in production.\n- Business logic duplicated across three route files.\n\n## Verification receipts\n\n1. Middleware order documented and covered by an integration test.\n2. Error path test: thrown service error → correct status + envelope, no stack.\n3. Auth test: public, authenticated, and cross-tenant access.\n4. Shutdown test under load.\n5. Load test at peak with event-loop delay measured.\n","# Express Architect\n\nExpress gives you a middleware chain and nothing else. Architecture is the\n**order of that chain** and what is allowed to know what.\n\n## When to use\n\n- A Node HTTP API where you want explicit control and minimal surface.\n- Existing Express app that has become a pile of `app.use`.\n- A service small enough that a framework's conventions would be overhead.\n\n## When NOT to use\n\n- Structured, DI-heavy, TypeScript-first service (see `nestjs-architect`).\n- Throughput-critical JSON APIs where schema-first speed matters\n  (`fastify-architect`).\n- Anything needing async-by-default semantics — Express 4 is callback\u002Fpromise\n  land; misconfigured async handlers crash or hang.\n\n## Decision 1 — Chain order (fixed, documented)\n\n```\nrequest id → logging → body limit → security headers → cors\n  → auth (router-scoped) → validation → handler → error handler\n```\n\n- Error handler is **last** and has 4 args; it is the only place that formats\n  errors.\n- Auth is applied per router, not globally, so public routes are explicit.\n- Body size limits before any parsing of untrusted input.\n\n## Decision 2 — Layering\n\n```\nroutes\u002F      express.Router(), path + validation wiring\n  controllers\u002F parse req -> call service -> res\n    services\u002F  use-cases, no req\u002Fres\n      repos\u002F   DB\u002Fqueue\n```\n\n- Controllers never contain SQL; services never touch `req`.\n- Mount routers by bounded context (`\u002Fv1\u002Forders`, `\u002Fv1\u002Fauth`).\n- Async errors: wrap handlers (`asyncHandler`) so rejections reach the error\n  middleware — an unhandled rejection in Express 4 is a silent hang.\n\n## Decision 3 — Contracts\n\n- One error envelope: `{error: {code, message, details?}}` for every failure.\n- Validation at the edge (zod\u002Fjoi), typed thereafter; never trust `req.body`.\n- 404 handler for unmatched routes; 405 where methods differ.\n- Pagination\u002Ffiltering parameters validated and capped.\n\n## Decision 4 — Runtime and deployment\n\n- Stateless processes; sessions in a store, never in memory.\n- `trust proxy` set correctly behind a load balancer, or rate limits and IPs\n  lie.\n- Graceful shutdown: stop accepting, drain, close DB pool.\n- Health endpoints separate liveness from readiness.\n\n## Failure modes at scale\n\n- Middleware added \"temporarily\" that mutates `req` for everyone.\n- Async handler throwing → request hangs until timeout.\n- Global `app.use(auth)` with a growing exception list.\n- Error messages leaking stack traces in production.\n- Business logic duplicated across three route files.\n\n## Verification receipts\n\n1. Middleware order documented and covered by an integration test.\n2. Error path test: thrown service error → correct status + envelope, no stack.\n3. Auth test: public, authenticated, and cross-tenant access.\n4. Shutdown test under load.\n5. Load test at peak with event-loop delay measured.\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\u002Fexpress-architect","website-architect","original","expressjs.com\u002Fen\u002Fguide; nodejs.org\u002Fapi\u002Fhttp","express, expressjs, express router, express middleware, node http, req res next","2026-10-30","Express 4\u002F5; Node 20+","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Fexpress-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 express-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill express-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill express-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ffrontend-development-architect\u002Freact-architect\u002Fnodejs-architect\u002Fexpress-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",[],[]]