What problem does it solve?
Adding a new Agent feature requires consistent permission keys and coordinated edits across backend permission catalogs, built-in roles, controllers, frontend menu mappings, route guards, and documentation; this Skill centralizes the decision rules and produces a complete, ordered checklist to avoid mismatches and missing updates.
Core Features & Use Cases
- Decision guidance: Applies the permission classification rules (agent.use, agent.manage, module.read/module.write) based on whether the feature calls LLM/AI and whether it has an independent page.
- Change checklist generation: Identifies exact locations to update including AdminPermissionCatalog.cs, BuiltInSystemRoles.cs, Controller attributes, frontend authzMenuMapping, and App route guards, and composes the required constant names and entries.
- Policy enforcement: Enforces role assignment rules and forbidden patterns (for example, disallowing use of overly broad permissions or mismatched frontend/backend checks).
- Use case: When a developer introduces a new Agent UI, run this Skill to get the permission key, role assignments, code snippets to add, and a verification checklist to complete the integration.
Quick Start
Ask the skill to "add permission" and provide the new agent name, desired permission key, and a short human-readable description and it will return classification, the files to update, and a verification checklist.
