senior-backend

Guide backend system design, code reviews, and architectural decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PerryB-GIT/wascar-perry-workspace --skill senior-backend-perryb-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-backend
Source: https://github.com/PerryB-GIT/wascar-perry-workspace/tree/main/claude-skills-package/skills/web-dev/senior-backend
Command: npx skills add https://github.com/PerryB-GIT/wascar-perry-workspace --skill senior-backend-perryb-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides expert guidance on designing, reviewing, and maintaining scalable, reliable, and maintainable backend systems, addressing complex architectural decisions and team collaboration challenges.

Core Features & Use Cases

  • System Design: Offers a structured approach to designing backend architectures, from high-level patterns to component deep dives.
  • Code Review: Provides a philosophy and checklist for effective and constructive code reviews.
  • Mentoring & Debugging: Guides on mentoring junior developers and systematically debugging complex production issues.
  • Use Case: A startup needs to design its core backend infrastructure. This Skill can guide the team through choosing between monoliths and microservices, selecting appropriate databases and caches, and establishing best practices for code quality and deployment.

Quick Start

Use the senior-backend skill to help design a scalable API for a new e-commerce platform.

Frequently Asked Questions about senior-backend

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

FAQPage Schema
How do I design a scalable backend architecture for an e-commerce platform?

Designing a scalable backend architecture involves choosing between monoliths and microservices, selecting appropriate databases and caches, and establishing deployment best practices to ensure maintainability and production readiness.

What is the best way to conduct effective code reviews for backend systems?

Effective code reviews require a structured philosophy and checklist to provide constructive feedback, ensuring code quality, maintainability, and team collaboration without creating friction.

When do I need event-driven architecture or CQRS in system design?

You need event-driven architecture or CQRS when designing complex backend systems that require high scalability, specific component deep dives, and reliable handling of independent read and write workloads.

Microservices vs monolith: how to choose for startup backend infrastructure?

Choosing between microservices and monoliths for startup backend infrastructure depends on your team dynamics, required scalability, and maintainability goals, balancing rapid deployment against architectural complexity.

How do I systematically debug complex production issues in backend systems?

Systematically debugging complex production issues requires structured methodologies to identify root causes in scalable backend architectures while mentoring junior developers through the resolution process.