symfony-voters — Claude Code skill: what it does, how to install
The symfony-voters skill guides Symfony Voter authorization work, from mapping access decisions to testing denied cases. Use it to keep permission checks out of duplicated controller logic.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a claude-codeWhat symfony-voters does
The workflow starts by mapping decisions across an actor, a resource and an action. It then places voter or constraint logic at the appropriate boundary and wires checks into controllers and API operations. This gives permission rules a defined home.
The skill calls for tests covering permitted, forbidden and invalid paths. It also says to retain explicit denials for sensitive actions and avoid exposing privileged state in error details. A successful-access test alone misses the cases these safeguards address.
For deeper implementation details, the skill points to reference.md. Its expected work includes security-boundary changes, integration points that enforce decisions and results from negative-path tests.
What it helps with
- separate authorization policy from controller code
- map access decisions for actors, resources and actions
- enforce checks in controllers and API operations
- test permitted, forbidden and invalid access paths
Example prompts for the agent
- Refactor this Symfony access check around Voters; map the actor, resource and action first.
- Wire the authorization rules into the controller and API operation without duplicating policy logic.
- Add tests for permitted, forbidden and invalid authorization paths.
How to install symfony-voters
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a claude-code2Manually: put the files in place
~/.claude/skills/symfony-voters/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/symfony-voters/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a codex2Manually: put the files in place
.agents/skills/symfony-voters/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a cursor2Manually: put the files in place
.cursor/skills/symfony-voters/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/symfony-voters2Manually: put the files in place
.github/skills/symfony-voters/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/symfony-votersManually: put the files in place
.devin/skills/symfony-voters/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about symfony-voters
How do I install symfony-voters in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill symfony-voters -a claude-code. The skill file is at ~/.claude/skills/symfony-voters/SKILL.md.
What does symfony-voters do?
It guides granular authorization with Symfony Voters, including where to enforce decisions and how to test the resulting access paths separately.
Which authorization cases should I test?
Cover permitted, forbidden and invalid paths. Sensitive actions should retain an explicit denial, and error details should not expose privileged state.
Source text
SKILL.md · MIT
--- name: symfony-voters description: Implement granular authorization with Symfony Voters; decouple permission logic from controllers; test authorization separately capabilities: [read, search, edit, shell] tags: [security] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep - Write - Edit - Bash --- # Symfony Voters (Symfony) ## Use when - Hardening access-control or validation boundaries. - Aligning voters/security expressions with domain rules. ## Default workflow 1. Map actor/resource/action decision matrix. 2. Implement voter/constraint logic at the right boundary. 3. Wire checks at controllers and API operations. 4. Test allowed/forbidden/invalid paths comprehensively. ## Guardrails - Avoid policy logic duplication across layers. - Do not leak privileged state via error detail. - Preserve explicit deny behavior for sensitive actions. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - Security boundary updates. - Integration points enforcing decisions. - Negative-path test results. ## References - `reference.md`
© dev-toolings · MIT · dev-toolings/superpowers-symfony