---
name: Symfony Bootstrap Check
slug: symfony-bootstrap-check
category: Quality
description: Symfony Bootstrap Check verifies core project configuration such as .env, services.yaml, Doctrine, and framework requirements. Use it before medium or complex changes to confirm boundaries and validation checkpoints.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/bootstrap-check"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/bootstrap-check ~/.claude/skills/bootstrap-check"
installs_to: ~/.claude/skills/bootstrap-check
source_path: skills/bootstrap-check/SKILL.md
collection_size: 23
category_size: 1557
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:04.955Z
last_synced: 2026-09-04T05:27:04.955Z
canonical_url: "https://dirskills.com/skills/symfony-bootstrap-check"
---

# Symfony Bootstrap Check

Symfony Bootstrap Check verifies core project configuration such as .env, services.yaml, Doctrine, and framework requirements. Use it before medium or complex changes to confirm boundaries and validation checkpoints.

**Install:**

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

## README

# Bootstrap Check (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`