[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SN8P3DBEZ86GC81FTASE8":3,"skill-same:01M79SN8P3DBEZ86GC81FTASE8":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},"01M79SN8P3DBEZ86GC81FTASE8","data-api-architect",null,"Architect-level design of data-serving APIs — query patterns and pre-aggregation, caching and freshness, pagination and export endpoints, row-level authorisation, and the cost controls that stop a dashboard API from scanning a warehouse on every request. Use when applications or partners consume analytical data.","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\u002Fdata-engineering-architect\u002Fdelivery-architect\u002Fdata-api-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-api-architect\ndescription: Architect-level design of data-serving APIs — query patterns and pre-aggregation, caching and freshness, pagination and export endpoints, row-level authorisation, and the cost controls that stop a dashboard API from scanning a warehouse on every request. Use when applications or partners consume analytical data.\nlicense: MIT\ncompatibility: Any warehouse; GraphQL\u002FREST; Cube, Hasura, custom services\nmetadata:\n  crusor-domain: data-engineering-architect\n  crusor-path: data-engineering-architect\u002Fdelivery-architect\u002Fdata-api-architect\n  crusor-origin: original\n  crusor-sources: \"cube.dev\u002Fdocs; hasura.io\u002Fdocs; cloud.google.com\u002Fbigquery\u002Fdocs\u002Fbest-practices-costs\"\n  crusor-triggers: \"data api, analytics api, export endpoint, query caching, pagination, row level security, partner data feed, serving analytics, expose analytics, embedded dashboard, partner feed\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Data API Architect\n\nA data API is **a warehouse query behind an HTTP contract**. Without pre-aggregation\nand caching, one dashboard refresh becomes a scan you pay for.\n\n## When to use\n\n- Applications, partners, or customers consume analytical data.\n- A dashboard product needs an API for embedding.\n- Reports must be exported programmatically.\n\n## When NOT to use\n\n- Internal analysts can query the warehouse directly.\n- The data is transactional and belongs in a service API.\n\n## Decision 1 — Query shape\n\n| Access pattern | Design |\n|---|---|\n| fixed dashboards | pre-aggregated tables or materialised views |\n| parameterised slices | curated dimensions, mandatory filters |\n| ad-hoc SQL from users | do not expose; offer a fixed query surface |\n| large exports | asynchronous job + signed URL |\n| single record lookup | serving store, not the warehouse |\n\n- The API should expose metrics and dimensions, not \"run this SQL\".\n- Enforce required filters (date range, tenant) at the API boundary, not in docs.\n\n## Decision 2 — Caching and freshness\n\n- Cache per (metric, dimensions, filters) with a TTL matched to the data cadence.\n- Return `generated_at` and data freshness in every response — consumers must know\n  how stale it is.\n- Invalidate on model rebuild rather than waiting for TTL where possible.\n- Warm the cache for top dashboards after a refresh; cold cache at 09:00 is a latency\n  cliff.\n\n## Decision 3 — Cost controls\n\n- Per-tenant query budgets and rate limits.\n- Reject unbounded date ranges; cap result rows.\n- Prefer pre-aggregated marts over live joins on raw events.\n- Monitor bytes scanned per endpoint; a single endpoint dominating cost is a design\n  smell.\n\n## Decision 4 — Authorisation\n\n- Row-level filters derived from the caller's identity, applied server-side in the\n  generated query — never trusted from parameters.\n- Column visibility per role: PII hidden unless explicitly granted.\n- Tenant isolation tested as a first-class case.\n- Audit log per request: who, what slice, how many rows.\n\n## Decision 5 — Pagination and exports\n\n- Keyset pagination for large result sets; offset pagination degrades at scale.\n- Exports as async jobs with a status endpoint and a signed, expiring URL.\n- Cap export size and rate; an unbounded export is a scan plus an egress bill.\n- Provide stable column names and a versioned response contract.\n\n## Failure modes at scale\n\n- API hits the warehouse on every page load; latency 4 s and cost unbounded.\n- Row-level filter taken from a request parameter; one tenant reads another's data.\n- Offset pagination on 5M rows; late pages time out.\n- Exports run synchronously; the gateway times out and users retry, doubling load.\n- No freshness metadata; consumers assume real-time.\n\n## Verification receipts\n\n1. Endpoint inventory with the query shape and required filters.\n2. Cache design with TTLs and hit-rate measurement.\n3. Row-level authorisation test across two tenants.\n4. Export job exercised end to end with an expiring URL.\n5. Cost per 1,000 requests and the bytes-scanned report per endpoint.\n","# Data API Architect\n\nA data API is **a warehouse query behind an HTTP contract**. Without pre-aggregation\nand caching, one dashboard refresh becomes a scan you pay for.\n\n## When to use\n\n- Applications, partners, or customers consume analytical data.\n- A dashboard product needs an API for embedding.\n- Reports must be exported programmatically.\n\n## When NOT to use\n\n- Internal analysts can query the warehouse directly.\n- The data is transactional and belongs in a service API.\n\n## Decision 1 — Query shape\n\n| Access pattern | Design |\n|---|---|\n| fixed dashboards | pre-aggregated tables or materialised views |\n| parameterised slices | curated dimensions, mandatory filters |\n| ad-hoc SQL from users | do not expose; offer a fixed query surface |\n| large exports | asynchronous job + signed URL |\n| single record lookup | serving store, not the warehouse |\n\n- The API should expose metrics and dimensions, not \"run this SQL\".\n- Enforce required filters (date range, tenant) at the API boundary, not in docs.\n\n## Decision 2 — Caching and freshness\n\n- Cache per (metric, dimensions, filters) with a TTL matched to the data cadence.\n- Return `generated_at` and data freshness in every response — consumers must know\n  how stale it is.\n- Invalidate on model rebuild rather than waiting for TTL where possible.\n- Warm the cache for top dashboards after a refresh; cold cache at 09:00 is a latency\n  cliff.\n\n## Decision 3 — Cost controls\n\n- Per-tenant query budgets and rate limits.\n- Reject unbounded date ranges; cap result rows.\n- Prefer pre-aggregated marts over live joins on raw events.\n- Monitor bytes scanned per endpoint; a single endpoint dominating cost is a design\n  smell.\n\n## Decision 4 — Authorisation\n\n- Row-level filters derived from the caller's identity, applied server-side in the\n  generated query — never trusted from parameters.\n- Column visibility per role: PII hidden unless explicitly granted.\n- Tenant isolation tested as a first-class case.\n- Audit log per request: who, what slice, how many rows.\n\n## Decision 5 — Pagination and exports\n\n- Keyset pagination for large result sets; offset pagination degrades at scale.\n- Exports as async jobs with a status endpoint and a signed, expiring URL.\n- Cap export size and rate; an unbounded export is a scan plus an egress bill.\n- Provide stable column names and a versioned response contract.\n\n## Failure modes at scale\n\n- API hits the warehouse on every page load; latency 4 s and cost unbounded.\n- Row-level filter taken from a request parameter; one tenant reads another's data.\n- Offset pagination on 5M rows; late pages time out.\n- Exports run synchronously; the gateway times out and users retry, doubling load.\n- No freshness metadata; consumers assume real-time.\n\n## Verification receipts\n\n1. Endpoint inventory with the query shape and required filters.\n2. Cache design with TTLs and hit-rate measurement.\n3. Row-level authorisation test across two tenants.\n4. Export job exercised end to end with an expiring URL.\n5. Cost per 1,000 requests and the bytes-scanned report per endpoint.\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},"data-engineering-architect\u002Fdelivery-architect\u002Fdata-api-architect","data-engineering-architect","original","cube.dev\u002Fdocs; hasura.io\u002Fdocs; cloud.google.com\u002Fbigquery\u002Fdocs\u002Fbest-practices-costs","data api, analytics api, export endpoint, query caching, pagination, row level security, partner data feed, serving analytics, expose analytics, embedded dashboard, partner feed","2026-10-30","Any warehouse; GraphQL\u002FREST; Cube, Hasura, custom services","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdata-engineering-architect\u002Fdelivery-architect\u002Fdata-api-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 data-api-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill data-api-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill data-api-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fdelivery-architect\u002Fdata-api-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",[],[]]