---
name: Controller Cleanup
slug: controller-cleanup
category: Quality
description: Controller Cleanup refactors fat Symfony controllers into lean ones by moving business logic into services, handlers, and invokable commands. Use it for medium-complexity architecture changes that need checkpoints and validation.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/controller-cleanup"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/controller-cleanup ~/.claude/skills/controller-cleanup"
installs_to: ~/.claude/skills/controller-cleanup
source_path: skills/controller-cleanup/SKILL.md
collection_size: 23
category_size: 1557
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:05.650Z
last_synced: 2026-09-04T05:27:05.650Z
canonical_url: "https://dirskills.com/skills/controller-cleanup"
---

# Controller Cleanup

Controller Cleanup refactors fat Symfony controllers into lean ones by moving business logic into services, handlers, and invokable commands. Use it for medium-complexity architecture changes that need checkpoints and validation.

**Install:**

```bash
npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/controller-cleanup ~/.claude/skills/controller-cleanup
```

## README

# Controller Cleanup (Symfony)

## Use when
- Refining architecture/workflows/context handling in Symfony projects.
- Planning and executing medium/complex changes safely.

## Default workflow
1. Establish current boundaries, constraints, and coupling points.
2. Propose smallest coherent architectural adjustment.
3. Execute in checkpoints with validation at each stage.
4. Summarize tradeoffs and follow-up backlog.

## Guardrails
- Use existing project patterns by default.
- Avoid broad refactors without explicit need.
- Keep decision log clear and auditable.

## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.

## Output contract
- Architecture/workflow changes.
- Checkpoint validation outcomes.
- Residual risks and next steps.

## References
- `reference.md`
- `docs/complexity-tiers.md`