backend-entity-dev

Automate backend entity creation with SQLAlchemy models and Pydantic schemas.

Updated Dec 27, 2025
One-click install
npx skills add https://github.com/ogghst/backcast --skill backend-entity-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-entity-dev
Source: https://github.com/ogghst/backcast/tree/main/.claude/skills/backend-entity-dev
Command: npx skills add https://github.com/ogghst/backcast --skill backend-entity-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend development often requires repetitive boilerplate for new domain entities and precise EVCS-patterned scaffolding. This Skill automates the creation and implementation of backend entities with strict typing and consistent structure.

Core Features & Use Cases

  • Entity type determination (Simple, Versionable, Branchable) based on versioning/branching needs
  • Automatic SQLAlchemy model generation with base classes and mixins
  • Pydantic schemas creation (Create, Update, Public)
  • Service layer scaffolding with proper base classes
  • Optional repository and tests scaffolding with unit and integration tests
  • Guidance for applying EVCS patterns across different domain models (Projects, Costs, Users, etc.)

Quick Start

Define the entity scope, then generate models, schemas, services, repositories, and tests following the EVCS patterns.

Frequently Asked Questions about backend-entity-dev

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

FAQPage Schema
How do I generate SQLAlchemy models and Pydantic schemas for new backend entities?

Backend entity creation requires repetitive boilerplate for domain models and precise EVCS-patterned scaffolding. This process automates generating models, schemas, services, repositories, and tests to eliminate manual boilerplate while enforcing strict typing and consistent structure across different domain models like Projects, Costs, and Users.

How do I determine whether a backend entity should be Simple, Versionable, or Branchable?

You can scaffold both unit and integration tests for new backend entities. The system provides specific guidance for applying EVCS patterns to test generation, ensuring strict typing and consistent structure across the domain models, repositories, and service layers.

Does this backend entity generation approach work with existing SQLAlchemy base classes and mixins?

Yes, this approach works with SQLAlchemy base classes and mixins by automatically generating models that enforce strict typing and integrate EVCS patterns. It scaffolds the service layer and repositories using proper base classes to ensure consistent structure across domain models.

What is the best way to scaffold a service layer and repository for a new domain entity?

The best way to scaffold a service layer and repository is to define the entity scope and let the system automatically generate the boilerplate following EVCS patterns. It produces service layers with proper base classes and optional repository scaffolding alongside Pydantic schemas and SQLAlchemy models.