[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SG2XFTSGJ7WH05DMXF8DX":3,"skill-same:01M79SG2XFTSGJ7WH05DMXF8DX":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},"01M79SG2XFTSGJ7WH05DMXF8DX","iam-architect",null,"Architect-level identity and access design in the cloud — human versus machine identities, role and permission boundaries, federation over keys, least privilege that can actually be maintained, break-glass access, and the audit trail that proves who did what. Use when designing accounts, roles, or service credentials.","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\u002Fidentity-architect\u002Fiam-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: iam-architect\ndescription: Architect-level identity and access design in the cloud — human versus machine identities, role and permission boundaries, federation over keys, least privilege that can actually be maintained, break-glass access, and the audit trail that proves who did what. Use when designing accounts, roles, or service credentials.\nlicense: MIT\ncompatibility: AWS IAM, Entra ID, GCP IAM, any OIDC federation\nmetadata:\n  crusor-domain: cloud-and-devops-architect\n  crusor-path: cloud-and-devops-architect\u002Fidentity-architect\u002Fiam-architect\n  crusor-origin: original\n  crusor-sources: \"docs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide; cloud.google.com\u002Fiam\u002Fdocs\u002Foverview; learn.microsoft.com\u002Fentra\u002Fidentity\"\n  crusor-triggers: \"iam, roles, permissions, least privilege, service account, federation, oidc, break glass, access review, policy boundary\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# IAM Architect\n\nIdentity is **the real perimeter**. Network controls are advisory once a credential\nis stolen; the permission set is what actually limits the damage.\n\n## When to use\n\n- Designing roles for humans and workloads.\n- Choosing between long-lived keys and federation.\n- An audit or incident asks \"who could have done this\".\n\n## When NOT to use\n\n- Application-level authorization (tenant roles, feature access) → web\n  `authz-models-architect`.\n- Secrets storage mechanics → `secrets-management-architect`.\n\n## Decision 1 — Identity classes\n\n| Class | Credential | Lifetime |\n|---|---|---|\n| human, interactive | SSO federation | session, hours |\n| human, privileged | SSO + step-up MFA | minutes |\n| workload in cloud | instance\u002Fworkload identity | automatic, rotated |\n| workload outside cloud | OIDC federation | minutes |\n| CI\u002FCD | OIDC to provider | minutes |\n| break-glass | hardware key, sealed | manual, audited |\n\n- Static access keys are a legacy exception requiring an owner and an expiry date.\n- One identity per workload — shared identities destroy attribution and blast-radius\n  control.\n\n## Decision 2 — Permission shape\n\n- Start from deny; grant by role at the smallest scope that runs the workload.\n- Use **roles with conditions** rather than wildcards: resource tags, source\n  network, MFA presence, time.\n- Permission boundaries \u002F guardrails stop a role from escalating itself — the most\n  important control in any delegated-admin model.\n- Managed policies first, custom only with a documented reason and a review date.\n- Separate planes: control-plane admin (create\u002Fdelete) from data-plane access\n  (read\u002Fwrite). Most humans need neither full-time.\n\n## Decision 3 — Federation\n\n- OIDC for CI: the provider issues short-lived credentials scoped to a repo\u002Fbranch.\n- Verify the token's audience and subject conditions — a permissive trust policy is\n  an open door.\n- Human access via the IdP; no local IAM users with console passwords.\n- Cross-account access by role assumption with an external id, not shared keys.\n\n## Decision 4 — Privileged access\n\n- Break-glass role: no standing access, alert on use, credentials held outside the\n  normal path, and a post-use review.\n- Just-in-time elevation with approval; standing admin is the default failure.\n- Session recording or command logging for production admin.\n- Offboarding is automated from the IdP — a departed human's roles die with the\n  account.\n\n## Decision 5 — Audit\n\n- Every identity action logged to an immutable store, retained per policy.\n- Access reviews quarterly: unused roles, unused permissions, stale keys.\n- Alert on: new admin role, policy attached to a principal, root\u002Fowner login,\n  key creation.\n- Attribution: the log must name the human behind the workload role when possible.\n\n## Failure modes at scale\n\n- One `deploy` role with `*` on `*`, used by every pipeline.\n- Access keys from 2019 still active in a CI secret store.\n- Trust policy accepting any repo in the org, so a fork can assume the role.\n- Break-glass credentials in a shared password manager nobody audits.\n- Hundreds of roles, none removable because \"something might use it\".\n\n## Verification receipts\n\n1. Identity inventory: class, credential type, rotation, owner.\n2. Least-privilege check: unused-permission report with removals applied.\n3. Federation trust policies reviewed for audience\u002Fsubject conditions.\n4. Break-glass use rehearsed and alert verified.\n5. Audit log query demonstrating attribution for a sensitive action.\n","# IAM Architect\n\nIdentity is **the real perimeter**. Network controls are advisory once a credential\nis stolen; the permission set is what actually limits the damage.\n\n## When to use\n\n- Designing roles for humans and workloads.\n- Choosing between long-lived keys and federation.\n- An audit or incident asks \"who could have done this\".\n\n## When NOT to use\n\n- Application-level authorization (tenant roles, feature access) → web\n  `authz-models-architect`.\n- Secrets storage mechanics → `secrets-management-architect`.\n\n## Decision 1 — Identity classes\n\n| Class | Credential | Lifetime |\n|---|---|---|\n| human, interactive | SSO federation | session, hours |\n| human, privileged | SSO + step-up MFA | minutes |\n| workload in cloud | instance\u002Fworkload identity | automatic, rotated |\n| workload outside cloud | OIDC federation | minutes |\n| CI\u002FCD | OIDC to provider | minutes |\n| break-glass | hardware key, sealed | manual, audited |\n\n- Static access keys are a legacy exception requiring an owner and an expiry date.\n- One identity per workload — shared identities destroy attribution and blast-radius\n  control.\n\n## Decision 2 — Permission shape\n\n- Start from deny; grant by role at the smallest scope that runs the workload.\n- Use **roles with conditions** rather than wildcards: resource tags, source\n  network, MFA presence, time.\n- Permission boundaries \u002F guardrails stop a role from escalating itself — the most\n  important control in any delegated-admin model.\n- Managed policies first, custom only with a documented reason and a review date.\n- Separate planes: control-plane admin (create\u002Fdelete) from data-plane access\n  (read\u002Fwrite). Most humans need neither full-time.\n\n## Decision 3 — Federation\n\n- OIDC for CI: the provider issues short-lived credentials scoped to a repo\u002Fbranch.\n- Verify the token's audience and subject conditions — a permissive trust policy is\n  an open door.\n- Human access via the IdP; no local IAM users with console passwords.\n- Cross-account access by role assumption with an external id, not shared keys.\n\n## Decision 4 — Privileged access\n\n- Break-glass role: no standing access, alert on use, credentials held outside the\n  normal path, and a post-use review.\n- Just-in-time elevation with approval; standing admin is the default failure.\n- Session recording or command logging for production admin.\n- Offboarding is automated from the IdP — a departed human's roles die with the\n  account.\n\n## Decision 5 — Audit\n\n- Every identity action logged to an immutable store, retained per policy.\n- Access reviews quarterly: unused roles, unused permissions, stale keys.\n- Alert on: new admin role, policy attached to a principal, root\u002Fowner login,\n  key creation.\n- Attribution: the log must name the human behind the workload role when possible.\n\n## Failure modes at scale\n\n- One `deploy` role with `*` on `*`, used by every pipeline.\n- Access keys from 2019 still active in a CI secret store.\n- Trust policy accepting any repo in the org, so a fork can assume the role.\n- Break-glass credentials in a shared password manager nobody audits.\n- Hundreds of roles, none removable because \"something might use it\".\n\n## Verification receipts\n\n1. Identity inventory: class, credential type, rotation, owner.\n2. Least-privilege check: unused-permission report with removals applied.\n3. Federation trust policies reviewed for audience\u002Fsubject conditions.\n4. Break-glass use rehearsed and alert verified.\n5. Audit log query demonstrating attribution for a sensitive action.\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\u002Fidentity-architect\u002Fiam-architect","cloud-and-devops-architect","original","docs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide; cloud.google.com\u002Fiam\u002Fdocs\u002Foverview; learn.microsoft.com\u002Fentra\u002Fidentity","iam, roles, permissions, least privilege, service account, federation, oidc, break glass, access review, policy boundary","2026-10-30","AWS IAM, Entra ID, GCP IAM, any OIDC federation","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcloud-and-devops-architect\u002Fidentity-architect\u002Fiam-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 iam-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill iam-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill iam-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Fidentity-architect\u002Fiam-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",[],[]]