symfony:daily-workflow
Daily development workflow for Symfony projects including common tasks, debugging, and productivity tips
Works with
--- name: symfony:daily-workflow description: Daily development workflow for Symfony projects including common tasks, debugging, and productivity tips license: MIT --- # Daily Workflow (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`
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
