senior-engineer

Implement software features through six phases with clean architecture and SOLID principles.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/unrealandychan/AgentFoundry --skill senior-engineer-unrealandychan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-engineer
Source: https://github.com/unrealandychan/AgentFoundry/tree/main/skills/senior-engineer
Command: npx skills add https://github.com/unrealandychan/AgentFoundry --skill senior-engineer-unrealandychan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production-grade software is hard to plan and implement consistently. This skill helps teams deliver robust, well-tested code by enforcing clean architecture, SOLID principles, comprehensive tests, and maintainable patterns.

Core Features & Use Cases

  • Phase-driven workflow guiding six steps: parse, clarify, design, implement, test, and production readiness.
  • Explicit assumptions, interface contracts, and modular design to reduce integration risk.
  • Built-in Phase #6 readiness and governance checks to ensure production readiness before deployment.

Quick Start

Provide a task to /senior-engineer specifying a code feature and optional flags to generate production-grade, well-tested implementation.

Frequently Asked Questions about senior-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write production-grade code with clean architecture?▼

Production-grade code with clean architecture is produced by enforcing SOLID principles, explicit interface contracts, modular design, and comprehensive testing throughout a structured development workflow.

What is the best way to refactor legacy software for SOLID compliance?▼

Refactoring legacy software for SOLID compliance is guided through a six-phase process: parse, clarify, design, implement, test, and production readiness to ensure maintainable patterns and robust architecture.

How do you enforce interface contracts and modular design during feature development?▼

Interface contracts and modular design are enforced by explicitly defining assumptions and interactions during the design phase, reducing integration risk before moving into implementation and testing.

Can I use this approach for architecture reviews across different tech stacks?▼

Architecture reviews across supported stacks are supported by applying clean architecture and SOLID principles to evaluate feature development, refactoring paths, and overall production readiness.

How do I check production readiness before deploying new software features?▼

Production readiness before deployment is checked through built-in phase six governance checks that verify comprehensive testing, explicit assumptions, and modular design compliance.

Why does software testing fail to catch integration issues in complex features?▼

Software testing fails to catch integration issues when explicit assumptions and interface contracts are not defined, making modular design and a structured phase-driven workflow necessary to reduce risks.