[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SCRK1FFV8KQ4KWS749CWD":3,"skill-same:01M79SCRK1FFV8KQ4KWS749CWD":51},{"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},"01M79SCRK1FFV8KQ4KWS749CWD","cloud-and-devops-architect",null,"Architect-level cloud direction — choosing provider services from operational reality, environment and account topology, infrastructure-as-code ownership, network and identity boundaries, reliability targets, and the cost model a system is designed against. Use before any provider, orchestration or IaC skill.","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\u002Fcloud-and-devops-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-and-devops-architect\ndescription: Architect-level cloud direction — choosing provider services from operational reality, environment and account topology, infrastructure-as-code ownership, network and identity boundaries, reliability targets, and the cost model a system is designed against. Use before any provider, orchestration or IaC skill.\nlicense: MIT\ncompatibility: AWS\u002FGCP\u002FAzure; Kubernetes; Terraform or Pulumi\nmetadata:\n  crusor-domain: cloud-and-devops-architect\n  crusor-path: cloud-and-devops-architect\n  crusor-origin: original\n  crusor-sources: \"12factor.net; aws.amazon.com\u002Farchitecture\u002Fwell-architected; kubernetes.io\u002Fdocs; developer.hashicorp.com\u002Fterraform\"\n  crusor-triggers: \"cloud architecture, infrastructure, devops, iac, kubernetes, terraform, environments, networking, cloud cost\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Cloud & DevOps Architect\n\nCloud architecture is **renting failure modes**. Every managed service you adopt\nbuys operational simplicity and sells you a new dependency, a new limit, and a\nnew bill.\n\n## When to use\n\n- Standing up or reviewing a cloud estate, or choosing between providers.\n- A cost, reliability or identity problem that has reached architecture level.\n- Any plan that touches networking, IaC, or managed-service selection.\n\n## When NOT to use\n\n- Application-level design questions — that is the website, mobile or data domain.\n- A single-service tweak with no cross-cutting consequence.\n\n## Leaf map\n\nSeven shelves, 35 books.\n\n| Shelf | Books |\n|---|---|\n| `providers-architect\u002F` | `aws` · `gcp` · `azure` · `cloudflare` |\n| `identity-architect\u002F` | `iam` · `multi-account` · `secrets-and-keys` |\n| `networking-architect\u002F` | `vpc-networking` · `dns-and-edge` · `network-security` |\n| `compute-architect\u002F` | `kubernetes` · `serverless` · `ec2` · `ecs` · `lambda` · `autoscaling` |\n| `data-services-architect\u002F` | `object-storage` · `managed-databases` · `messaging` · `caching` |\n| `iac-architect\u002F` | `terraform` · `pulumi` · `cloudformation` · `ansible` |\n| `platform-architect\u002F` | `helm` · `gitops` · `service-mesh` · `kubernetes-security` · `platform-engineering` |\n| `operations-architect\u002F` | `reliability` · `cost-optimization` · `sre-observability` · `chaos-engineering` · `backup-and-dr` · `cloud-incident-response` |\n\nRead this crown, then take the one or two books the decision needs. The shelf\ntells you the axis; the book tells you the trade-off.\n\n## Decision 1 — Topology before services\n\n```\naccounts\u002Fsubscriptions per environment (dev, staging, prod, shared)\n  network per environment (VPC\u002FVNet), private by default\n    workload per bounded context\n      data per owner — never one shared database for everything\n```\n\n- Environments are **isolated by account**, not by naming convention.\n- Blast radius is a design input: what fails together should be grouped\n  together, and production must not share a control plane with staging.\n- One region until a documented requirement forces multi-region; multi-region\n  multiplies every consistency decision.\n\n## Decision 2 — Managed vs self-run\n\n| Situation | Choose |\n|---|---|\n| commodity (queues, object storage, DNS) | managed |\n| undifferentiated but operationally risky (Kafka, Postgres at scale) | managed first |\n| core differentiator, hard constraints | self-run, with an owner |\n\n- Every self-run component needs an owner, a runbook, and an upgrade path.\n- Managed services still need limits knowledge: quotas, throttles, regional\n  availability, and the pricing cliff.\n\n## Decision 3 — Infrastructure as code, always\n\n- No console changes in production; drift is detected and reverted.\n- State is remote, locked, and per environment; state contains secrets, so it is\n  access-controlled.\n- Modules are versioned and consumed by reference, not copy-paste.\n- Plan output is reviewed like code; apply happens in the pipeline.\n\n## Decision 4 — Identity and network boundaries\n\n- Workloads authenticate with roles\u002Fworkload identity, never static keys.\n- Least privilege per service: each has its own identity and its own policy.\n- Private subnets for data and internal services; public only where required\n  (load balancer, CDN edge).\n- Egress is controlled: an allow-list beats an open NAT for both security and\n  cost.\n- Secrets in a managed secret store with rotation (see\n  `secrets-management-architect`).\n\n## Decision 5 — Reliability targets\n\n- Define SLIs\u002FSLOs per user journey before choosing redundancy.\n- Single-AZ by default, multi-AZ for anything with an SLO above 99.9%.\n- Backups: automated, encrypted, restore-tested; RPO\u002FRTO written down.\n- Chaos is scheduled: kill an instance, drain a zone, expire a credential.\n\n## Decision 6 — Cost is architecture\n\n- Tag everything (service, environment, owner) from day one; untagged spend\n  cannot be attributed.\n- Budgets and alerts per environment; anomaly detection on.\n- The expensive patterns are predictable: idle clusters, cross-AZ chatter,\n  unbounded logs, over-provisioned instances, storage never deleted.\n\n## Failure modes at scale\n\n- Console changes that IaC later reverts or duplicates.\n- One account for everything; a staging mistake reaches production credentials.\n- Static access keys in CI.\n- Multi-region \"for safety\" with no failover test.\n- Costs discovered at the end of the quarter, untagged and unattributable.\n\n## Verification receipts\n\n1. Account\u002Fenvironment diagram with network and identity boundaries.\n2. IaC plan\u002Fdrift report clean; no manual production changes in the last period.\n3. IAM review: per-workload roles, no long-lived keys.\n4. Restore drill with measured RTO; failover drill if multi-AZ\u002Fregion claimed.\n5. Cost report by tag with budget alerts active.\n","# Cloud & DevOps Architect\n\nCloud architecture is **renting failure modes**. Every managed service you adopt\nbuys operational simplicity and sells you a new dependency, a new limit, and a\nnew bill.\n\n## When to use\n\n- Standing up or reviewing a cloud estate, or choosing between providers.\n- A cost, reliability or identity problem that has reached architecture level.\n- Any plan that touches networking, IaC, or managed-service selection.\n\n## When NOT to use\n\n- Application-level design questions — that is the website, mobile or data domain.\n- A single-service tweak with no cross-cutting consequence.\n\n## Leaf map\n\nSeven shelves, 35 books.\n\n| Shelf | Books |\n|---|---|\n| `providers-architect\u002F` | `aws` · `gcp` · `azure` · `cloudflare` |\n| `identity-architect\u002F` | `iam` · `multi-account` · `secrets-and-keys` |\n| `networking-architect\u002F` | `vpc-networking` · `dns-and-edge` · `network-security` |\n| `compute-architect\u002F` | `kubernetes` · `serverless` · `ec2` · `ecs` · `lambda` · `autoscaling` |\n| `data-services-architect\u002F` | `object-storage` · `managed-databases` · `messaging` · `caching` |\n| `iac-architect\u002F` | `terraform` · `pulumi` · `cloudformation` · `ansible` |\n| `platform-architect\u002F` | `helm` · `gitops` · `service-mesh` · `kubernetes-security` · `platform-engineering` |\n| `operations-architect\u002F` | `reliability` · `cost-optimization` · `sre-observability` · `chaos-engineering` · `backup-and-dr` · `cloud-incident-response` |\n\nRead this crown, then take the one or two books the decision needs. The shelf\ntells you the axis; the book tells you the trade-off.\n\n## Decision 1 — Topology before services\n\n```\naccounts\u002Fsubscriptions per environment (dev, staging, prod, shared)\n  network per environment (VPC\u002FVNet), private by default\n    workload per bounded context\n      data per owner — never one shared database for everything\n```\n\n- Environments are **isolated by account**, not by naming convention.\n- Blast radius is a design input: what fails together should be grouped\n  together, and production must not share a control plane with staging.\n- One region until a documented requirement forces multi-region; multi-region\n  multiplies every consistency decision.\n\n## Decision 2 — Managed vs self-run\n\n| Situation | Choose |\n|---|---|\n| commodity (queues, object storage, DNS) | managed |\n| undifferentiated but operationally risky (Kafka, Postgres at scale) | managed first |\n| core differentiator, hard constraints | self-run, with an owner |\n\n- Every self-run component needs an owner, a runbook, and an upgrade path.\n- Managed services still need limits knowledge: quotas, throttles, regional\n  availability, and the pricing cliff.\n\n## Decision 3 — Infrastructure as code, always\n\n- No console changes in production; drift is detected and reverted.\n- State is remote, locked, and per environment; state contains secrets, so it is\n  access-controlled.\n- Modules are versioned and consumed by reference, not copy-paste.\n- Plan output is reviewed like code; apply happens in the pipeline.\n\n## Decision 4 — Identity and network boundaries\n\n- Workloads authenticate with roles\u002Fworkload identity, never static keys.\n- Least privilege per service: each has its own identity and its own policy.\n- Private subnets for data and internal services; public only where required\n  (load balancer, CDN edge).\n- Egress is controlled: an allow-list beats an open NAT for both security and\n  cost.\n- Secrets in a managed secret store with rotation (see\n  `secrets-management-architect`).\n\n## Decision 5 — Reliability targets\n\n- Define SLIs\u002FSLOs per user journey before choosing redundancy.\n- Single-AZ by default, multi-AZ for anything with an SLO above 99.9%.\n- Backups: automated, encrypted, restore-tested; RPO\u002FRTO written down.\n- Chaos is scheduled: kill an instance, drain a zone, expire a credential.\n\n## Decision 6 — Cost is architecture\n\n- Tag everything (service, environment, owner) from day one; untagged spend\n  cannot be attributed.\n- Budgets and alerts per environment; anomaly detection on.\n- The expensive patterns are predictable: idle clusters, cross-AZ chatter,\n  unbounded logs, over-provisioned instances, storage never deleted.\n\n## Failure modes at scale\n\n- Console changes that IaC later reverts or duplicates.\n- One account for everything; a staging mistake reaches production credentials.\n- Static access keys in CI.\n- Multi-region \"for safety\" with no failover test.\n- Costs discovered at the end of the quarter, untagged and unattributable.\n\n## Verification receipts\n\n1. Account\u002Fenvironment diagram with network and identity boundaries.\n2. IaC plan\u002Fdrift report clean; no manual production changes in the last period.\n3. IAM review: per-workload roles, no long-lived keys.\n4. Restore drill with measured RTO; failover drill if multi-AZ\u002Fregion claimed.\n5. Cost report by tag with budget alerts active.\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","12factor.net; aws.amazon.com\u002Farchitecture\u002Fwell-architected; kubernetes.io\u002Fdocs; developer.hashicorp.com\u002Fterraform","cloud architecture, infrastructure, devops, iac, kubernetes, terraform, environments, networking, cloud cost","2026-10-30","AWS\u002FGCP\u002FAzure; Kubernetes; Terraform or Pulumi","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcloud-and-devops-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 cloud-and-devops-architect",{"tool":43,"command":44},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill cloud-and-devops-architect",{"tool":46,"command":47},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill cloud-and-devops-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]