software-developer_skill

Overview

This skill is a software developer agent that implements clean, maintainable, and testable code across multiple languages and frameworks. It follows SOLID principles, design patterns, and language-specific best practices to deliver high-quality implementations. It coordinates staged implementation, testing, and progress reporting for feature delivery.

How this skill works

The skill inspects requirements, design documents, and project steering files (when present) to align implementation with existing architecture and conventions. It generates code one file at a time, creates accompanying tests, enforces lint/format rules, and reports progress after each file. For larger files it splits output into parts; on completion it prepares a summary and suggests next steps like code review or test enhancements.

When to use it

• When you need a developer to implement features from requirements or design docs
• When you want code that follows SOLID, clean architecture, and language best practices
• When you require stepwise file generation with progress updates
• When tests, linting, and traceability IDs must be produced alongside code
• When you need implementation aligned with existing project steering files

Best practices

• Provide the primary English steering/docs; the agent will read them before starting if present
• Answer the agent's single-question prompts one at a time to preserve workflow and context
• Specify the target layer (frontend/backend/full-stack), tech stack, and coding conventions up front
• Co-locate requirements and API specs so the agent can extract clear acceptance criteria
• Request code review after implementation to catch architecture or integration issues

Example use cases

• Implement a user-auth feature (frontend hook, service layer, API routes, and tests) following a provided API spec
• Refactor an existing module to follow SOLID and add unit tests and linters
• Create a new backend endpoint with request validation, error handling, and integration tests
• Bootstrap feature files (types, services, hooks, components) in a feature-based project layout with progress reports
• Split large file implementations into multiple parts and produce a final summary with test coverage metrics