backend-dev

Generate OpenAPI 3.x specifications, service layer scaffolds, error catalogs, and repository patterns.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ivegamsft/work-tracker --skill backend-dev-ivegamsft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-dev
Source: https://github.com/ivegamsft/work-tracker/tree/main/.agents/skills/backend-dev
Command: npx skills add https://github.com/ivegamsft/work-tracker --skill backend-dev-ivegamsft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines backend development by providing templates for API specifications, service layers, error catalogs, and repository patterns, reducing the time spent on repetitive coding tasks.

Core Features & Use Cases

  • API Spec Templates: Offers a structured template for creating OpenAPI 3.x specifications for new API resources.
  • Service Layer Scaffold: Provides a template for creating service layers with dependency injection, error handling, and logging stubs.
  • Error Catalog Structure: Assists in defining structured error codes and messages with HTTP status codes and resolution hints.
  • Repository Pattern Boilerplate: Includes a template for a data access repository pattern adaptable to any ORM or query builder.
  • Use Case: For a developer starting a new API project, this Skill can be used to quickly set up a solid foundation for API design, service layer, and error handling.

Quick Start

Use the backend-dev skill to create a new API endpoint using the API spec template.

Frequently Asked Questions about backend-dev

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

FAQPage Schema
How do I generate an OpenAPI 3.x specification for a new API resource?

To generate an OpenAPI 3.x specification, this Skill provides structured templates that automate the creation of API specs for new resources, ensuring proper endpoint documentation and standardized REST or GraphQL API design.

What is the best way to implement an ORM-agnostic repository pattern?

The best way to implement an ORM-agnostic repository pattern is using the included boilerplate template, which provides a flexible data access structure adaptable to any ORM or query builder without locking you into a specific database framework.

Does this backend development template work for both REST and GraphQL APIs?

Yes, the backend development templates are explicitly designed for developers implementing both REST and GraphQL APIs, providing foundational scaffolds for API specifications, service layers, and data access patterns across either protocol.

Can I use these repository pattern templates with any query builder or ORM?

Yes, you can use these repository pattern templates with any query builder or ORM, as the boilerplate is specifically designed to be ORM-agnostic, allowing you to adapt the data access layer to your existing database tools.