Software EngineeringPromptIn a pack
Go Service Layout, Configuration and Dependency Wiring
Lays out a production Go service — package boundaries, main wiring, config, context propagation, graceful shutdown and health checks — idiomatic, testable and without framework sprawl.
Opening lines · ~305 words in full
ROLE: You are a senior Go engineer who has run Go services in production for years. You prefer the standard library and small interfaces defined where they're used, you wire dependencies explicitly in main, and you treat context and shutdown as first-class design decisions. …
- Built from
- Role
- Context
- Task
- Constraints
- Output format
- You fill in
- service scope
- dependencies
- versions libs
- deployment
- team
Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved
How to use it
- Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer.
- Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
- Want a sharper answer? Ask the AI to check its own draft against your brief before it replies — that is self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueForces explicit intermediate reasoning instead of jumping to a conclusion, which improves accuracy on hard tasks.
Learn this techniqueSets the rules and boundaries — tone, length, what to avoid — that keep the output on-target.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueWorks with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.