[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SS7SQF98YJMSBX49RBZWD":3,"skill-same:01M79SS7SQF98YJMSBX49RBZWD":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},"01M79SS7SQF98YJMSBX49RBZWD","bigquery-architect",null,"Architect-level BigQuery design — datasets and project layout, partitioning and clustering that actually prune, slots versus on-demand pricing, materialised views and BI Engine, streaming inserts versus the Storage Write API, and the query patterns that quietly scan terabytes. Use when the warehouse is BigQuery.","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\u002Fstorage-architect\u002Fbigquery-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bigquery-architect\ndescription: Architect-level BigQuery design — datasets and project layout, partitioning and clustering that actually prune, slots versus on-demand pricing, materialised views and BI Engine, streaming inserts versus the Storage Write API, and the query patterns that quietly scan terabytes. Use when the warehouse is BigQuery.\nlicense: MIT\ncompatibility: Google BigQuery\nmetadata:\n  crusor-domain: data-engineering-architect\n  crusor-path: data-engineering-architect\u002Fstorage-architect\u002Fbigquery-architect\n  crusor-origin: original\n  crusor-sources: \"cloud.google.com\u002Fbigquery\u002Fdocs\u002Fpartitioned-tables; cloud.google.com\u002Fbigquery\u002Fdocs\u002Fclustered-tables; cloud.google.com\u002Fbigquery\u002Fpricing\"\n  crusor-triggers: \"bigquery, bq slots, partitioned table, clustering bigquery, on demand pricing, storage write api, bi engine, google warehouse\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# BigQuery Architect\n\nBigQuery charges **per byte scanned** on-demand, or per slot-hour with capacity.\nBoth models make table design the primary cost control.\n\n## When to use\n\n- The analytical store is BigQuery.\n- Query costs are surprising or unpredictable.\n- Choosing between on-demand and slot reservations.\n\n## When NOT to use\n\n- Cross-cloud analytical design → `warehouse-architect`.\n- Transactional workloads — BigQuery is not an OLTP store.\n\n## Decision 1 — Layout\n\n```\norganisation\n  project per environment \u002F business domain\n    dataset per layer: raw_\u003Csource>, silver, gold_marts\n      tables partitioned by date, clustered by high-selectivity column\n```\n\n- Datasets are the access-control and location boundary; choose region once\n  (multi-region costs more, is not always needed).\n- Separate billing projects for ad-hoc analysis so exploratory spend is visible.\n- Table naming: `\u003Clayer>_\u003Cdomain>_\u003Centity>`; undocumented tables become landfill.\n\n## Decision 2 — Physical design\n\n| Technique | Effect |\n|---|---|\n| partition by DATE\u002FTIMESTAMP column | prunes whole days |\n| partition by ingestion time | useful only if you filter on it |\n| clustering (up to 4 cols) | prunes within partitions |\n| `require_partition_filter` | blocks accidental full scans |\n| column types (no wide STRING blobs) | scans are columnar |\n\n- Set `require_partition_filter = true` on large tables — the cheapest guardrail\n  available.\n- Clustering order matters: most selective first.\n- Nested\u002Frepeated fields reduce joins but can hide scan cost; measure.\n\n## Decision 3 — Pricing model\n\n- On-demand: simple, per-TB scanned, good for spiky or small workloads.\n- Slots (autoscaling reservations): better for predictable, high-volume BI.\n- Break-even is roughly total scanned TB\u002Fday versus slot cost; compute it with real\n  numbers rather than intuition.\n- Reservations are per project\u002Fregion; unused committed slots are still billed.\n\n## Decision 4 — Serving patterns\n\n- Materialised views for repeated aggregations; refresh cost is real.\n- BI Engine for dashboard-heavy concurrency.\n- Streaming inserts are for small volumes; Storage Write API for high throughput\n  with exactly-once semantics.\n- Scheduled queries for transforms; dbt or Dataform for managed pipelines.\n\n## Decision 5 — Cost control\n\n- `INFORMATION_SCHEMA.JOBS` by user, project, and bytes billed — review weekly.\n- Guardrails: custom quotas, per-query byte limits, and partitioned table\n  requirements.\n- Kill patterns: `SELECT *` on wide tables, cross joins, unpartitioned\n  self-joins, and dashboards scanning raw events.\n- Cache hits are free; identical queries within 24 h reuse results — design\n  dashboards to hit the cache.\n\n## Failure modes at scale\n\n- No partition filter required; one dashboard scans two years of events hourly.\n- Clustering on a low-cardinality column; no pruning benefit.\n- On-demand pricing with 200 dashboards refreshing every five minutes.\n- Streaming inserts for event data at scale; quota limits and duplicate rows.\n- Ad-hoc exploration billed to the production project, invisible in reports.\n\n## Verification receipts\n\n1. Dataset\u002Fproject layout with locations and access roles.\n2. Bytes-scanned report for the top 20 queries, with fixes identified.\n3. Partition filter enforced on the largest tables, proven by a failed query.\n4. Pricing model decision with the break-even calculation.\n5. Cost alerting on daily scan volume per project.\n","# BigQuery Architect\n\nBigQuery charges **per byte scanned** on-demand, or per slot-hour with capacity.\nBoth models make table design the primary cost control.\n\n## When to use\n\n- The analytical store is BigQuery.\n- Query costs are surprising or unpredictable.\n- Choosing between on-demand and slot reservations.\n\n## When NOT to use\n\n- Cross-cloud analytical design → `warehouse-architect`.\n- Transactional workloads — BigQuery is not an OLTP store.\n\n## Decision 1 — Layout\n\n```\norganisation\n  project per environment \u002F business domain\n    dataset per layer: raw_\u003Csource>, silver, gold_marts\n      tables partitioned by date, clustered by high-selectivity column\n```\n\n- Datasets are the access-control and location boundary; choose region once\n  (multi-region costs more, is not always needed).\n- Separate billing projects for ad-hoc analysis so exploratory spend is visible.\n- Table naming: `\u003Clayer>_\u003Cdomain>_\u003Centity>`; undocumented tables become landfill.\n\n## Decision 2 — Physical design\n\n| Technique | Effect |\n|---|---|\n| partition by DATE\u002FTIMESTAMP column | prunes whole days |\n| partition by ingestion time | useful only if you filter on it |\n| clustering (up to 4 cols) | prunes within partitions |\n| `require_partition_filter` | blocks accidental full scans |\n| column types (no wide STRING blobs) | scans are columnar |\n\n- Set `require_partition_filter = true` on large tables — the cheapest guardrail\n  available.\n- Clustering order matters: most selective first.\n- Nested\u002Frepeated fields reduce joins but can hide scan cost; measure.\n\n## Decision 3 — Pricing model\n\n- On-demand: simple, per-TB scanned, good for spiky or small workloads.\n- Slots (autoscaling reservations): better for predictable, high-volume BI.\n- Break-even is roughly total scanned TB\u002Fday versus slot cost; compute it with real\n  numbers rather than intuition.\n- Reservations are per project\u002Fregion; unused committed slots are still billed.\n\n## Decision 4 — Serving patterns\n\n- Materialised views for repeated aggregations; refresh cost is real.\n- BI Engine for dashboard-heavy concurrency.\n- Streaming inserts are for small volumes; Storage Write API for high throughput\n  with exactly-once semantics.\n- Scheduled queries for transforms; dbt or Dataform for managed pipelines.\n\n## Decision 5 — Cost control\n\n- `INFORMATION_SCHEMA.JOBS` by user, project, and bytes billed — review weekly.\n- Guardrails: custom quotas, per-query byte limits, and partitioned table\n  requirements.\n- Kill patterns: `SELECT *` on wide tables, cross joins, unpartitioned\n  self-joins, and dashboards scanning raw events.\n- Cache hits are free; identical queries within 24 h reuse results — design\n  dashboards to hit the cache.\n\n## Failure modes at scale\n\n- No partition filter required; one dashboard scans two years of events hourly.\n- Clustering on a low-cardinality column; no pruning benefit.\n- On-demand pricing with 200 dashboards refreshing every five minutes.\n- Streaming inserts for event data at scale; quota limits and duplicate rows.\n- Ad-hoc exploration billed to the production project, invisible in reports.\n\n## Verification receipts\n\n1. Dataset\u002Fproject layout with locations and access roles.\n2. Bytes-scanned report for the top 20 queries, with fixes identified.\n3. Partition filter enforced on the largest tables, proven by a failed query.\n4. Pricing model decision with the break-even calculation.\n5. Cost alerting on daily scan volume per project.\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\u002Fstorage-architect\u002Fbigquery-architect","data-engineering-architect","original","cloud.google.com\u002Fbigquery\u002Fdocs\u002Fpartitioned-tables; cloud.google.com\u002Fbigquery\u002Fdocs\u002Fclustered-tables; cloud.google.com\u002Fbigquery\u002Fpricing","bigquery, bq slots, partitioned table, clustering bigquery, on demand pricing, storage write api, bi engine, google warehouse","2026-10-30","Google BigQuery","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdata-engineering-architect\u002Fstorage-architect\u002Fbigquery-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 bigquery-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill bigquery-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill bigquery-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fstorage-architect\u002Fbigquery-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",[],[]]