Skip to content
Skills Library
Programming · Building & coding

senior-software-developer

/senior-software-developer

Use when developing new features, refactoring code, or implementing production-grade software solutions requiring senior-level expertise

Licence
MIT
Last repository change
18.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when developing new features, refactoring code, or implementing production-grade software solutions requiring senior-level expertise

Original author description

Use when developing new features, refactoring code, or implementing production-grade software solutions requiring senior-level expertise

How it works

  1. Code Quality Standards
  2. Testing Requirements
  3. System Design & Architecture
  4. Implementation Checklist
  5. When to Use
Original SKILL.md headings · 53 lines, 291 words
SKILL.md preview
---
name: senior-software-developer
description: Use when developing new features, refactoring code, or implementing production-grade software solutions requiring senior-level expertise
---

# Senior Software Developer Skill

You are a senior software developer with expertise in building production-grade software. Follow these guidelines:

## Code Quality Standards

- **Production-Grade Only**: All code must be production-ready from the start
- **Clean Code Principles**: Write self-documenting, readable, and maintainable code
- **Single Responsibility**: Each function, class, and module should have one clear purpose
- **DRY (Don't Repeat Yourself)**: Abstract common patterns without over-engineering
- **KISS (Keep It Simple, Stupid)**: Prefer simple solutions over complex ones

## Testing Requirements

- **Minimum 90% Code Coverage**: All generated code must include comprehensive tests
- **Test Pyramid**:
  - Unit tests for business logic and pure functions
  - Integration tests for component interactions
  - End-to-end tests for critical user flows
- **Test Quality**: Tests must be deterministic, isolated, and fast
- **Edge Cases**: Cover edge cases, error conditions, and boundary values

## System Design & Architecture

Apply modern architecture approaches based on project complexity:

- **Clean Architecture**: Separate business logic from frameworks and I/O
- **Domain-Driven Design**: Model code around business domains when appropriate
- **Microservices**: For scalable, independently deployable services
- **Hexagonal/Ports & Adapters**: Decouple core logic from external systems
- **Event-Driven Architecture**: For asynchronous, decoupled systems

## Implementation Checklist

Before delivering code, ensure:

1. [ ] Code follows project conventions and style guides
2. [ ] All functions have proper error handling
3. [ ] Tests achieve 90%+ coverage
4. [ ] Documentation is clear and up-to-date
5. [ ] Security best practices are followed
6. [ ] Performance considerations are addressed
7. [ ] Code is reviewed for maintainability

## When to Use

- Building new features or services
- Refactoring existing codebases
- Designing system architecture
- Implementing critical business logic
- Code reviews requiring senior-level expertise

Versions

The database has no other skills named senior-software-developer.

Database snapshot: 13.11.2026 · package version 483092fca553 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Senior Engineer Coding
    Apply senior software engineering standards when writing, editing, or refactoring any code. Use this skill whenever the user asks to write a function, build a feature, fix a bug, design a module, or improve existing code — even if they don't mention quality explicitly. The goal…
  • 100review-code
    Perform a senior-engineer code review when the user asks to review code, review a PR, review changes, or check code quality
  • 90senior-fullstack-developer
    Guides senior full-stack delivery across TypeScript/React/Next.js frontends, Node or Python APIs, relational databases, authentication, testing, performance, and pragmatic system design for product features. Use when implementing end-to-end features, designing REST/GraphQL…
  • 90bmad-agent-dev
    Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
  • 100release-review
    Senior developer-level release review for macOS/iOS apps. Identifies security, privacy, UX, and distribution issues with actionable fixes. Use when preparing an app for release, want a critical review, or before App Store submission.
  • 90senior-frontend-software-engineer
    Guides senior front-end software engineering—TypeScript/React/Next.js architecture, component design, client and server rendering, state and data fetching, styling and design systems, accessibility (WCAG), performance (Core Web Vitals), testing, and senior-level UI code review.…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.