backend-core

Guide backend architecture for APIs, authentication, security, and database schemas.

Updated Aug 2, 2025
One-click install
npx skills add https://github.com/czer323/d3-item-salvager --skill backend-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-core
Source: https://github.com/czer323/d3-item-salvager/tree/main/.claude/skills/backend-core
Command: npx skills add https://github.com/czer323/d3-item-salvager --skill backend-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Language-agnostic backend patterns for API design, authentication, security, and databases help teams build robust, scalable backends across projects without vendor lock.

Core Features & Use Cases

  • API Design Guidance: REST, GraphQL, and data modeling patterns for consistent interfaces.
  • Authentication & Security: JWT, OAuth, sessions, input validation, and secure defaults to protect endpoints.
  • Database & Migrations: Schema design, migrations, indexing, and soft-delete guidelines to maintain data integrity.
  • Use Case: A team standardizes backend architecture across microservices to reduce duplication and improve security.

Quick Start

Review the Backend Core Patterns guide to apply API design, authentication, security, and database patterns to your project.

Frequently Asked Questions about backend-core

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

FAQPage Schema
What are the best backend patterns for designing secure APIs?

Secure API design patterns provide language-agnostic guidance for REST, GraphQL, and data modeling to build consistent interfaces. They address authentication, input validation, and secure defaults to protect endpoints across microservices without vendor lock-in.

How do I choose between JWT, OAuth, and sessions for API authentication?

API authentication strategies include JWT, OAuth, and sessions, each offering distinct security boundaries. Evaluating these options involves applying secure defaults and input validation to select the appropriate mechanism for protecting endpoints across your specific microservices architecture.

When do I need database schema migrations and soft-delete guidelines?

Database schema migrations and soft-delete guidelines are needed to maintain data integrity when evolving data-driven applications. They provide structured approaches for indexing and schema design, ensuring consistent interfaces and robust backend state management.

How do I standardize backend architecture across multiple microservices?

Standardizing backend architecture across microservices involves applying consistent API design, authentication strategies, and database patterns. This reduces duplication and improves security by enforcing language-agnostic guidelines for interfaces and data modeling.

Can I apply these backend patterns to any API-centric architecture?

Yes, these backend patterns apply to any API-centric architecture, including microservices and data-driven applications. They offer language-agnostic guidance for API design, security, and databases, preventing vendor lock-in while ensuring robust and scalable implementations.