---
# ─────────────────────────────────────────────────────────────────────────────
#  .github/prompts/scaffold-service-module.prompt.md  ·  reusable prompt file
#  QRefAI AI Coding Field Guide, Part 3 (Q3.3)
#
#  Prompt files are reusable, invokable prompts. They show up as SLASH COMMANDS in
#  the IDE (here: /scaffold-service-module). Good for repeatable chores — scaffolds,
#  boilerplate, repetitive refactors — done your way every time.
#
#  Supported in VS Code, Visual Studio, and JetBrains. In harness terms, prompt
#  files map roughly to Claude slash commands.
#
#  Frontmatter:
#    description  shown in the slash-command picker
#    tools        the tool surface this prompt may use while running
# ─────────────────────────────────────────────────────────────────────────────
description: Scaffold a new service module following the project template.
tools: [codebase, search, editFiles, runCommands]
---

Scaffold a new service module named `${input:moduleName}` following this project's
conventions.

Steps:
  1. Create the standard folder layout under `internal/${input:moduleName}/`
     (domain / transport / store), matching an existing module as the reference.
  2. Wire the module into the service registry.
  3. Add a placeholder test file with the project's test naming convention.
  4. Add an entry to `docs/api-changelog.md` if a public endpoint is introduced.

Follow every rule in copilot-instructions.md and any path-scoped instructions that
apply. Do not invent a new structure — mirror the closest existing module.

<!--
  NOTE: ${input:name} prompts the user for a value when the slash command runs.
  Keep prompt files task-shaped and bounded; anything that needs judgment or a
  persona belongs in a chat mode or a custom agent instead.
-->