add-service

Scaffold a DotMac Omni CRM service module with models, schemas, routes, and tests.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/michaelayoade/dotmac_crm --skill add-service-michaelayoade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-service
Source: https://github.com/michaelayoade/dotmac_crm/tree/main/.claude/skills/add-service
Command: npx skills add https://github.com/michaelayoade/dotmac_crm --skill add-service-michaelayoade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a consistent, production-ready service module structure so developers don’t have to manually wire models, schemas, services, routes, migrations, and tests from scratch.

Core Features & Use Cases

  • End-to-end scaffolding: Generates the full slice of a service module (model, service manager, schemas, API and web route patterns, and tests) to match existing conventions.
  • Domain-aware customization: Lets you provide a module name and purpose so the scaffold can be tailored to the entity’s domain (tickets, projects, CRM, etc.).
  • Workflow-ready verification: Includes guidance for linting, formatting, type-checking, and a minimal import sanity check before relying on the new code.

Quick Start

Use the add-service skill to scaffold a new CRM module by providing a module name and a one-line purpose like: "inventory reservations for stock management".

Frequently Asked Questions about add-service

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

FAQPage Schema
How do I scaffold a FastAPI service module with CRUD operations and Pydantic schemas?

Scaffolding a FastAPI service module generates a complete slice of architecture including SQLAlchemy models, Pydantic schemas, a service manager with CRUD and soft-delete behavior, and matching API route patterns, eliminating manually wiring boilerplate code from scratch.

What is the best way to generate boilerplate architecture for a new domain entity in an existing app?

Generating boilerplate architecture for a new entity requires providing a module name and purpose to produce an end-to-end service module, automatically matching existing app/models, app/services, app/schemas, and route conventions for consistent code organization.

Does scaffolding a service module include Alembic migrations and tests for immediate verification?

Scaffolding a service module includes producing an Alembic migration and tests workflow for immediate verification, alongside guidance for linting, formatting, type-checking, and a minimal import sanity check before relying on the new code.

Can I customize the scaffolded CRM module for specific domains like tickets or inventory reservations?

Customizing the scaffolded CRM module for domains like tickets or inventory reservations is supported through domain-aware customization, where you provide a module name and purpose so generated models, schemas, and routes are tailored to that entity.

What limitations should I expect when relying on a scaffolded service module for code organization?

Limitations of a scaffolded service module include strict adherence to established app/models, app/services, app/schemas, and route conventions, meaning the deterministic structure expects these specific architectural patterns rather than supporting arbitrary custom layouts.