[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SDDDBFT6897SFAGF7C6RS":3,"skill-same:01M79SDDDBFT6897SFAGF7C6RS":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},"01M79SDDDBFT6897SFAGF7C6RS","ecs-architect",null,"Architect-level container platform design without Kubernetes — ECS\u002FFargate task definitions, service scheduling and placement, ALB integration, secrets and IAM task roles, blue-green deploys with CodeDeploy, and the operational surface a small team can actually run. Use when containers are needed but a full cluster is not.","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\u002Fcompute-architect\u002Fecs-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ecs-architect\ndescription: Architect-level container platform design without Kubernetes — ECS\u002FFargate task definitions, service scheduling and placement, ALB integration, secrets and IAM task roles, blue-green deploys with CodeDeploy, and the operational surface a small team can actually run. Use when containers are needed but a full cluster is not.\nlicense: MIT\ncompatibility: AWS ECS, Fargate; Cloud Run and Azure Container Apps analogues\nmetadata:\n  crusor-domain: cloud-and-devops-architect\n  crusor-path: cloud-and-devops-architect\u002Fcompute-architect\u002Fecs-architect\n  crusor-origin: original\n  crusor-sources: \"docs.aws.amazon.com\u002FAmazonECS\u002Flatest\u002Fdeveloperguide; docs.aws.amazon.com\u002FAmazonECS\u002Flatest\u002Fbestpracticesguide; aws.github.io\u002Fcopilot-cli\"\n  crusor-triggers: \"ecs, fargate, task definition, container service, copilot, aws container, blue green deploy, service discovery, container platform\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# ECS Architect\n\nECS is **a container scheduler with a small surface**. It wins when the team wants\ncontainers, not a cluster to operate — so the design should stay boring.\n\n## When to use\n\n- AWS-native containers without Kubernetes expertise.\n- Small platform team, few services, strong AWS alignment.\n- Batch jobs and scheduled tasks alongside long-running services.\n\n## When NOT to use\n\n- Rich scheduling needs, CRDs, or multi-cloud portability → `kubernetes-architect`.\n- A single container with mild traffic → Cloud Run \u002F App Runner \u002F Lambda container.\n\n## Decision 1 — Fargate or EC2 capacity\n\n| Factor | Fargate | EC2 capacity |\n|---|---|---|\n| ops burden | none | patching, scaling, AMIs |\n| cost at high, steady utilisation | higher | lower |\n| GPU \u002F special hardware | no | yes |\n| daemon-style agents | limited | yes |\n| predictable burst | good | fine with capacity providers |\n\n- Start on Fargate; move to capacity providers when sustained utilisation makes\n  the price difference real.\n\n## Decision 2 — Task definition\n\n- One process per container; a sidecar only for a genuine cross-cutting concern\n  (proxy, log router).\n- CPU\u002Fmemory at task level and container level, sized from measurement.\n- Image by digest, not `latest`; immutable tags in every environment.\n- Secrets from Secrets Manager\u002FSSM via `secrets`, never in environment plaintext.\n- Task role (application permissions) separate from execution role (pull\u002Flog).\n- Health check defined in the task, matching the app's real readiness.\n- Read-only root filesystem where the app allows; non-root user.\n\n## Decision 3 — Services\n\n- Service per deployable; ALB target group per service, path\u002Fhost rules upstream.\n- Deployment: rolling with circuit breaker, or blue-green via CodeDeploy with\n  traffic shifting and automatic rollback on alarms.\n- `desiredCount` across AZs with spread placement; no single-AZ pinning.\n- Service discovery via Cloud Map for internal service-to-service calls.\n- Autoscaling on ALB request count, queue depth, or latency — not CPU alone.\n\n## Decision 4 — Networking\n\n- `awsvpc` mode; private subnets only; egress via NAT or VPC endpoints.\n- Security groups per service, referencing other services' groups.\n- No public IPs on tasks; ingress only through the load balancer.\n\n## Decision 5 — Operations\n\n- Logs to CloudWatch with structured JSON and a retention policy; traces via\n  X-Ray\u002FOTel.\n- Deploy pipeline: build → scan image → push → register task definition → deploy\n  with rollback alarms.\n- Runbook: how to roll back a service, drain a task, and read the last deployment\n  event.\n- Cost: Fargate task size drift is the usual leak — a 4 vCPU task for a 200 ms\n  handler.\n\n## Failure modes at scale\n\n- Task definition with 4 GB memory for a service that needs 512 MB, ×40 services.\n- Secrets in plaintext environment variables visible in the console.\n- `latest` tag deployed; two environments run different code with the same name.\n- No circuit breaker; a failing deploy replaces every task and stays broken.\n- One cluster per service, doubling the operational surface for no isolation gain.\n\n## Verification receipts\n\n1. Task definition inventory: image digest, size, roles, secrets source.\n2. Blue-green deploy demonstrated with automatic rollback on a bad image.\n3. Networking check: no public IP, egress path documented.\n4. Autoscaling policy tested under a synthetic load increase.\n5. Cost per service at current task size, with right-sizing proposals.\n","# ECS Architect\n\nECS is **a container scheduler with a small surface**. It wins when the team wants\ncontainers, not a cluster to operate — so the design should stay boring.\n\n## When to use\n\n- AWS-native containers without Kubernetes expertise.\n- Small platform team, few services, strong AWS alignment.\n- Batch jobs and scheduled tasks alongside long-running services.\n\n## When NOT to use\n\n- Rich scheduling needs, CRDs, or multi-cloud portability → `kubernetes-architect`.\n- A single container with mild traffic → Cloud Run \u002F App Runner \u002F Lambda container.\n\n## Decision 1 — Fargate or EC2 capacity\n\n| Factor | Fargate | EC2 capacity |\n|---|---|---|\n| ops burden | none | patching, scaling, AMIs |\n| cost at high, steady utilisation | higher | lower |\n| GPU \u002F special hardware | no | yes |\n| daemon-style agents | limited | yes |\n| predictable burst | good | fine with capacity providers |\n\n- Start on Fargate; move to capacity providers when sustained utilisation makes\n  the price difference real.\n\n## Decision 2 — Task definition\n\n- One process per container; a sidecar only for a genuine cross-cutting concern\n  (proxy, log router).\n- CPU\u002Fmemory at task level and container level, sized from measurement.\n- Image by digest, not `latest`; immutable tags in every environment.\n- Secrets from Secrets Manager\u002FSSM via `secrets`, never in environment plaintext.\n- Task role (application permissions) separate from execution role (pull\u002Flog).\n- Health check defined in the task, matching the app's real readiness.\n- Read-only root filesystem where the app allows; non-root user.\n\n## Decision 3 — Services\n\n- Service per deployable; ALB target group per service, path\u002Fhost rules upstream.\n- Deployment: rolling with circuit breaker, or blue-green via CodeDeploy with\n  traffic shifting and automatic rollback on alarms.\n- `desiredCount` across AZs with spread placement; no single-AZ pinning.\n- Service discovery via Cloud Map for internal service-to-service calls.\n- Autoscaling on ALB request count, queue depth, or latency — not CPU alone.\n\n## Decision 4 — Networking\n\n- `awsvpc` mode; private subnets only; egress via NAT or VPC endpoints.\n- Security groups per service, referencing other services' groups.\n- No public IPs on tasks; ingress only through the load balancer.\n\n## Decision 5 — Operations\n\n- Logs to CloudWatch with structured JSON and a retention policy; traces via\n  X-Ray\u002FOTel.\n- Deploy pipeline: build → scan image → push → register task definition → deploy\n  with rollback alarms.\n- Runbook: how to roll back a service, drain a task, and read the last deployment\n  event.\n- Cost: Fargate task size drift is the usual leak — a 4 vCPU task for a 200 ms\n  handler.\n\n## Failure modes at scale\n\n- Task definition with 4 GB memory for a service that needs 512 MB, ×40 services.\n- Secrets in plaintext environment variables visible in the console.\n- `latest` tag deployed; two environments run different code with the same name.\n- No circuit breaker; a failing deploy replaces every task and stays broken.\n- One cluster per service, doubling the operational surface for no isolation gain.\n\n## Verification receipts\n\n1. Task definition inventory: image digest, size, roles, secrets source.\n2. Blue-green deploy demonstrated with automatic rollback on a bad image.\n3. Networking check: no public IP, egress path documented.\n4. Autoscaling policy tested under a synthetic load increase.\n5. Cost per service at current task size, with right-sizing proposals.\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},"cloud-and-devops-architect\u002Fcompute-architect\u002Fecs-architect","cloud-and-devops-architect","original","docs.aws.amazon.com\u002FAmazonECS\u002Flatest\u002Fdeveloperguide; docs.aws.amazon.com\u002FAmazonECS\u002Flatest\u002Fbestpracticesguide; aws.github.io\u002Fcopilot-cli","ecs, fargate, task definition, container service, copilot, aws container, blue green deploy, service discovery, container platform","2026-10-30","AWS ECS, Fargate; Cloud Run and Azure Container Apps analogues","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcloud-and-devops-architect\u002Fcompute-architect\u002Fecs-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 ecs-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill ecs-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill ecs-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Fcompute-architect\u002Fecs-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",[],[]]