alivirgo/major-ai-skills/use-good-answers-as-templates

┌─────────────────────────────────────────────────────────────┐
│                 Format Consistency Mechanics                │
│                                                             │
│  Descriptive Prose Specification (High Variance):           │
│  "Write a feature doc like the one you did yesterday with   │
│   a title, bullet points, parameters, and a code block."    │
│  ↳ Inconsistent header sizes, omitted parameter types       │
│                                                             │
│  Self-Exemplar Pattern Injection (Zero Variance):           │
│  <exemplar_format> [PASTE EXACT PAST WINNING POST] </exemplar>│
│  "Generate the entry for [NEW TOPIC] following this schema."│
│  ↳ 100% Identical Visual Hierarchy, Tone, & Depth           │
└─────────────────────────────────────────────────────────────┘

I want to write an entry for: **[NEW TOPIC / FEATURE NAME]**.
 
Below is a gold-standard reference example that I approved earlier. 
Follow its **exact visual layout, heading hierarchy, tone, and depth**:
 
<exemplar_format>
[PASTE YOUR FAVORITE PAST RESPONSE HERE]
</exemplar_format>
 
Input Data for [NEW TOPIC]:
[PASTE RAW NOTES / DATA FOR THE NEW ITEM]
 
Output the new entry strictly matching the exemplar structure.

Generate the API documentation for `PaymentService`:
 
<exemplar_format>
### `POST /v1/users`
**Description**: Creates a new user profile and triggers welcome email.
 
#### Request Headers
| Header | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| `Authorization` | Bearer Token | Yes | Scoped OAuth2 token |
 
#### Example Payload (JSON)

</exemplar_format>
 
Raw details for `PaymentService`: Endpoint `POST /v1/charges`, requires `Authorization` and `Idempotency-Key`, payload takes `amount` in cents and `currency`.