---
name: Symfony Effective Context
slug: symfony-effective-context
category: AI Engineering
description: Symfony Effective Context provides execution guidance for Symfony changes with relevant files, patterns, and constraints. Use it when planning medium or complex updates and validating them in checkpoints.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/effective-context"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/effective-context ~/.claude/skills/effective-context"
installs_to: ~/.claude/skills/effective-context
source_path: skills/effective-context/SKILL.md
collection_size: 23
category_size: 2970
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:08.115Z
last_synced: 2026-09-04T05:27:08.115Z
canonical_url: "https://dirskills.com/skills/symfony-effective-context"
---

# Symfony Effective Context

Symfony Effective Context provides execution guidance for Symfony changes with relevant files, patterns, and constraints. Use it when planning medium or complex updates and validating them in checkpoints.

**Install:**

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

## README

# Effective Context (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`