[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79STHNNE1NRQP07RK7CDX08":3,"skill-same:01M79STHNNE1NRQP07RK7CDX08":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},"01M79STHNNE1NRQP07RK7CDX08","warehouse-architect",null,"Architect-level analytical storage design — warehouse versus lake versus lakehouse, dimensional and wide-table modelling, grain and keys, partitioning and clustering, medallion layering, and the governance that keeps a warehouse from becoming a swamp. Use when designing where analytical data lives and how it is modelled.","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\u002Fwarehouse-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: warehouse-architect\ndescription: Architect-level analytical storage design — warehouse versus lake versus lakehouse, dimensional and wide-table modelling, grain and keys, partitioning and clustering, medallion layering, and the governance that keeps a warehouse from becoming a swamp. Use when designing where analytical data lives and how it is modelled.\nlicense: MIT\ncompatibility: Snowflake, BigQuery, Redshift, Databricks, Iceberg\u002FDelta, DuckDB\nmetadata:\n  crusor-domain: data-engineering-architect\n  crusor-path: data-engineering-architect\u002Fstorage-architect\u002Fwarehouse-architect\n  crusor-origin: original\n  crusor-sources: \"docs.snowflake.com; cloud.google.com\u002Fbigquery\u002Fdocs; iceberg.apache.org; databricks.com\u002Fdiscover\u002Flakehouse\"\n  crusor-triggers: \"data warehouse, data lake, lakehouse, star schema, dimensional model, snowflake, bigquery, iceberg, partitioning, medallion, analytical model\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Warehouse Architect\n\nAnalytical storage is **a product with consumers**, not a bucket. The design\nquestions are grain, ownership, and what a query costs.\n\n## When to use\n\n- Choosing warehouse\u002Flake\u002Flakehouse for analytics, BI, or ML features.\n- A warehouse is slow, expensive, or full of near-duplicate tables.\n- Defining layers (raw\u002Fsilver\u002Fgold) and modelling conventions.\n\n## When NOT to use\n\n- OLTP schema design for an application → `website-architect\u002Fdatabase-*`.\n- A single team's one-off analysis — a notebook and a temporary table.\n\n## Decision 1 — Warehouse, lake, or lakehouse\n\n| Need | Choice |\n|---|---|\n| SQL BI, governed, moderate volume | warehouse |\n| cheap bulk storage, many formats, ML | lake with table format |\n| BI and ML on the same data | lakehouse (Iceberg\u002FDelta) |\n| local analysis, \u003C100 GB | DuckDB or a warehouse free tier |\n\n- Storage and compute separation is now table stakes; choose on ecosystem and\n  governance, not on the brochure.\n- Open table formats buy you exit rights — worth real money at scale.\n\n## Decision 2 — Layers\n\n```\nraw\u002Fbronze   append-only, source-shaped, immutable\nsilver       cleaned, typed, deduplicated, conformed keys\ngold         modelled, metric-ready, one row per grain\n```\n\n- Silver is where business keys are conformed — the highest-leverage layer and the\n  one teams skip.\n- Gold tables have a declared grain and an owner. If nobody owns it, it dies\n  slowly and expensively.\n- Do not let consumers read raw. That is how two teams compute two truths.\n\n## Decision 3 — Modelling\n\n- **Dimensional (star)** — facts at a declared grain, conformed dimensions;\n  best for BI and stable metrics.\n- **Wide\u002FOBT** — one big denormalised table per mart; fast to build, cheap to\n  query, expensive to change.\n- **Data Vault** — auditable hubs\u002Flinks\u002Fsatellites; heavy, justified by regulation\n  and many sources.\n- State the grain in the table name or docs (`fact_order_line`, not `orders_data`).\n\n## Decision 4 — Physical layout\n\n- Partition on the dominant filter (usually date); cluster\u002Fsort on the next most\n  selective.\n- Small partitions create overhead; huge partitions defeat pruning.\n- Pre-aggregate where BI re-computes the same rollup thousands of times.\n- Materialised views\u002Fstreams for recurring transforms; watch refresh cost.\n- Sort and compact small files — the most common silent cost in lakehouses.\n\n## Decision 5 — Governance\n\n- Schemas per domain, not per person; naming conventions enforced by CI.\n- PII tagged at the column level; masking policies follow the tag.\n- Retention per table, automated, not remembered.\n- Cost attribution by warehouse\u002Frole + query tags, reviewed monthly.\n- Deprecation is a process: mark, announce, freeze, drop.\n\n## Failure modes at scale\n\n- Three tables named `users`, `users_v2`, `users_final`, all queried.\n- Gold tables with no grain: joins that fan out silently and inflate revenue.\n- Partitioning by ingestion date while everyone filters on event date.\n- Storage cost grows from copies of copies, each labelled a \"backup\".\n- Nobody knows which dashboard depends on which table, so nothing is removable.\n\n## Verification receipts\n\n1. Layer diagram with owners and allowed readers per layer.\n2. Grain documented for every gold table; fan-out test on a join.\n3. Query plan showing partition pruning on a typical BI query.\n4. Cost report by warehouse\u002Frole for the last month.\n5. Deprecation list with consumers mapped and dates agreed.\n","# Warehouse Architect\n\nAnalytical storage is **a product with consumers**, not a bucket. The design\nquestions are grain, ownership, and what a query costs.\n\n## When to use\n\n- Choosing warehouse\u002Flake\u002Flakehouse for analytics, BI, or ML features.\n- A warehouse is slow, expensive, or full of near-duplicate tables.\n- Defining layers (raw\u002Fsilver\u002Fgold) and modelling conventions.\n\n## When NOT to use\n\n- OLTP schema design for an application → `website-architect\u002Fdatabase-*`.\n- A single team's one-off analysis — a notebook and a temporary table.\n\n## Decision 1 — Warehouse, lake, or lakehouse\n\n| Need | Choice |\n|---|---|\n| SQL BI, governed, moderate volume | warehouse |\n| cheap bulk storage, many formats, ML | lake with table format |\n| BI and ML on the same data | lakehouse (Iceberg\u002FDelta) |\n| local analysis, \u003C100 GB | DuckDB or a warehouse free tier |\n\n- Storage and compute separation is now table stakes; choose on ecosystem and\n  governance, not on the brochure.\n- Open table formats buy you exit rights — worth real money at scale.\n\n## Decision 2 — Layers\n\n```\nraw\u002Fbronze   append-only, source-shaped, immutable\nsilver       cleaned, typed, deduplicated, conformed keys\ngold         modelled, metric-ready, one row per grain\n```\n\n- Silver is where business keys are conformed — the highest-leverage layer and the\n  one teams skip.\n- Gold tables have a declared grain and an owner. If nobody owns it, it dies\n  slowly and expensively.\n- Do not let consumers read raw. That is how two teams compute two truths.\n\n## Decision 3 — Modelling\n\n- **Dimensional (star)** — facts at a declared grain, conformed dimensions;\n  best for BI and stable metrics.\n- **Wide\u002FOBT** — one big denormalised table per mart; fast to build, cheap to\n  query, expensive to change.\n- **Data Vault** — auditable hubs\u002Flinks\u002Fsatellites; heavy, justified by regulation\n  and many sources.\n- State the grain in the table name or docs (`fact_order_line`, not `orders_data`).\n\n## Decision 4 — Physical layout\n\n- Partition on the dominant filter (usually date); cluster\u002Fsort on the next most\n  selective.\n- Small partitions create overhead; huge partitions defeat pruning.\n- Pre-aggregate where BI re-computes the same rollup thousands of times.\n- Materialised views\u002Fstreams for recurring transforms; watch refresh cost.\n- Sort and compact small files — the most common silent cost in lakehouses.\n\n## Decision 5 — Governance\n\n- Schemas per domain, not per person; naming conventions enforced by CI.\n- PII tagged at the column level; masking policies follow the tag.\n- Retention per table, automated, not remembered.\n- Cost attribution by warehouse\u002Frole + query tags, reviewed monthly.\n- Deprecation is a process: mark, announce, freeze, drop.\n\n## Failure modes at scale\n\n- Three tables named `users`, `users_v2`, `users_final`, all queried.\n- Gold tables with no grain: joins that fan out silently and inflate revenue.\n- Partitioning by ingestion date while everyone filters on event date.\n- Storage cost grows from copies of copies, each labelled a \"backup\".\n- Nobody knows which dashboard depends on which table, so nothing is removable.\n\n## Verification receipts\n\n1. Layer diagram with owners and allowed readers per layer.\n2. Grain documented for every gold table; fan-out test on a join.\n3. Query plan showing partition pruning on a typical BI query.\n4. Cost report by warehouse\u002Frole for the last month.\n5. Deprecation list with consumers mapped and dates agreed.\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\u002Fwarehouse-architect","data-engineering-architect","original","docs.snowflake.com; cloud.google.com\u002Fbigquery\u002Fdocs; iceberg.apache.org; databricks.com\u002Fdiscover\u002Flakehouse","data warehouse, data lake, lakehouse, star schema, dimensional model, snowflake, bigquery, iceberg, partitioning, medallion, analytical model","2026-10-30","Snowflake, BigQuery, Redshift, Databricks, Iceberg\u002FDelta, DuckDB","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdata-engineering-architect\u002Fstorage-architect\u002Fwarehouse-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 warehouse-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill warehouse-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill warehouse-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fstorage-architect\u002Fwarehouse-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",[],[]]