用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hasinhayder/tyro --skill tyro命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | tyro |
| version | 1.0.0 |
| description | Framework-maintainer skill for the Tyro Laravel authorization package |
This skill provides engineering rules for maintaining and extending Tyro, a reusable Laravel authorization framework providing role-based access control (RBAC), permissions, privileges, suspensions, authorization caching, audit logging, and Artisan tooling.
Tyro is the authorization layer of the Tyro ecosystem. Related packages (Tyro Login, Tyro Dashboard) depend on Tyro's public APIs.
This skill treats every rule as a framework contract. Changes must preserve backward compatibility, avoid privilege escalation, and follow established conventions.
Activate this skill when working on:
src/config/tyro.phpdatabase/migrations/database/seeders/tests/HasinHayder\Tyro\ namespaceBefore introducing any new pattern, check whether an established convention already exists in the Tyro codebase.
HasinHayder\Tyro namespace, PSR-4 autoloading)tyro:{entity}-{action}, tyro:sys-{action}, tyro:auth-{action}){entity}.{action} dot notation for audit events)tyro:user-{userId}:roles, tyro:user-{userId}:privileges)Consistency is more important than theoretical perfection.
| Concern | Rule File |
|---|---|
| Package structure, dependency direction | rules/architecture.md |
| Authorization contracts, services, boundaries | rules/authorization.md |
| Permission registration, naming, lifecycle | rules/permissions.md |
| Role registration, assignment, hierarchy | rules/roles.md |
| System-level privileges, break-glass access | rules/privileges.md |
| User/role/permission/tenant suspensions | rules/suspensions.md |
| Role/permission/privilege inheritance | rules/inheritance.md |
| Resolution pipelines, conflict handling | rules/permission-resolution.md |
| Policy integration, discovery, boundaries | rules/policies.md |
| Public/internal APIs, REST endpoints, versioning | rules/api-design.md |
| Command architecture, naming, UX, safety | rules/artisan-commands.md |
| Audit logging, immutable trails, compliance | rules/audit-logs.md |
| Permission/role/event/command/cache naming | rules/naming-conventions.md |
| Tenant isolation, scoped permissions | rules/multi-tenancy.md |
| Cache invalidation, warming, consistency | rules/caching.md |
| Privilege escalation prevention, secure defaults | rules/security.md |
| Role/permission/privilege/suspension/cache events | rules/events.md |
| Package, cache, driver, tenant configuration | rules/configuration.md |
| Custom providers, drivers, resolvers | rules/extensibility.md |
| Permission, authorization, security testing | rules/testing.md |
| Lookup optimization, query tuning, scaling | rules/performance.md |
| Migrations, seeding, synchronization | rules/migrations-seeding.md |
| Public API stability, deprecation, upgrade paths | rules/backward-compatibility.md |
| Public API docs, extension docs, upgrade guides | rules/documentation.md |
| Middleware architecture, resolution, wildcards | rules/middleware.md |
| Blade directives, aliases, registration | rules/blade-directives.md |
| Model conventions, pivots, observers, factories | rules/models.md |
| Error responses, HTTP status codes, exit codes | rules/error-handling.md |
vendor/bin/pestvendor/bin/pint --testEvery rule file follows this structure: