Skip to main content
skill CX Codex

daily-workflow — Claude Code skill for Symfony

The daily-workflow skill lays out a routine for Symfony work, from getting a project running to checking changes before a commit. Use it for migrations, debugging, and recurring maintenance.

MIT ★ 234 updated 2026-10-05

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dev-toolings/superpowers-symfony --skill daily-workflow -a claude-code
Open on GitHub

What daily-workflow does

At the start of a session, the skill advises syncing the project, installing dependencies if the lock file changed, and applying pending migrations. Start the services the project uses, then check bin/console about. It favours small changes tested as you go.

For debugging, it points to debug:* commands, the profiler, and var/log/dev.log. Before a commit, run style checks, static analysis, and tests; remove dump() and dd(). Do not load fixtures or reset the schema on a shared or production database, since that can affect other users' data. Prefix commands with the Docker or host runner used by the project.

What it helps with

  • get a Symfony project ready for a work session
  • apply pending migrations and inspect the application
  • trace a bug with debugging commands and logs
  • check changes before committing

Example prompts for the agent

  • Get this Symfony project ready for a work session and check its status.
  • Investigate this error using debug:*, the profiler, and var/log/dev.log.
  • Check my changes before commit and find any remaining dump() or dd().

How to install daily-workflow

1Skills CLI (Vercel)

npx skills add dev-toolings/superpowers-symfony --skill daily-workflow -a claude-code

2Manually: put the files in place

~/.claude/skills/daily-workflow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/daily-workflow/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about daily-workflow

How do I install daily-workflow in Claude Code?

Run npx skills add dev-toolings/superpowers-symfony --skill daily-workflow -a claude-code. The skill file is at ~/.claude/skills/daily-workflow/SKILL.md.

What does daily-workflow do?

It sets out a Symfony routine for starting work, testing changes, debugging, and running checks before a commit.

Can I reset a database schema while following this skill?

Do not reset the schema or load fixtures on a shared or production database.

Source text

SKILL.md · MIT
---
name: daily-workflow
description: Daily development workflow for Symfony projects including common tasks, debugging, and productivity tips
capabilities: [read, search]
tags: [workflow]
# projected by `bun run build` — do not edit by hand
allowed-tools:
  - Read
  - Glob
  - Grep
---

# Daily Workflow (Symfony)

## Use when
- Starting or resuming a work session on a Symfony project.
- Routine tasks: migrations, fixtures, consuming messages, clearing the cache.
- Debugging with `debug:*` commands, the profiler, and the logs.
- Getting a change ready to commit.

## Default workflow
1. Sync: pull, run `composer install` when the lock file changed, apply pending migrations.
2. Start the services the project uses and check `bin/console about`.
3. Work in small test-first cycles with the project's test runner.
4. Debug with `debug:*` commands, the profiler and `var/log/dev.log` before adding dumps.
5. Before committing, run style, static analysis and tests, and remove every `dump()` and `dd()`.

## Guardrails
- Prefix commands with the runner the project uses (Docker or host), from the runtime context.
- Never load fixtures or reset the schema on a shared or production database.
- Do not commit `dump()`, `dd()` or debug-only code.
- Do not patch `vendor/` to work around a problem.

## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.

## Output contract
- The commands run, with the project's runner prefix.
- Debugging findings, with the evidence behind them.
- A change ready to commit, quality gates green.

## References
- `reference.md`

© dev-toolings · MIT · dev-toolings/superpowers-symfony

Similar skills

All skills for Backend and APIs →

From the same set51

The whole set →
strategy-pattern Implements the Strategy pattern in Symfony using tagged services. Helps clean up branching logic when algorithms or providers vary at runtime. CX Codex +1 ★ 234repo stars executing-plans The executing-plans skill guides Claude Code through an approved implementation plan, with test-first steps and a separate commit for each one. Use it for multi-step work or to resume after an interruption. CX Codex +1 ★ 234repo stars twig-components twig-components turns repeated Twig markup into Symfony UX components with props, slots and CVA variants. Handy once the same template chunk starts getting copied around. CX Codex +1 ★ 234repo stars cqrs-and-handlers cqrs-and-handlers implements CQRS in Symfony projects using separate Messenger buses for commands and queries. CX Codex +1 ★ 234repo stars bootstrap-check bootstrap-check runs a pass/fail check over a Symfony project's setup: .env, services, Doctrine mappings, routes. Each failure comes with the fix. CX Codex +1 ★ 234repo stars ports-and-adapters ports-and-adapters guides Claude Code in setting up Hexagonal Architecture in Symfony, isolating domain models from Doctrine, HTTP, and vendor SDKs. CX Codex +1 ★ 234repo stars config-env-parameters The config-env-parameters skill guides changes to Symfony environment variables, parameters, and secrets across environments. Use it when configuration needs a clear home and safe injection into the app. CX Codex +1 ★ 234repo stars doctrine-fixtures-foundry doctrine-fixtures-foundry teaches the agent to build Doctrine test data with Zenstruck Foundry v2 factories: named states, sequences and entity relations. Triggers when you write fixtures or migrate factories from Foundry v1. CX Codex +1 ★ 234repo stars

Project sponsors

Companies that keep this analytics open