
Symfony:bootstrap Check Skill
- 499 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:bootstrap-check is a Claude Code skill that validates fresh Symfony project directory structure, configuration files, and essential dependencies for developers who need a verified foundation before writing busine
About
symfony:bootstrap-check is a Symfony-focused agent skill from makfly/superpowers-symfony that audits a newly created Symfony project for correct directory layout, required configuration files, and essential Composer dependencies. The skill walks through Symfony conventions—config/, src/, public/, .env, composer.json packages, and bundle registration—so agents catch scaffold gaps before controllers, entities, or services are added. Developers reach for symfony:bootstrap-check right after `symfony new` or Flex install when bootstrapping a greenfield API or web app and want confidence the skeleton matches Symfony best practices. The skill ranks 5 on skills.sh with 418 installs, signaling steady adoption among Symfony teams using AI coding agents.
- Validates Symfony project bootstrap against official best practices
- Checks directory layout, composer.json, .env, and security settings
- Reports missing or misconfigured bootstrap components
- Designed as the first step after `symfony new` or `composer create-project`
- Outputs clear remediation steps for any failed checks
Symfony:Bootstrap Check by the numbers
- 499 all-time installs (skills.sh)
- Ranked #835 of 4,492 Backend & APIs 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 symfonybootstrap-checkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 499 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do you verify a fresh Symfony project scaffold?
Verify a fresh Symfony project has the correct directory structure, configuration files, and essential dependencies before writing business logic.
Who is it for?
PHP developers bootstrapping a new Symfony 6/7 project who want an automated scaffold audit before writing domain code.
Skip if: Teams debugging runtime errors, writing PHPUnit tests, or deploying Symfony to production infrastructure.
When should I use this skill?
User creates or clones a new Symfony project and asks to verify structure, config, or dependencies before coding.
What you get
Symfony bootstrap checklist results, missing-file report, and dependency verification notes
By the numbers
- 418 installs on skills.sh
- Ranked #5 in makfly/superpowers-symfony
Files
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.mddocs/complexity-tiers.md
Reference
Bootstrap Check
Verify your Symfony project is properly configured before starting development.
Essential Files Check
1. Environment Configuration
# Required files
.env # Base environment variables
.env.local # Local overrides (not committed)
.env.test # Test environment
# Check .env exists
ls -la .env*2. Configuration Files
# Framework configuration
config/packages/framework.yaml
config/packages/doctrine.yaml
config/packages/security.yaml
config/services.yaml
# Routes
config/routes.yaml
config/routes/annotations.yaml # or attributes.yaml3. Directory Structure
your-project/
├── bin/
│ └── console
├── config/
│ ├── packages/
│ ├── routes/
│ └── services.yaml
├── public/
│ └── index.php
├── src/
│ ├── Controller/
│ ├── Entity/
│ └── Kernel.php
├── var/
│ ├── cache/
│ └── log/
├── vendor/
├── composer.json
└── composer.lockQuick Validation Commands
# Check Symfony requirements
bin/console about
# Verify services are wired correctly
bin/console debug:autowiring
# Check routes
bin/console debug:router
# Verify Doctrine configuration
bin/console doctrine:mapping:info
# Check container compilation
bin/console cache:clearCommon Issues & Fixes
1. Missing APP_SECRET
# .env
APP_SECRET=your-secret-here
# Generate new secret
php -r "echo bin2hex(random_bytes(16));"2. Database Not Configured
# .env
DATABASE_URL="postgresql://user:pass@127.0.0.1:5432/db?serverVersion=15"
# or
DATABASE_URL="mysql://user:pass@127.0.0.1:3306/db?serverVersion=8.0"3. Cache Permission Issues
# Clear and warm cache
bin/console cache:clear
bin/console cache:warmup
# Fix permissions
chmod -R 777 var/cache var/log
# Or better, use ACL
setfacl -R -m u:www-data:rwX var
setfacl -dR -m u:www-data:rwX var4. Missing Vendor Directory
composer install5. Doctrine Schema Out of Sync
# Check differences
bin/console doctrine:schema:validate
# Generate migration
bin/console make:migration
# Run migrations
bin/console doctrine:migrations:migrateAPI Platform Check
If using API Platform:
# Verify API Platform is working
bin/console debug:router | grep api
# Check API resources
bin/console api:openapi:export
# Verify serialization groups
bin/console debug:serializerMessenger Check
If using Messenger:
# Verify transports
bin/console debug:messenger
# Check routing
bin/console debug:config framework messengerPre-Development Checklist
- [ ]
.envfile exists with required variables - [ ]
composer installexecuted - [ ] Database connection working
- [ ]
bin/console cache:clearsucceeds - [ ]
bin/console debug:autowiringshows services - [ ] All migrations executed
- [ ] (Optional) Fixtures loaded for development
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:bootstrap-check over generic PHP lint skills when you need Symfony-specific directory, bundle, and Flex dependency validation on a fresh project.
FAQ
What does symfony:bootstrap-check validate?
symfony:bootstrap-check validates a fresh Symfony project's directory layout, configuration files such as .env and config/packages/, and essential Composer dependencies. The skill confirms the scaffold matches Symfony conventions before controllers, entities, or services are adde
When should I run symfony:bootstrap-check?
Run symfony:bootstrap-check immediately after `symfony new`, Flex install, or cloning a Symfony starter repo. The skill catches missing directories, misconfigured bundles, or absent dependencies before business logic is written.