agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/interfaces-and-autowiring/SKILL.md

interfaces-and-autowiring

Skill2 starsChanged 6 months agoMITView on GitHub

Master Symfony DI — interface autowiring (one impl per interface = automatic binding), `#[Autowire(service: 'X')]` for explicit override, `#[AutowireDecorated]` for decorators, `#[Target('name')]` for named-client routing (e.g. `HttpClientInterface` scoped clients), tagged services with `#[AsTaggedItem]` / `#[AutoconfigureTag]`, `#[AsAlias('id')]` for service aliases. Decorator pattern via `#[AsDecorator(decorates: 'id')]`. Trigger on "inject this", "decorate an API Platform processor", "multiple impls of same interface", or "named HTTP client".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use existing project patterns by default.

    line 24
  2. Distinctive:

    Avoid broad refactors without explicit need.

    line 25
  3. Distinctive:

    Keep decision log clear and auditable.

    line 26
  4. Distinctive:

    Use this file for execution posture and risk controls.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interfaces And Autowiring (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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free