service-design

Installation
SKILL.md

Service Design

Design services around clear product ownership, explicit dependency direction, and business behavior that is testable independently of delivery and infrastructure concerns. Treat the Echo/Huma HTTP stack, persistence tools such as sqlc, and external vendors as components within that design—not as the application architecture.

Workflow

1. Inspect before designing

Read the repository tree, go.mod, application entry point, transport construction, one representative module, persistence configuration, tests, and repository guidance such as AGENTS.md and CODING_STANDARDS.md when present.

State assumptions and identify whether the task is:

  • adding behavior within an existing module;
  • introducing a new product module;
  • adding a transport, persistence, or vendor adapter;
  • correcting ownership/dependency drift;
  • deciding whether an existing module needs an internal capability boundary.

Do not impose the example tree mechanically. Existing explicit project decisions take precedence unless the user asks to change them.

Installs
42
First Seen
Oct 11, 2026