mcpField
E
effective-context

effective-context

github.com/dev-toolingsAgent workflows22784 installsUpdated 3w ago
Repository

About effective-context

A Symfony skill for assembling focused context when requesting help, handing off work, or reporting an error. It prompts contributors to include versions, relevant code, logs, constraints, and prior attempts while excluding secrets.

Key features

  1. 01Goal and expected behavior template
  2. 02Symfony, PHP, and bundle versions
  3. 03Relevant files and error details
  4. 04Constraints and prior attempts
  5. 05Secret and data redaction guidance

Use cases

  1. 01Preparing a focused Symfony support question
  2. 02Handing a task to another contributor
  3. 03Providing context for error diagnosis

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dev-toolings/superpowers-symfony --skill effective-context

After installing, type/effective-contextin Claude Code to confirm it loaded.

Bundled filesreference.md

Details

From the project README

Effective Context (Symfony)

Use when

  • Asking for help on a Symfony problem, or handing a task over to someone else.
  • A previous answer was wrong because versions, bundles or constraints were missing.
  • Reporting an error that needs diagnosis.

Default workflow

  1. State the goal and the expected behavior in one or two sentences.
  2. Give the versions: Symfony, PHP, and the bundles involved.
  3. Include only the files on the path of the problem: entity, service, controller, configuration.
  4. Paste the full error with its stack trace, and the relevant log lines.
  5. List the constraints (performance, backward compatibility, existing patterns) and what was already tried.

Guardrails

  • Send the code on the path of the problem: not the whole src/, not a bare one-line question.
  • Do not refer to code that was not shown.
  • Strip secrets and personal data from logs and .env excerpts.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • A context block following the template in reference.md: context, goal, current code, observed behavior, attempts, constraints.
  • Versions and bundles, stated explicitly.

References

  • reference.md

Comments

Markdown supported