Backend Engineer
Backend work from requirements to a validated implementation, instead of jumping straight into code.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a complex domain. Let me ask some clarifying questions first. Are you handling recurring billing monthly or supporting custom intervals? Do you need to track refunds and disputes separately? What's your payment processor—Stripe, another provider? How many subscriptions do you expect per day? I'd normally suggest normalizing user, subscription, and payment tables, but your specific requirements might call for a different approach. What's your scale and retention pattern like?
DATABASE SCHEMA: SUBSCRIPTION BILLING CORE TABLES Users → id, email, created_at, stripe_customer_id Subscriptions → id, user_id, plan_id, status (active/canceled/suspended), started_at, ends_at, current_period_start, current_period_end Invoices → id, subscription_id, amount, currency, due_date, paid_at, status (draft/sent/paid/void) Payments → id, invoice_id, provider_id (stripe charge ID), amount, method, succeeded_at, failed_at Refunds → id, payment_id, reason, amount, initiated_at, completed_at RELATIONSHIPS & INDEXES subscriptions.user_id → users (cascade delete) subscriptions.status + current_period_end → index for renewal jobs invoices.subscription_id, paid_at → index for reporting payments.provider_id → unique constraint (prevent duplicate webhook processing) EDGE CASES ADDRESSED Proration → Calculate daily rate if plan changes mid-cycle Dispute flow → Payment marked disputed, subscription held (not canceled) Cancellation → Soft-delete pattern, keeps invoicing history Retry logic → Failed payment marked, not auto-retried (webhook handles) MIGRATION STRATEGY Step 1: Create new tables (no downtime) Step 2: Backfill from old system (parallel read) Step 3: Dual-write new tables for 1 week Step 4: Read from new tables, monitor for anomalies Step 5: Archive old table after 30-day validation
About this skill
name: cs-backend-engineer description: Use when Structured Claude skill that gives Claude a repeatable workflow for cs backend engineer.
Cs Backend Engineer
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Cs Backend Engineer workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cs-backend-engineer skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cs Backend Engineer; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cs-backend-engineer
description: Use this skill when a backend engineering task needs a repeatable workflow for designing APIs, data models, and service logic with consistent validation.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Cs Backend Engineer
Gives backend engineering work a consistent workflow from requirements to a validated implementation, rather than jumping straight into code.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.