skills.rest
mdnaimul22
mdnaimul22COMMUNITY
Explore all skills by this author →
GitHub

senior-backend

Design backend systems with architecture patterns, API workflows, and database optimization.

2|Updated Apr 15, 2026
Search Tags:#authentication#database migrations#load testing#rest api#backend architecture#api security#postgresql optimization
One-click install
npx skills add https://github.com/mdnaimul22/human-skills --skill senior-backend-mdnaimul22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-backend
Source: https://github.com/mdnaimul22/human-skills/tree/main/skills/senior-backend
Command: npx skills add https://github.com/mdnaimul22/human-skills --skill senior-backend-mdnaimul22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires argparse, json, threading, concurrent.futures, statistics, ssl, urllib.request, urllib.error, pathlib, dataclasses, typing, re, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you design and implement production-ready backend systems by turning unclear product/backend requests into concrete API, database, and security decisions with explicit assumptions and verifiable success criteria.

Core Features & Use Cases

  • Backend architecture & pattern selection: Choose monolith vs modular monolith vs microservices with team-size, tenancy, and risk constraints, and surface tradeoffs before locking decisions.
  • API implementation guidance: Design REST/GraphQL-ready API structure, route scaffolding workflows, and consistent error/response conventions for real-world services.
  • Database optimization & safe migrations: Analyze schemas, spot indexing/migration gaps, and generate migration plans (including rollback) aligned to performance and reliability goals.
  • Security hardening workflows: Apply authentication, authorization, rate limiting, input validation, security headers, and security test/load strategies to reduce OWASP-class risks.

Quick Start

Ask: "Design the backend architecture for my customer-facing service with secure REST APIs, Postgres optimization, and production security hardening; assume shared multi-tenant PII and my team has 8 engineers with p99 QPS around 50—also give me the SLO and rollback approach I should document."

Frequently Asked Questions about senior-backend

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

FAQPage Schema
How do I design backend architecture for a multi-tenant REST API with PostgreSQL optimization?▼

Backend architecture design selects monolith or microservices patterns based on team size and tenancy constraints. It scaffolds REST API routes and applies PostgreSQL schema and index optimization strategies to achieve explicit p99 QPS and SLO performance targets.

How do I plan safe database migrations with rollback for production services?▼

Safe database migrations generate migration plans that include rollback procedures aligned with reliability goals. They analyze PostgreSQL schemas to spot indexing gaps and enforce recovery point objectives, ensuring data integrity during production deployment.

What's the best way to implement authentication and API security hardening?▼

API security hardening applies authentication, authorization, rate limiting, input validation, and security headers to reduce OWASP-class risks. It enforces tenancy and data-sensitivity gating before recommending specific authentication workflows for REST APIs.

How does load testing verify API performance for backend systems?▼

API load testing verifies backend performance by enforcing read/write ratio and p99 QPS assumptions. It validates that the architecture meets explicit SLO requirements under traffic, using concurrent execution to generate and measure real-time throughput.

Can I use this backend architecture approach for a small team of 8 engineers?▼

Backend architecture selection explicitly considers team size constraints when choosing between monolith, modular monolith, and microservices patterns. It surfaces tradeoffs based on your engineering headcount and multi-tenant data sensitivity before locking architectural decisions.

When do I need to document SLO and RPO/RTO for backend architecture decisions?▼

Backend architecture decisions require an explicit SLO plus recovery point and time objectives in recommendations. You need them when designing production REST APIs to ensure security hardening and database migration plans meet verifiable reliability criteria.

Related Skills

Explore More Software Engineering Skills→
saranskumarsaranskumar

system-architecture-designer

Plan and document scalable system architecture with deployment boundaries.

Community
Advanced
DexploarerDexploarer
7

disaster-recovery-planner

Design disaster recovery strategies with tiered RTO/RPO targets and multi-region failover.

Community
Advanced
AngelP17AngelP17
1

senior-devops

Automate CI/CD pipelines, infrastructure provisioning, and deployments across AWS, GCP, and Azure.

Community
Intermediate
badowhpbadowhp

software-architect

Design software architecture with service boundaries, data ownership, and tradeoff analysis.

Community
Advanced