Add authorization methods for a new entity to AuthorizationService. Use after creating a resource service. Triggers on "add permissions", "authorization methods", "entity permissions", "add auth methods".
日本語の概要は準備中です。原文の説明を表示しています。
748 件 ・ 関連度順
概要と使いどころ
Add authorization methods for a new entity to AuthorizationService. Use after creating a resource service. Triggers on "add permissions", "authorization methods", "entity permissions", "add auth methods".
日本語の概要は準備中です。原文の説明を表示しています。
Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit. Use when presenting a privacy-preserving accessory picker, defining discovery descriptors for BLE or Wi-Fi devices, handling accessory session events, migrating from CoreBluetooth permission-based scanning, or setting up accessories without requiring broad Bluetooth permissions.
日本語の概要は準備中です。原文の説明を表示しています。
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Role-Based Access Control (RBAC), permissions management, and authorization policies. Use when building secure access control systems with fine-grained permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with access policies, field access, authorization middleware, gates, route access control, AccessResult semantics, permission handlers, or files in packages/access/, packages/routing/src/AccessChecker.php, packages/user/src/Middleware/. Covers entity-level access (deny-by-default via isAllowed), field-level access (open-by-default via !isForbidden), the Gate system, route options (_public, _permission, _role, _gate), and the SessionMiddleware/AuthorizationMiddleware pipeline in public/index.php.
日本語の概要は準備中です。原文の説明を表示しています。
Implements permission-based authorization with custom attributes, policy providers, and authorization handlers. Provides granular access control beyond simple role-based authorization.
日本語の概要は準備中です。原文の説明を表示しています。
Windows アプリ開発 (Windows App SDK / WinRT) のファイル・設定・データ保存リファレンス。 Windows.Storage の StorageFile, StorageFolder, IStorageItem, FileIO, PathIO, CachedFileManager, DataReader, DataWriter。ApplicationData, ApplicationDataContainer, ApplicationDataCompositeValue によるローカル・ローミング設定。 FileOpenPicker, FileSavePicker, FolderPicker, StorageApplicationPermissions, KnownFolders によるファイルアクセスと権限。JsonObject, JsonArray, XmlDocument, SQLite, EF Core によるシリアライズと永続化。
OpenAI Codex (CLI / IDE / cloud) の公式リファレンス。 codex CLI, codex exec, AGENTS.md, rules, subagents, prompting, approvals, sandbox, permission profiles, auto-review, config.toml, profiles, MCP 設定, 環境変数, GitHub Action, Codex SDK, Agents SDK 連携, cloud 委譲, administration, roles, provisioning, analytics API, compliance API, Codex Security 脆弱性スキャン, deep scan, triage, findings, SARIF export, threat model, security hardening, cloud / local / worktree 環境, git worktrees, Record & Replay, GitHub / Linear / Slack 連携。
Claude Agent SDK (code.claude.com/docs/en/agent-sdk) の TypeScript / Python リファレンス。 query(), ClaudeAgentOptions / Options, custom tools (in-process MCP), createSdkMcpServer, hooks, permissions (canUseTool), subagents, sessions (resume / fork), streaming, structured outputs, slash commands, tool search, hosting / observability。
Claude Managed Agents (platform.claude.com/docs/en/managed-agents) リファレンス。 Agents API, Sessions API, Environments API, SSE event streaming, threads, deployments (cron スケジュール), dreams (メモリ統合), vaults (credentials), memory stores, self-hosted sandboxes, webhooks, multiagent orchestration, user profiles, Agent Skills 添付, MCP connector 接続, permission policies。
LAM ハーネスの規範層をプロジェクトへ敷く初期化スキル。 plugin コンポーネントとして配れない層(.claude/rules/ と docs/internal/ と .claude/scripts/ = managed、 および CLAUDE.md 等の starter)をファイルとして配置し、.claude/harness.json に記録する。 ランタイム(Python)が無い環境では完了を拒む。 Layer 1(.claude/settings.json の permissions)は敷かず、手作業の手順として提示する。 Use when the user installs lam-harness into a project, or runs /lam-harness:init.
Check whether a user may start side work alongside their current job, by reading the employer's own rules and contract clause by clause: whether side work is prohibited, needs prior permission, or only a notification, and which duties the planned side work could touch (non-compete, confidentiality, exclusive attention to the main job, use of company assets and information, combined working hours). Separate what is confirmed in a document from what is hearsay, and produce the questions to ask the employer plus the facts an application or notification will need. Use when someone with a main job is considering side work, freelance or gyomu-itaku work, a second part-time job, or paid trial work for another company, and needs to know what their own employer's rules require first; do not use to rule on whether a clause is lawful or enforceable, to help conceal side work from an employer or avoid filing obligations, to predict whether permission will be granted, or to submit the application or contact the employer.
日本語の概要は準備中です。原文の説明を表示しています。
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.
日本語の概要は準備中です。原文の説明を表示しています。
Generate ABP Application.Contracts layer scaffolding (interfaces, DTOs, permissions) from technical design. Enables parallel development by abp-developer and qa-engineer. Use when: (1) backend-architect needs to generate contracts, (2) preparing for parallel implementation workflow, (3) creating API contracts before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Audit codebases, infrastructure, AND agentic AI systems for security issues. Covers traditional security (dependencies, secrets, OWASP web top 10, SSL/TLS, file permissions) PLUS agentic security (prompt injection scanning, identity spoofing detection, memory poisoning checks, multi-agent communication audit, OWASP Agentic Top 10). Use when scanning for vulnerabilities, detecting hardcoded secrets, reviewing agent workspace configuration, checking prompt injection vectors, or auditing agent permissions and boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision.
日本語の概要は準備中です。原文の説明を表示しています。
Design focused empty states for zero-data, no-results, permission, and error situations with clear value framing, strong CTAs, and less dead chrome. Use when the user mentions blank pages, zero-data screens, no results, permission states, or dead controls—not broader onboarding strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Detect risky OAuth application consent grants in Azure AD / Microsoft Entra ID using Microsoft Graph API, audit logs, and permission analysis to identify illicit consent grant attacks.
日本語の概要は準備中です。原文の説明を表示しています。
Detect AWS IAM privilege escalation paths using boto3 and Cloudsplaining policy analysis to identify overly permissive policies, dangerous permission combinations, and least-privilege violations
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Kubernetes cluster RBAC configurations to identify overly permissive roles, wildcard permissions, dangerous ClusterRoleBindings, service account abuse, and privilege escalation paths using kubectl, rbac-tool, KubiScan, and Kubeaudit.
日本語の概要は準備中です。原文の説明を表示しています。
Creates comprehensive permission tests ensuring RBAC doesn't regress with test matrices, CI gating, and authorization coverage. Use for "RBAC testing", "permission tests", "authorization testing", or "access control tests".
日本語の概要は準備中です。原文の説明を表示しています。
Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.
日本語の概要は準備中です。原文の説明を表示しています。
Runtime enforcement of file system boundaries and tool access restrictions. Blocks unauthorized operations and logs violations. Activate on 'enforce scope', 'access control', 'boundary enforcement', 'tool restrictions', 'runtime security'. NOT for validation (use dag-permission-validator) or isolation management (use dag-isolation-manager).
日本語の概要は準備中です。原文の説明を表示しています。
Cryptographic security for agentic systems — zero-trust agent networking, signed message envelopes (JWS/JWE), capability-based security (ocaps), Merkle tree audit trails, WASM sandboxing, and formal verification. Covers CLI dev tool security, mTLS between agents, permission boundaries (least privilege for AI agents), and supply chain security for skills/plugins. Activate on: "agent security", "zero trust agents", "secure agent communication", "capability-based security", "ocap", "signed messages between agents", "agent audit trail", "sandbox agent execution", "agent permissions", "mTLS agents", "cryptographic verification", "agent supply chain", "OWASP agentic", "prove agent did X", "tamper-proof agent logs". NOT for: application-level SAST scanning (use security-auditor), network firewall rules (use infrastructure), SOC2/HIPAA compliance (organizational), or prompt injection defense (use prompt-engineer).
日本語の概要は準備中です。原文の説明を表示しています。