Results for “custom-permissions”

acl-permission-system

Simulator.Company access-control specialist — who can view/modify/remove/sign/execute an object (actor, form, account, template, tree layer). Use when the user wants to share or unshare an object, grant or revoke permissions, list who has access, or bulk-share. Activate when the user says "share this with", "give access to", "grant permission", "revoke access", "who can see/edit this", "set permissions", "make read-only", "поділись з", "надай доступ", "забери доступ", "хто має доступ", "права доступу", "дай доступ", "открой доступ", "отзови доступ", "кто имеет доступ", "права доступа". Also activate when a tool fails because the caller has NO access to an object — "request access", "I can't see this actor", "access denied", "403", "no permission", "запроси доступ", "немає доступу", "немає прав", "відмовлено в доступі", "запроси доступ", "нет доступа", "доступ запрещён". For the object's own data use the domain skill (`simulator-actors` / `simulator-forms` / `simulator-finance`).

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.

WordPress capabilities and roles — add_role, remove_role, add_cap, remove_cap, current_user_can, user_can, WP_Roles, custom capabilities, administrator editor author contributor subscriber, capability mapping, meta capabilities, map_meta_cap, register_post_type capabilities, custom post type capabilities, WP_User roles and caps, ACF field group visibility by role. Invoke for: custom roles, multi-role sites, restrict content by capability, map_meta_cap, "hide ACF field from role", "register capability for CPT".

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

Scaffolds VS Code custom agent files (.agent.md) with YAML frontmatter, tool configuration, handoffs, and instructions for specialized AI personas.

Use when the user wants to start tracking a local custom instruction file (like .agy/ANTIGRAVITY.md or .github/copilot-instructions.md) in SuperCtx. Requires a path argument.

Use when implementing login, registration, session handling, protected routes, or role-based access.

Use when a user asks to mine or update a private, evidence-backed work profile from local Claude Code, Codex, Copilot CLI, or OpenCode sessions.

Use when a user asks to mine or update a private, evidence-backed work profile from local Claude Code, Codex, Copilot CLI, or OpenCode sessions.

Documents MariaDB-specific GRANT behavior, including privilege scope levels, implicit account creation, MariaDB-only privileges, roles, proxy grants, resource limits, and TLS options, to help write accurate GRANT statements.

Use when the team needs authentication, identity providers, custom claims, session strategy, or permission design for a Firebase-backed app. Trigger on requests to design or review Firebase Auth architecture.

Delegate coding tasks to the Claude Code CLI via terminal commands, supporting both one-shot and interactive sessions.

飞书/Lark CLI 共享基础：应用配置初始化、认证登录（auth login）、身份切换（--as user/bot）、权限与 scope 管理、Permission denied 错误处理、安全规则。当用户需要第一次配置(`lark-cli config init`)、使用登录授权(`lark-cli auth login`)、遇到权限不足、切换 user/bot 身份、配置 scope、或首次使用 lark-cli 时触发。

Decide whether Git submodules are the right boundary for external dependencies, then execute the appropriate workflow: add and pin, bootstrap recursively, sync to a recorded commit, advance a tracked branch, edit inside a submodule without detached-HEAD surprises, remove cleanly, or configure CI checkout constraints.

Architects, reviews, and scales backend systems with structured blueprints, trade-off analysis, and audit reports.

Design and deploy Salesforce restriction rules to subtract record access from users, covering eligibility, criteria syntax, metadata shape, and documented enforcement gaps.

Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.

Tailor the IP-LEGAL sub-plugin to one organization by capturing its risk tolerance, jurisdictions, and default playbook positions.