[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T92D3ETDBYVMS25QWXT0D":3,"skill-same:01M79T92D3ETDBYVMS25QWXT0D":61},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M79T92D3ETDBYVMS25QWXT0D","website-architect",null,"Domain entry for building web products — which branch owns a given decision (frontend, backend, data, API, UI implementation, security, delivery), and the cross-branch rules every web system is held to. Use first when the work is a website, app or web service, then open the branch it names.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: website-architect\ndescription: Domain entry for building web products — which branch owns a given decision (frontend, backend, data, API, UI implementation, security, delivery), and the cross-branch rules every web system is held to. Use first when the work is a website, app or web service, then open the branch it names.\nlicense: Apache-2.0\ncompatibility: Framework-agnostic; any web stack\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\n  crusor-origin: original\n  crusor-sources: \"web.dev; MDN; OWASP ASVS; 12factor.net\"\n  crusor-triggers: \"website, web app, web product, web service, full stack, web architecture, startup, platform, ecommerce, e-commerce, amazon\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Website Architect\n\nA web product is **seven decisions in a trench coat**: tier, rendering, serving, state, contract, trust and delivery. This skill names which branch owns each, and the numbers each is held to.\n\n## When to use\n\n- Starting a web product, or re-planning one that outgrew its structure.\n- A cross-cutting problem: performance, security, data ownership, delivery.\n- Choosing which branch a plan should open.\n\n## When NOT to use\n\n- A single-branch question — go straight to that branch's crown.\n- Native apps, mobile apps or desktop runtimes: those are separate domains.\n\n## Branch map\n\n| Decision | Branch |\n| --- | --- |\n| product tier, full-stack vs prototype | `website-architect` |\n| rendering model, components, styling, motion, a11y, perf | `frontend-development-architect` |\n| language and runtime for server code | `backend-development-architect` |\n| schema, indexing, migrations, transactions | `database-engineering-architect` |\n| contract between clients and server | `api-development-architect` |\n| design → code, interaction, design-system ops | `ui-ux-implementation-architect` |\n| trust boundaries, permissions, secrets, supply chain | `security-architect` |\n| tests, CI, environments, telemetry, rollout | `testing-and-deployment-architect` |\n\n## Decision 0 — Product Tier (Startup Production vs Toy Prototype)\n\n- Any task involving \"startup\", \"platform\", \"e-commerce\", \"marketplace\", \"SaaS\", or \"like \u003Cservice>\" is **Startup Production Tier**.\n- **Toy Prototype Anti-Pattern**: Emitting a purely client-side static HTML\u002FCSS file with hardcoded data arrays and no backend API\u002Fpersistence is strictly forbidden.\n- Startup-grade architecture requires:\n  1. **Persistence Tier**: Relational SQLite (WAL mode) or PostgreSQL with atomic write transactions and models.\n  2. **API & Service Tier**: Runnable backend service with typed JSON REST endpoints and HTTP status contracts.\n  3. **Role Architecture**: Differentiated user surfaces (e.g., Customer storefront + Vendor\u002FSeller\u002FAdmin portal).\n  4. **Integration Tests**: Automated backend test suite verifying database transactions and API integrity.\n\n## Decision 1 — Rendering model\n\nMatch content: SSG\u002FISR for cacheable content, SSR for personalisation above the fold, SPA only behind auth.\n- Dashboards: SSR shell + islands; shell paints from cache in \u003C 1 s.\n- Budget: `LCP ≤ 2.5 s`, `INP ≤ 200 ms`, `CLS ≤ 0.1` at p75 mobile.\n\n## Decision 2 — Where state lives\n\nOne home per kind of state: server data in a query cache (`react-query`, `SWR`), UI state with the screen, session in an `httpOnly` cookie.\n- Stale-by-default (`staleTime` 30 s), refetch on focus; never mirror into redux.\n- If the server can compute it, the server computes it.\n\n## Decision 3 — The contract\n\nThe API is the product boundary: version it (`\u002Fv1`), type it (`OpenAPI`, `tRPC`), generate clients.\n- p95 `≤ 300 ms` at load; `≤ 1 s` for cold authenticated read.\n- Lists paginate (`cursor` once writes are concurrent).\n- Errors carry stable `code`, human `message`, and `request_id`.\n\n## Decision 4 — Data ownership\n\nOne writer per table; reads go through the owner's API, never shared connections.\n- Multi-tenant rows carry `tenant_id` with row-level security.\n- Migrations are expand\u002Fcontract across two deploys, never one.\n\n## Decision 5 — Trust boundaries\n\nAuthenticate at edge, authorise on server with facts server owns — never trust client claims.\n- Cookies: `httpOnly`, `Secure`, `SameSite=Lax`, rotating refresh.\n- Mutations are CSRF- or token-protected; `GET` never mutates.\n- Secrets live in the platform store, rotated.\n\n## Decision 6 — Delivery\n\nDeploy is not release: ship behind a flag, monitor error rate, ramp 1% → 10% → 50% → 100%.\n- Rollback is one rehearsed command.\n- Error budget 99.9% monthly governs whether features ship.\n- Logs, metrics and traces share one `request_id`.\n\n## Rules that hold across every branch\n\n1. **One owner per dataset** — one service writes it; others read through it.\n2. **Contracts before code** — API shape, schema, component API are artefacts.\n3. **State has one home** — no second copy, anywhere.\n4. **Never downgrade a startup to a static mock** — require persistence and API contracts.\n5. **Failure states are designed** — loading, empty, error, partial.\n6. **Authorisation is server-side**, from facts the server owns.\n7. **Nothing ships without a rollback**; flags separate deploy from release.\n8. **Observability precedes launch** — one correlation id across services.\n\n## Architecture review questions\n\n1. What renders each page, and where does its data come from?\n2. Which service owns each write, and what enforces it?\n3. What is cached, for how long, invalidated how?\n4. Who can call each endpoint, and where is that decided?\n5. How does a change reach production, and how is it undone?\n\n## Failure modes at scale\n\n- Downgrading a startup request to a client-only static HTML mock with no real persistence.\n- The frontend owning business rules because the API was never designed.\n- The database becoming the integration layer; services reading each other's tables.\n- Lack of reversibility: deploys, migrations and schema going one way.\n\n## Verification receipts\n\n1. Diagram naming services, stores, boundaries, and owning branches.\n2. `LCP ≤ 2.5 s`, `INP ≤ 200 ms`, `CLS ≤ 0.1` at p75 on throttled mobile.\n3. p95 API latency per endpoint at expected load from a load test.\n4. Automated test suite verifying persistence and API contract coverage.\n","# Website Architect\n\nA web product is **seven decisions in a trench coat**: tier, rendering, serving, state, contract, trust and delivery. This skill names which branch owns each, and the numbers each is held to.\n\n## When to use\n\n- Starting a web product, or re-planning one that outgrew its structure.\n- A cross-cutting problem: performance, security, data ownership, delivery.\n- Choosing which branch a plan should open.\n\n## When NOT to use\n\n- A single-branch question — go straight to that branch's crown.\n- Native apps, mobile apps or desktop runtimes: those are separate domains.\n\n## Branch map\n\n| Decision | Branch |\n| --- | --- |\n| product tier, full-stack vs prototype | `website-architect` |\n| rendering model, components, styling, motion, a11y, perf | `frontend-development-architect` |\n| language and runtime for server code | `backend-development-architect` |\n| schema, indexing, migrations, transactions | `database-engineering-architect` |\n| contract between clients and server | `api-development-architect` |\n| design → code, interaction, design-system ops | `ui-ux-implementation-architect` |\n| trust boundaries, permissions, secrets, supply chain | `security-architect` |\n| tests, CI, environments, telemetry, rollout | `testing-and-deployment-architect` |\n\n## Decision 0 — Product Tier (Startup Production vs Toy Prototype)\n\n- Any task involving \"startup\", \"platform\", \"e-commerce\", \"marketplace\", \"SaaS\", or \"like \u003Cservice>\" is **Startup Production Tier**.\n- **Toy Prototype Anti-Pattern**: Emitting a purely client-side static HTML\u002FCSS file with hardcoded data arrays and no backend API\u002Fpersistence is strictly forbidden.\n- Startup-grade architecture requires:\n  1. **Persistence Tier**: Relational SQLite (WAL mode) or PostgreSQL with atomic write transactions and models.\n  2. **API & Service Tier**: Runnable backend service with typed JSON REST endpoints and HTTP status contracts.\n  3. **Role Architecture**: Differentiated user surfaces (e.g., Customer storefront + Vendor\u002FSeller\u002FAdmin portal).\n  4. **Integration Tests**: Automated backend test suite verifying database transactions and API integrity.\n\n## Decision 1 — Rendering model\n\nMatch content: SSG\u002FISR for cacheable content, SSR for personalisation above the fold, SPA only behind auth.\n- Dashboards: SSR shell + islands; shell paints from cache in \u003C 1 s.\n- Budget: `LCP ≤ 2.5 s`, `INP ≤ 200 ms`, `CLS ≤ 0.1` at p75 mobile.\n\n## Decision 2 — Where state lives\n\nOne home per kind of state: server data in a query cache (`react-query`, `SWR`), UI state with the screen, session in an `httpOnly` cookie.\n- Stale-by-default (`staleTime` 30 s), refetch on focus; never mirror into redux.\n- If the server can compute it, the server computes it.\n\n## Decision 3 — The contract\n\nThe API is the product boundary: version it (`\u002Fv1`), type it (`OpenAPI`, `tRPC`), generate clients.\n- p95 `≤ 300 ms` at load; `≤ 1 s` for cold authenticated read.\n- Lists paginate (`cursor` once writes are concurrent).\n- Errors carry stable `code`, human `message`, and `request_id`.\n\n## Decision 4 — Data ownership\n\nOne writer per table; reads go through the owner's API, never shared connections.\n- Multi-tenant rows carry `tenant_id` with row-level security.\n- Migrations are expand\u002Fcontract across two deploys, never one.\n\n## Decision 5 — Trust boundaries\n\nAuthenticate at edge, authorise on server with facts server owns — never trust client claims.\n- Cookies: `httpOnly`, `Secure`, `SameSite=Lax`, rotating refresh.\n- Mutations are CSRF- or token-protected; `GET` never mutates.\n- Secrets live in the platform store, rotated.\n\n## Decision 6 — Delivery\n\nDeploy is not release: ship behind a flag, monitor error rate, ramp 1% → 10% → 50% → 100%.\n- Rollback is one rehearsed command.\n- Error budget 99.9% monthly governs whether features ship.\n- Logs, metrics and traces share one `request_id`.\n\n## Rules that hold across every branch\n\n1. **One owner per dataset** — one service writes it; others read through it.\n2. **Contracts before code** — API shape, schema, component API are artefacts.\n3. **State has one home** — no second copy, anywhere.\n4. **Never downgrade a startup to a static mock** — require persistence and API contracts.\n5. **Failure states are designed** — loading, empty, error, partial.\n6. **Authorisation is server-side**, from facts the server owns.\n7. **Nothing ships without a rollback**; flags separate deploy from release.\n8. **Observability precedes launch** — one correlation id across services.\n\n## Architecture review questions\n\n1. What renders each page, and where does its data come from?\n2. Which service owns each write, and what enforces it?\n3. What is cached, for how long, invalidated how?\n4. Who can call each endpoint, and where is that decided?\n5. How does a change reach production, and how is it undone?\n\n## Failure modes at scale\n\n- Downgrading a startup request to a client-only static HTML mock with no real persistence.\n- The frontend owning business rules because the API was never designed.\n- The database becoming the integration layer; services reading each other's tables.\n- Lack of reversibility: deploys, migrations and schema going one way.\n\n## Verification receipts\n\n1. Diagram naming services, stores, boundaries, and owning branches.\n2. `LCP ≤ 2.5 s`, `INP ≤ 200 ms`, `CLS ≤ 0.1` at p75 on throttled mobile.\n3. p95 API latency per endpoint at expected load from a load test.\n4. Automated test suite verifying persistence and API contract coverage.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":29},{"crusor-path":5,"crusor-domain":5,"crusor-origin":25,"crusor-sources":26,"crusor-triggers":27,"crusor-verified-on":28},"original","web.dev; MDN; OWASP ASVS; 12factor.net","website, web app, web product, web service, full stack, web architecture, startup, platform, ecommerce, e-commerce, amazon","2026-10-30","Framework-agnostic; any web stack","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill website-architect",{"tool":43,"command":44},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill website-architect",{"tool":46,"command":47},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill website-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",2645,"https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002FREADME.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"VERIFICATION.md",6159,"https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002FVERIFICATION.md",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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.","MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]