backend

Implement consistent Go backend features using HARP patterns across all layers.

5|3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/hackutd/harp --skill backend-hackutd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/hackutd/harp/tree/main/.claude/skills/backend
Command: npx skills add https://github.com/hackutd/harp --skill backend-hackutd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates guesswork when extending the HARP Go backend by providing consistent architectural patterns for database changes, storage logic, handlers, routes, tests, and API documentation.

Core Features & Use Cases

  • Pattern-Based Backend Development: Select and implement CRUD, self-resource, pagination, workflow queue, file storage, public API, bulk operation, status update, settings, and stats patterns.
  • Convention Enforcement: Apply HARP standards for raw SQL, migrations, JSON envelopes, validation, error mapping, role-based routes, timeouts, mocks, Swagger annotations, and structured logging.
  • Use Case: Add a new admin-managed resource with migrations, store interfaces, mock implementations, handlers, protected routes, comprehensive tests, and regenerated Swagger documentation while matching existing codebase conventions.

Quick Start

Ask the backend skill to add the requested Go API feature and have it select the appropriate reference patterns, implement every required layer, and create the corresponding tests.

Frequently Asked Questions about backend

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

FAQPage Schema
How do I add CRUD endpoints with database migrations in a Go backend?

To add CRUD endpoints with database migrations in a Go backend, implement consistent architectural patterns across storage, handlers, routes, and raw SQL layers. This applies HARP standards for validation, JSON envelopes, and role-based authorization to ensure production-ready API features.

What is the best way to generate Swagger documentation for Go API handlers?

Generating Swagger documentation for Go API handlers requires applying Swagger annotations directly to your code. This approach enforces structured logging and automatically regenerates API documentation to match your newly implemented CRUD resources and routing conventions.

How do I set up handler testing and mocks for Go API CRUD operations?

Handler testing and mocks for Go API CRUD operations require implementing mock storage interfaces alongside your handlers. This enforces timeouts, structured logging, and role-based authorization rules while validating error mapping and JSON envelope responses across your endpoints.

Can I implement pagination and bulk operations using raw SQL in Go?

You can implement pagination and bulk operations using raw SQL in Go by selecting specific HARP reference patterns. This enforces direct database migrations, consistent JSON envelope responses, and structured logging for your production-ready API endpoints.

Does this Go backend pattern support workflow queues and file storage APIs?

This Go backend pattern supports workflow queues and file storage APIs by applying dedicated HARP patterns. It extends your storage logic, handlers, and routes while enforcing raw SQL, validation, error mapping, and Swagger annotations for these specific use cases.