Designing Backend

Name: Designing Backend
Author: qte77

ASecurity

Designs concise, streamlined backend systems matching exact task requirements. Use when planning APIs, data models, system architecture, or when the user requests backend design work.

2 stars
0 votes
0 copies
3 views
Added September 5, 2026

ai-agentsgitapibackendperformance

Works with

claude code
api

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add qte77/claude-code-plugins --skill designing-backend --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Designing Backend?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Designing Backend

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qte77-designing-backend/badge)](https://www.skillsdirectory.com/skills/qte77-designing-backend)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: designing-backend
description: Designs concise, streamlined backend systems matching exact task requirements. Use when planning APIs, data models, system architecture, or when the user requests backend design work.
compatibility: Designed for Claude Code
metadata:
  allowed-tools: Read, Grep, Glob, WebSearch, WebFetch
  argument-hint: [component-name]
  context: fork
  agent: Explore
  stability: stable
  content-hash: sha256:9db70205b1e48b51850bf2f9031a2ac58fe71a0a0af04b9e8e4c7e0692802c99
  last-verified-cc-version: 1.0.34
---

# Backend Architecture

## Git Context

- Recent changes: !`git log --oneline -3`
- Current branch: !`git branch --show-current`

**Target**: $ARGUMENTS

Creates **focused, streamlined** backend system designs matching stated
requirements exactly. No over-engineering.

## Workflow

1. **Read backend requirements** from specified documents
2. **Validate scope** - Simple data processing vs Complex system architecture
3. **Design minimal solution** matching stated complexity
4. **Create focused deliverables** - single doc for simple, multiple for complex
5. **Use make recipes** for all commands

## Architecture Strategy

**Simple Processing**: Basic functions, lightweight integration, existing patterns
**Complex Systems**: Multi-tiered pipelines, PydanticAI orchestration, async patterns
**Performance targets**: <1s simple operations, scalable for complex systems

## Output Standards

**Simple Tasks**: Single focused backend specification
**Complex Tasks**: Multiple targeted architecture files
**All outputs**: Concise, streamlined, no unnecessary complexity