How do I install the Backend Mindset skill?

Run npx skillmds@latest add ntphat0322/backend-mindset in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backend Mindset safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backend Mindset?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backend Mindset free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backend Mindset?

NTPhat0322 (@ntphat0322) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backend Mindset by ntphat0322 — Agent Skill

Name: Backend Mindset
Rating: 4.2 (5 reviews)
Author: NTPhat0322

Backend Mindset

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

NTPhat0322 Updated Sep 22, 2026

File contents

Backend Development Skill

References

File	Covers
`references/api-design.md`	REST, GraphQL, gRPC — URL rules, status codes, protocol selection
`references/authentication.md`	OAuth 2.1, JWT, RBAC, MFA, session management
`references/security.md`	OWASP Top 10 (2025), rate limiting, headers, secrets
`references/performance.md`	Indexing, caching patterns, load balancing, async processing
`references/architecture.md`	Microservices patterns, event-driven, CQRS, scalability
`references/testing.md`	TDD, test pyramid, contract testing, migration tests
`references/code-quality.md`	SOLID, design patterns, refactoring signals

Quick Decision Guide

Need	Choose
Public / browser clients	REST or GraphQL
Internal high-throughput	gRPC
Flexible data fetching	GraphQL
Streaming	gRPC (bidirectional) or SSE
Single team, unclear domain	Monolith
Multiple autonomous teams	Microservices
Audit trail required	Event Sourcing
Read/write load imbalance	CQRS
Task >200ms off request path	Async queue
Session across instances	Redis (never in-process)

Defaults

Every non-public endpoint requires explicit auth declaration — no implicit defaults
Input validation at every system boundary (API handler, event consumer, file parser)
Parameterized queries everywhere — never string-interpolate user input
Rate limiting on auth endpoints, public API, and file upload (see security.md for thresholds)
Integration tests hit real infrastructure (Testcontainers) — in-memory substitutes hide real bugs
TDD: write the failing test before any implementation
Services return result envelopes — never throw for expected failures (404, 400, 409)

---name: backend-mindsetdescription: Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.---# Backend Development Skill## References| File | Covers ||------|--------|| `references/api-design.md` | REST, GraphQL, gRPC — URL rules, status codes, protocol selection || `references/authentication.md` | OAuth 2.1, JWT, RBAC, MFA, session management || `references/security.md` | OWASP Top 10 (2025), rate limiting, headers, secrets || `references/performance.md` | Indexing, caching patterns, load balancing, async processing || `references/architecture.md` | Microservices patterns, event-driven, CQRS, scalability || `references/testing.md` | TDD, test pyramid, contract testing, migration tests || `references/code-quality.md` | SOLID, design patterns, refactoring signals |## Quick Decision Guide| Need | Choose ||------|--------|| Public / browser clients | REST or GraphQL || Internal high-throughput | gRPC || Flexible data fetching | GraphQL || Streaming | gRPC (bidirectional) or SSE || Single team, unclear domain | Monolith || Multiple autonomous teams | Microservices || Audit trail required | Event Sourcing || Read/write load imbalance | CQRS || Task >200ms off request path | Async queue || Session across instances | Redis (never in-process) |## Defaults- Every non-public endpoint requires explicit auth declaration — no implicit defaults- Input validation at every system boundary (API handler, event consumer, file parser)- Parameterized queries everywhere — never string-interpolate user input- Rate limiting on auth endpoints, public API, and file upload (see security.md for thresholds)- Integration tests hit real infrastructure (Testcontainers) — in-memory substitutes hide real bugs- TDD: write the failing test before any implementation- Services return result envelopes — never throw for expected failures (404, 400, 409)

Frequently asked questions