
Symfony:effective Context Skill
- 457 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:effective-context is a Symfony superpowers skill that gives coding agents concise project context—bundles, conventions, env, and task scope—so patches match app structure and avoid generic PHP mistakes.
About
symfony:effective-context is a skill in MakFly/superpowers-symfony that applies production-grade Symfony architecture workflows with controlled scope and auditable checkpoints. Part of a 44-skill Symfony 7.4 LTS and 8.x pack, it guides agents to establish boundaries, constraints, and coupling points, propose the smallest coherent adjustment, execute in validated stages, and log tradeoffs plus follow-up backlog items. Allowed tools are Read, Glob, and Grep for safe context discovery without premature edits. Developers reach for symfony:effective-context when planning medium-to-complex Symfony refactors, refining context handling across bundles and services, or limiting blast radius before broad changes. Output contracts include architecture changes, checkpoint validation outcomes, and residual risk notes referencing docs/complexity-tiers.md.
- Project layout summaries
- Bundle and service map hints
- Env and config boundaries
- Task-scoped file lists
- Symfony-specific guardrails
Symfony:Effective Context by the numbers
- 457 all-time installs (skills.sh)
- Ranked #1,929 of 16,575 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonyeffective-contextAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 457 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do agents get effective Symfony project context?
Give coding agents concise Symfony project context—bundles, conventions, env, and task scope—so generated patches match your app structure and avoid generic PHP mistakes.
Who is it for?
PHP developers on Symfony 7.4 LTS or 8.x projects running medium-complexity architectural or workflow changes through validated checkpoints.
Skip if: Greenfield Symfony bootstrapping or one-line bug fixes without architectural scope should use symfony:bootstrap-check or targeted recipe skills instead.
When should I use this skill?
A Symfony task needs bounded context about bundles, services, env, and conventions before planning or executing multi-step backend changes.
What you get
Scoped architecture adjustments, checkpoint validation outcomes, auditable decision log, and follow-up backlog items.
- Scoped change plan
- Checkpoint validation log
- Residual risk and backlog notes
By the numbers
- Member of superpowers-symfony pack with 44 skill definitions
- 4-step default workflow from boundaries through tradeoff summary
Files
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.mddocs/complexity-tiers.md
Reference
Providing Effective Context
What Context Helps
When asking Claude for help with Symfony, provide:
1. Relevant code files - Entity, Service, Controller involved 2. Error messages - Full stack trace if available 3. Symfony version - 8.x (stable), 7.4 LTS, or 6.4 legacy LTS 4. Installed bundles - API Platform, Messenger, etc. 5. Constraints - Performance requirements, backward compatibility
Code Context Examples
For Entity Questions
Provide:
- The entity file
- Related entities (if relationships involved)
- The repository if custom queries
- Current migration stateFor API Platform Questions
Provide:
- Entity with API Platform attributes
- Custom providers/processors if any
- Relevant filters
- Expected request/response formatFor Testing Questions
Provide:
- Test file
- Code being tested
- Factory files
- Error outputEffective Prompts
Good: Specific and Contextual
I have a Symfony 7 app with API Platform 4. I need to add a filter
that searches across multiple fields (title, description, author name).
Here's my entity:
[paste entity code]
Current filters work for single fields. How do I create a custom
filter that does OR search across these fields?Bad: Vague and Missing Context
How do I search in API Platform?Including Error Context
Full Error Message
When I run bin/console doctrine:migrations:migrate, I get:
[Error message with full stack trace]
My entity is:
[entity code]
My migration is:
[migration code]Relevant Log Output
The Messenger worker crashes with this error in var/log/dev.log:
[2024-01-15 10:30:00] messenger.ERROR: Error thrown while handling message...
My message handler:
[handler code]
My message:
[message code]Constraints to Mention
Performance Requirements
This endpoint needs to handle 1000 requests/second. Currently it's slow
because of N+1 queries. Here's the code:
[code]Backward Compatibility
I need to add a new field to the API response without breaking existing
clients. Current response format:
[JSON example]Existing Patterns
Our codebase uses CQRS pattern. Here's an example command handler:
[example code]
I need to add a new feature following the same pattern.Project Structure Context
When Asking About Architecture
Our project structure:
src/
├── Domain/ # Entities, Value Objects
├── Application/ # Commands, Queries, Handlers
└── Infrastructure/ # Controllers, Repositories
We follow hexagonal architecture. How should I structure a new
feature for user notifications?When Asking About Configuration
config/packages/messenger.yaml:
[current config]
I need to add a second transport for high-priority messages.Version-Specific Context
Symfony Version
Symfony 6.4 LTS project. Can I use MapRequestPayload attribute?
Or is that only in 7.x?PHP Version
PHP 8.2, Symfony 7.1. I want to use readonly classes for my DTOs.Bundle Versions
API Platform 3.2. I see examples using "operations" but my version
uses "collectionOperations". Which syntax should I use?Anti-Patterns to Avoid
Don't Provide Too Much
# Bad: dumping entire project
Here's my entire src/ directory...
[thousands of lines]Don't Provide Too Little
# Bad: no context
Why doesn't my query work?Don't Assume Knowledge
# Bad: referring to unseen code
The UserService I showed you earlier...
[But it wasn't shown]Template for Asking Questions
## Context
- Symfony version: X.Y
- PHP version: 8.X
- Relevant bundles: [list]
## What I'm Trying to Do
[Clear description of goal]
## Current Code
[Relevant files only]
## What's Happening
[Error message or unexpected behavior]
## What I've Tried
[Previous attempts if any]
## Constraints
[Performance, compatibility, patterns to follow]Skill Operating Checklist
Design checklist
- Confirm operation boundaries and invariants first.
- Minimize scope while preserving contract correctness.
- Test both happy path and negative path behavior.
Validation commands
- rg --files
- composer validate
- ./vendor/bin/phpstan analyse
Failure modes to test
- Invalid payload or forbidden actor.
- Boundary values / not-found cases.
- Retry or partial-failure behavior for async flows.
Related skills
How it compares
Pick symfony:effective-context for scoped Symfony context and checkpoints; use symfony:brainstorming for early requirements exploration without execution posture.
FAQ
What Symfony versions does symfony:effective-context target?
symfony:effective-context belongs to superpowers-symfony, which targets Symfony 7.4 LTS and 8.x with 6.4 LTS legacy support, API Platform v4, and Doctrine ORM 3.
What tools can symfony:effective-context use?
symfony:effective-context allows Read, Glob, and Grep only. The skill gathers Symfony project context and plans checkpointed changes before deeper write skills execute patches.