Software Engineering

Workflow

1. Understand the required behavior and the existing code before proposing structural changes.
2. Load clean-code, code-review, testing-strategies, practical-refactoring, solid-principles or design-patterns only as needed.
3. Prefer a small verified change; make abstractions earn their place and document only consequential choices.

Completion

Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.

Select a focused topic

• clean-code
• code-review
• design-patterns
• practical-refactoring
• solid-principles
• testing-strategies

---

Canonical source: skills/software-engineering/SKILL.md.