[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TPNXCW2STXJA38TQCFYQR":3,"skill-same:01M79TPNXCW2STXJA38TQCFYQR":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},"01M79TPNXCW2STXJA38TQCFYQR","authz-models-architect",null,"Architect-level authorization modelling — choosing RBAC, ABAC or ReBAC for a domain, where policy is evaluated, relationship and tenant modelling, and the enforcement points that stop privilege escalation across a product. Use when permissions outgrow a boolean on the user row.","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\u002Fwebsite-architect\u002Fsecurity-architect\u002Fauthz-models-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: authz-models-architect\ndescription: Architect-level authorization modelling — choosing RBAC, ABAC or ReBAC for a domain, where policy is evaluated, relationship and tenant modelling, and the enforcement points that stop privilege escalation across a product. Use when permissions outgrow a boolean on the user row.\nlicense: MIT\ncompatibility: Framework-agnostic; policy engines (OPA\u002FCedar) optional\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Fsecurity-architect\u002Fauthz-models-architect\n  crusor-origin: original\n  crusor-sources: \"owasp.org\u002Fwww-project-authorization-cheat-sheet; openpolicyagent.org\u002Fdocs; docs.cerbos.dev\"\n  crusor-triggers: \"rbac, abac, rebac, permissions, roles, policy, fine grained authorization, multi tenant, privilege escalation\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Authorization Models Architect\n\nAuthorization is **a model of the business**, not a table of booleans. Pick the\nmodel the domain actually has, or every new feature becomes a permission patch.\n\n## When to use\n\n- Roles are multiplying, or \"can this user do X\" is answered in five places.\n- Adding teams, sharing, orgs, or multi-tenancy.\n- An authorization bug let someone see another tenant's data.\n\n## When NOT to use\n\n- A two-role internal tool — one enum and a guard is enough, and the model below\n  is over-engineering.\n\n## Decision 1 — Choose the model\n\n| Domain shape | Model |\n|---|---|\n| few global roles (admin, staff, customer) | RBAC |\n| rules over attributes (plan, region, clearance, time) | ABAC |\n| sharing and nested resources (docs, folders, teams) | ReBAC (Zanzibar-style) |\n| per-resource custom permissions | ACL with an owner |\n\n- Mixed domains exist: RBAC for the admin surface, ReBAC for customer content is\n  normal — document which applies where.\n- Roles grant **capabilities**, never specific records. \"editor of document 42\"\n  is a relationship, not a role.\n\n## Decision 2 — Where policy is evaluated\n\n```\nedge\u002Fauthn  → who is this? (session\u002Ftoken)\nservice     → may this subject do this action on this resource?\ndata        → tenant\u002Frow scoping as a second net (RLS, query filters)\n```\n\n- The service layer is where the business rule lives; the database scoping is a\n  backstop, not the only control.\n- Centralise the check in one function\u002Fpolicy module per domain; scattered\n  `if (user.role === 'admin')` is how holes appear.\n- Deny by default; unknown action or resource → deny.\n\n## Decision 3 — Object-level checks\n\n- Every access is `(subject, action, resource)` — all three, never just the\n  subject.\n- Fetch the resource with tenant\u002Fowner scoping in the query itself\n  (`WHERE tenant_id = $1 AND id = $2`), so \"not found\" and \"not yours\" are the\n  same answer.\n- List endpoints filter by the same rule as detail endpoints — the classic leak\n  is a detail check that the list forgets.\n- Batch\u002Fbulk operations check each item, not just the request.\n\n## Decision 4 — Modelling relationships\n\n- Store edges explicitly (memberships, shares) with their own attributes\n  (role on that resource, expiry).\n- Denormalised permission caches must have a rebuild path and an invalidation\n  event.\n- Explicit deny beats allow; delegation has a scope and an expiry.\n- Superadmin is a break-glass path: audited, time-boxed, never a normal role.\n\n## Decision 5 — Policy as code\n\n- Policy files (OPA\u002FCedar\u002Fyour own DSL) live in the repo, are tested like code,\n  and are reviewed by whoever owns the domain.\n- A policy test suite covers: allowed cases, denied cases, cross-tenant cases.\n- Policy changes ship with a decision log entry, not silently.\n\n## Failure modes at scale\n\n- Role explosion: 60 roles because teams needed slightly different access.\n- Authorization in the UI plus a middleware that only checks \"logged in\".\n- Detail endpoint scoped, list endpoint not.\n- Tenant id read from the request body.\n- Permission cache never invalidated after a role change.\n\n## Verification receipts\n\n1. Model documented: which domain uses RBAC\u002FABAC\u002FReBAC and why.\n2. Authorization matrix test per resource × action × subject class.\n3. Cross-tenant test on list **and** detail endpoints.\n4. Policy test suite run in CI.\n5. Audit trail for privileged and denied actions.\n","# Authorization Models Architect\n\nAuthorization is **a model of the business**, not a table of booleans. Pick the\nmodel the domain actually has, or every new feature becomes a permission patch.\n\n## When to use\n\n- Roles are multiplying, or \"can this user do X\" is answered in five places.\n- Adding teams, sharing, orgs, or multi-tenancy.\n- An authorization bug let someone see another tenant's data.\n\n## When NOT to use\n\n- A two-role internal tool — one enum and a guard is enough, and the model below\n  is over-engineering.\n\n## Decision 1 — Choose the model\n\n| Domain shape | Model |\n|---|---|\n| few global roles (admin, staff, customer) | RBAC |\n| rules over attributes (plan, region, clearance, time) | ABAC |\n| sharing and nested resources (docs, folders, teams) | ReBAC (Zanzibar-style) |\n| per-resource custom permissions | ACL with an owner |\n\n- Mixed domains exist: RBAC for the admin surface, ReBAC for customer content is\n  normal — document which applies where.\n- Roles grant **capabilities**, never specific records. \"editor of document 42\"\n  is a relationship, not a role.\n\n## Decision 2 — Where policy is evaluated\n\n```\nedge\u002Fauthn  → who is this? (session\u002Ftoken)\nservice     → may this subject do this action on this resource?\ndata        → tenant\u002Frow scoping as a second net (RLS, query filters)\n```\n\n- The service layer is where the business rule lives; the database scoping is a\n  backstop, not the only control.\n- Centralise the check in one function\u002Fpolicy module per domain; scattered\n  `if (user.role === 'admin')` is how holes appear.\n- Deny by default; unknown action or resource → deny.\n\n## Decision 3 — Object-level checks\n\n- Every access is `(subject, action, resource)` — all three, never just the\n  subject.\n- Fetch the resource with tenant\u002Fowner scoping in the query itself\n  (`WHERE tenant_id = $1 AND id = $2`), so \"not found\" and \"not yours\" are the\n  same answer.\n- List endpoints filter by the same rule as detail endpoints — the classic leak\n  is a detail check that the list forgets.\n- Batch\u002Fbulk operations check each item, not just the request.\n\n## Decision 4 — Modelling relationships\n\n- Store edges explicitly (memberships, shares) with their own attributes\n  (role on that resource, expiry).\n- Denormalised permission caches must have a rebuild path and an invalidation\n  event.\n- Explicit deny beats allow; delegation has a scope and an expiry.\n- Superadmin is a break-glass path: audited, time-boxed, never a normal role.\n\n## Decision 5 — Policy as code\n\n- Policy files (OPA\u002FCedar\u002Fyour own DSL) live in the repo, are tested like code,\n  and are reviewed by whoever owns the domain.\n- A policy test suite covers: allowed cases, denied cases, cross-tenant cases.\n- Policy changes ship with a decision log entry, not silently.\n\n## Failure modes at scale\n\n- Role explosion: 60 roles because teams needed slightly different access.\n- Authorization in the UI plus a middleware that only checks \"logged in\".\n- Detail endpoint scoped, list endpoint not.\n- Tenant id read from the request body.\n- Permission cache never invalidated after a role change.\n\n## Verification receipts\n\n1. Model documented: which domain uses RBAC\u002FABAC\u002FReBAC and why.\n2. Authorization matrix test per resource × action × subject class.\n3. Cross-tenant test on list **and** detail endpoints.\n4. Policy test suite run in CI.\n5. Audit trail for privileged and denied actions.\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},"website-architect\u002Fsecurity-architect\u002Fauthz-models-architect","website-architect","original","owasp.org\u002Fwww-project-authorization-cheat-sheet; openpolicyagent.org\u002Fdocs; docs.cerbos.dev","rbac, abac, rebac, permissions, roles, policy, fine grained authorization, multi tenant, privilege escalation","2026-10-30","Framework-agnostic; policy engines (OPA\u002FCedar) optional","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Fsecurity-architect\u002Fauthz-models-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 authz-models-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill authz-models-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill authz-models-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fsecurity-architect\u002Fauthz-models-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",[],[]]