Skill: billchirico/discord-markdown (version 1.0.0)

--- name: discord-markdown description: Format text for Discord using markdown syntax. Use when composing Discord messages, bot responses, embed descriptions, forum posts, webhook payloads, or any content destined for Discord's chat interface. Triggers on requests mentioning Discord formatting, Discord messages, Discord bots, Discord embeds, or when the user needs text styled for Discord's rendering engine. Covers bold, italic, underline, strikethrough, spoilers, code blocks with syntax highlighting, headers, subtext, lists, block quotes, masked links, timestamps, and mentions. Always presents Discord-ready messages inside fenced code blocks so the user can copy-paste them directly into Discord with all markdown formatting preserved. --- # Discord Markdown Formatting Format text for Discord's chat rendering engine. Discord uses a modified subset of Markdown with some unique additions (spoilers, timestamps, subtext, guild navigation). ## Output Presentation — CRITICAL When composing a Discord message for the user, **always present the final message inside a fenced code block** so the user can copy-paste it directly into Discord with all markdown formatting intact. **Why:** Claude's chat interface renders markdown (e.g., `**bold**` becomes **bold**). If the user copies rendered text, the markdown syntax is stripped and the message loses its formatting when pasted into Discord. A code block preserves the raw syntax. ### How to Present Discord Messages Always wrap the final copy-paste-ready message in a fenced code block with the `markdown` language tag: ```` ```markdown # 🚀 Announcement **This is bold** and ~~this is struck~~ and ||this is a spoiler|| > Block quote here -# Subtext footer ``` ```` ### Rules 1. **Always use a fenced code block** — Triple backticks with `markdown` language identifier 2. **The ENTIRE message goes in ONE block** — Everything the user will paste into Discord lives inside a single fenced code block. No part of the Discord message should ever appear outside the block as rendered markdown 3. **Explain outside the block** — Put any notes, options, or context _before_ or _after_ the code block, never inside it 4. **Handle nested code blocks** — If the Discord message itself contains code blocks, use four backticks (``````) as the outer fence so the inner triple backticks are preserved. The user copies everything between the outer fence — the inner triple backticks are part of the Discord message: ````` ````markdown Here's some code: ```javascript console.log("hello"); ``` Pretty cool right? ```` ````` 5. **Multiple messages = multiple blocks** — If providing alternatives or a multi-message sequence, use a separate code block for each with a label above it 6. **Message metadata summary** — Always display a metadata summary table immediately after every Discord message code block (see below) 7. **Templates too** — When presenting templates from the reference files, they should also be in copyable code blocks following these same rules 8. **Never partially render** — Do NOT put headers, bold text, code snippets, or any other Discord-formatted content outside the code block. If it's part of the Discord message, it goes inside the block. The user should never have to assemble a message from rendered markdown and code blocks ### Message Metadata Summary After **every** Discord message code block, include a summary table with the following stats: | Stat | Description | How to Count | | -------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **Characters** | Total character count of the message | Count all characters inside the code block. Show as `X / 2,000` for chat messages or `X / 4,096` for embed descriptions | | **Sections** | Number of header-delimited sections | Count all `#`, `##`, `###` headers. If no headers, show `0` | | **User Mentions** | Users mentioned via `<@USER_ID>` or `<@!USER_ID>` | Count unique `<@...>` patterns (not role mentions) | | **Role Mentions** | Roles mentioned via `<@&ROLE_ID>` | Count unique `<@&...>` patterns. Include `@everyone` and `@here` | | **Channel Mentions** | Channels linked via `<#CHANNEL_ID>` or `<id:...>` | Count unique `<#...>` and `<id:...>` patterns | | **URLs** | Links in the message | Count raw URLs and masked links `[text](url)` | | **Code Blocks** | Code blocks with language info | If the message contains fenced code blocks, list languages used (e.g., `javascript`, `bash`). Show `—` if none | Format the summary as a compact table directly below the code block: ``` | Stat | Value | |--------------------|----------------| | Characters | 437 / 2,000 | | Sections | 3 | | User Mentions | 1 | | Role Mentions | 1 (@everyone) | | Channel Mentions | 0 | | URLs | 0 | | Code Blocks | — | ``` **Notes:** - For role mentions, parenthetically note if `@everyone` or `@here` is included since those ping the entire server - For code blocks, list each language, e.g. `javascript, bash` — or `(no lang)` if the block has no language identifier - If characters exceed 80% of the limit, add a ⚠️ warning - If characters exceed the limit, add a 🚫 and suggest splitting the message ### Example Interaction **User:** "Write me a Discord announcement about a new SDK release that includes code examples" **Claude's response should look like:** Here's your SDK announcement: ````markdown # 🚀 Volvox SDK v2.0 — Breaking Changes Hey @everyone — we just shipped **v2.0** of the SDK and there are a few things you need to know before upgrading. ## What Changed The `createJar` method now accepts an options object instead of positional arguments: **Before:** ```ts const jar = createJar("Lunch Spots", ["Chipotle", "Sweetgreen"], true); ``` **After:** ```ts const jar = createJar({ name: "Lunch Spots", options: ["Chipotle", "Sweetgreen"], allowDuplicates: true, }); ``` ## New: Shake Events ```ts jar.on("shake", (result) => { console.log(`🎉 Selected: ${result.option}`); }); ``` > 💡 Full migration guide pinned in <#dev-resources> Drop questions in <#sdk-support> — <@core-team> is standing by. 🫡 -# v2.0.0 • <t:1770537600:D> ```` | Stat | Value | | ---------------- | -------------------- | | Characters | 659 / 2,000 | | Sections | 3 | | User Mentions | 1 | | Role Mentions | 1 (@everyone) | | Channel Mentions | 2 | | URLs | 0 | | Code Blocks | 3 — `ts`, `ts`, `ts` | **Key:** Notice the outer fence uses four backticks (``````) because the Discord message contains inner triple-backtick code blocks. The user copies everything between the outer fence — inner backticks are part of the message. --- ## Quick Reference | Style | Syntax | Renders As | | --------------------- | -------------------- | -------------------- | | Bold | `**text**` | **text** | | Italic | `*text*` or `_text_` | _text_ | | Underline | `__text__` | underlined text | | Strikethrough | `~~text~~` | ~~text~~ | | Spoiler | `\|\|text\|\|` | hidden until clicked | | Inline code | `` `code` `` | monospaced | | Bold italic | `***text***` | **_text_** | | Underline italic | `__*text*__` | underlined italic | | Underline bold | `__**text**__` | underlined bold | | Underline bold italic | `__***text***__` | all three | | Strikethrough bold | `~~**text**~~` | struck bold | ## Text Formatting ### Emphasis ``` *italic* or _italic_ **bold** ***bold italic*** __underline__ ~~strikethrough~~ ||spoiler text|| ``` ### Combining Styles Nest formatting markers from outside in. Discord resolves them in this order: underline → bold → italic → strikethrough. ``` __**bold underline**__ __*italic underline*__ __***bold italic underline***__ ~~**bold strikethrough**~~ ~~__**bold underline strikethrough**__~~ ||**bold spoiler**|| ``` ### Escaping Prefix any markdown character with `\` to display it literally: ``` \*not italic\* \*\*not bold\*\* \|\|not a spoiler\|\| ``` ## Headers Headers require `#` at the **start of a line** followed by a space. Only three levels are supported. ``` # Large Header ## Medium Header ### Small Header ``` **Important:** Headers do not work inline. The `#` must be the first character on the line. ## Subtext Small, muted gray text below content. Useful for footnotes, disclaimers, or attribution. ``` -# This renders as subtext ``` ## Block Quotes ### Single-line ``` > This is a single block quote ``` ### Multi-line Everything after `>>>` (including subsequent lines) becomes quoted: ``` >>> This entire block including this line and this line are all quoted ``` ## Lists ### Unordered Use `-` or `*` with a space. Indent with spaces for nesting: ``` - Item one - Item two - Nested item - Another nested item - Deep nested ``` ### Ordered ``` 1. First item 2. Second item 3. Third item ``` **Auto-numbering trick:** Discord auto-increments if you repeat `1.`: ``` 1. First 1. Second (renders as 2.) 1. Third (renders as 3.) ``` ## Code Blocks ### Inline Code ``` Use `inline code` for short snippets ``` ### Multi-line Code Block Wrap code with triple backticks on their own lines: ```` ``` function hello() { return "world"; } ``` ```` ### Syntax Highlighting Add a language identifier after the opening backticks: ```` ```javascript function hello() { return "world"; } ``` ```` See [references/syntax-highlighting.md](references/syntax-highlighting.md) for the full list of supported languages. **Commonly used languages:** `javascript`, `typescript`, `python`, `csharp`, `json`, `bash`, `css`, `html`, `sql`, `yaml`, `diff`, `markdown` ## Links ### Masked Links ``` [Click here](https://example.com) ``` **Note:** Masked links work in embeds and some contexts, but regular chat may show a preview. Discord may suppress masked links from bots in certain conditions. ### Auto-linking Discord auto-links any valid URL pasted directly: ``` Check out https://example.com for more info ``` ### Suppressing Link Previews Wrap a URL in angle brackets to prevent Discord from generating a preview embed: ``` <https://example.com> ``` ## Timestamps Dynamic timestamps that display in each user's local timezone. **Format:** `<t:UNIX_TIMESTAMP:FORMAT_FLAG>` | Flag | Output Style | Example | | ---- | ------------------------- | ---------------------------------- | | `t` | Short time | `4:20 PM` | | `T` | Long time | `4:20:30 PM` | | `d` | Short date | `02/08/2026` | | `D` | Long date | `February 8, 2026` | | `f` | Short date/time (default) | `February 8, 2026 4:20 PM` | | `F` | Long date/time | `Sunday, February 8, 2026 4:20 PM` | | `R` | Relative | `2 hours ago` | **Example:** ``` Event starts <t:1770537600:F> That was <t:1770537600:R> ``` **Tip:** Use `Math.floor(Date.now() / 1000)` or `date +%s` to get the current Unix timestamp. ## Mentions & References ``` <@USER_ID> → @username mention <@!USER_ID> → @username mention (nickname format) <@&ROLE_ID> → @role mention <#CHANNEL_ID> → #channel link <id:browse> → Browse Channels link <id:customize> → Customize Community link <id:guide> → Server Guide link <id:linked-roles> → Linked Roles link ``` ## Emoji ``` :emoji_name: → Standard/custom emoji <:emoji_name:EMOJI_ID> → Custom emoji <a:emoji_name:EMOJI_ID> → Animated custom emoji ``` ## Discord-Specific Gotchas 1. **No nested block quotes** — Discord does not support `>>` for nested quotes 2. **Headers need line start** — `#` must be the first character on the line (not inline) 3. **Underline is NOT standard Markdown** — `__text__` underlines in Discord but bolds in standard Markdown 4. **Spoilers are Discord-only** — `||text||` has no equivalent in standard Markdown 5. **Lists need a blank line** — Start lists after a blank line or they may not render 6. **Embed markdown differs** — Some formatting behaves differently in embeds vs chat messages 7. **2000 character limit** — Standard messages max at 2,000 characters; nitro users get 4,000 8. **Embed description limit** — Embed descriptions max at 4,096 characters 9. **Code block language names are case-insensitive** — `JS`, `js`, and `JavaScript` all work ## Formatting for Different Contexts > **Reminder:** Regardless of context, always present the final Discord-ready message inside a fenced code block so the user can copy-paste it directly. See "Output Presentation" above. ### Chat Messages Full markdown support. 2,000 character limit (4,000 with Nitro). ### Embed Descriptions Full markdown support. 4,096 character limit. Masked links work reliably here. ### Embed Field Values Limited markdown. 1,024 character limit per field. ### Bot Messages / Webhooks Full markdown support. Same as chat messages. Use embeds for richer formatting. ### Forum Posts Full markdown support in the post body. Title is plain text only. ## Resources - **Syntax highlighting:** [references/syntax-highlighting.md](references/syntax-highlighting.md) — full list of supported languages with examples - **Templates:** [references/templates.md](references/templates.md) — copy-paste templates for common Discord formatting patterns

path: references/syntax-highlighting.md
content: # Syntax Highlighting Languages

Discord uses highlight.js for code block syntax highlighting. Add the language identifier after the opening triple backticks.

## Usage

````
```language
your code here
```
````

## Supported Languages

### Web & Frontend

| Language   | Identifiers        | Notes         |
| ---------- | ------------------ | ------------- |
| JavaScript | `javascript`, `js` |               |
| TypeScript | `typescript`, `ts` |               |
| HTML       | `html`, `xml`      | Shared parser |
| CSS        | `css`              |               |
| JSON       | `json`             |               |
| Markdown   | `markdown`, `md`   |               |

### Backend & General Purpose

| Language | Identifiers        | Notes |
| -------- | ------------------ | ----- |
| Python   | `python`, `py`     |       |
| C#       | `csharp`, `cs`     |       |
| C++      | `cpp`, `c++`, `cc` |       |
| C        | `c`                |       |
| Java     | `java`             |       |
| Go       | `go`, `golang`     |       |
| Rust     | `rust`, `rs`       |       |
| Ruby     | `ruby`, `rb`       |       |
| PHP      | `php`              |       |
| Swift    | `swift`            |       |
| Kotlin   | `kotlin`, `kt`     |       |
| Scala    | `scala`            |       |
| R        | `r`                |       |
| Perl     | `perl`, `pl`       |       |
| Lua      | `lua`              |       |
| Haskell  | `haskell`, `hs`    |       |
| Elixir   | `elixir`           |       |
| Erlang   | `erlang`           |       |
| Clojure  | `clojure`, `clj`   |       |
| OCaml    | `ocaml`, `ml`      |       |
| F#       | `fsharp`, `fs`     |       |

### Shell & Scripting

| Language     | Identifiers                  | Notes |
| ------------ | ---------------------------- | ----- |
| Bash         | `bash`, `sh`, `shell`, `zsh` |       |
| PowerShell   | `powershell`, `ps`, `ps1`    |       |
| Batch        | `batch`, `bat`, `cmd`        |       |
| CoffeeScript | `coffeescript`, `coffee`     |       |
| AutoHotkey   | `autohotkey`, `ahk`          |       |

### Data & Config

| Language | Identifiers         | Notes |
| -------- | ------------------- | ----- |
| YAML     | `yaml`, `yml`       |       |
| TOML     | `toml`              |       |
| INI      | `ini`               |       |
| XML      | `xml`               |       |
| SQL      | `sql`               |       |
| GraphQL  | `graphql`, `gql`    |       |
| Protobuf | `protobuf`, `proto` |       |

### DevOps & Infrastructure

| Language   | Identifiers              | Notes |
| ---------- | ------------------------ | ----- |
| Dockerfile | `dockerfile`, `docker`   |       |
| Nginx      | `nginx`                  |       |
| Apache     | `apache`, `apacheconf`   |       |
| Terraform  | `terraform`, `tf`, `hcl` |       |

### Markup & Documentation

| Language | Identifiers        | Notes |
| -------- | ------------------ | ----- |
| LaTeX    | `latex`, `tex`     |       |
| AsciiDoc | `asciidoc`, `adoc` |       |

### Assembly

| Language      | Identifiers     | Notes |
| ------------- | --------------- | ----- |
| x86 Assembly  | `x86asm`        |       |
| ARM Assembly  | `armasm`, `arm` |       |
| AVR Assembly  | `avrasm`        |       |
| MIPS Assembly | `mipsasm`       |       |
| LLVM IR       | `llvm`          |       |

### Special Purpose

| Language  | Identifiers                | Notes                                  |
| --------- | -------------------------- | -------------------------------------- |
| Diff      | `diff`                     | Shows added/removed lines in green/red |
| Fix       | `fix`                      | FIX protocol                           |
| GLSL      | `glsl`                     | OpenGL shading language                |
| Prolog    | `prolog`                   |                                        |
| XL        | `xl`                       | Extensible language                    |
| Plaintext | `text`, `plaintext`, `txt` | No highlighting                        |

## Diff Highlighting

The `diff` language is particularly useful for showing changes:

````
```diff
- removed line (shows in red)
+ added line (shows in green)
  unchanged line
```
````

## Tips

1. **Language identifiers are case-insensitive** — `Python`, `python`, `py` all work
2. **No language = no highlighting** — Omit the identifier for plain monospace text
3. **Unknown languages fall back to plaintext** — Won't error, just won't highlight
4. **ANSI coloring** — Use `ansi` identifier for ANSI escape code rendering (limited support)
5. **Keep blocks short** — Very long code blocks may get cut off in mobile clients


path: references/templates.md
content: # Discord Formatting Templates

Copy-paste templates for common Discord formatting patterns. Replace placeholder content with your own.

## Announcements

> **Note:** Announcement templates include `@everyone` to notify the whole server. Remove it if you only want to post without pinging, or replace with `@here` (online members only) or a role mention like `<@&ROLE_ID>`.

### Feature Release

```
# 🚀 New Feature: [Feature Name] @everyone

We just shipped **[feature name]** — here's what it does:

- **[Benefit 1]** — brief description
- **[Benefit 2]** — brief description
- **[Benefit 3]** — brief description

> Try it now: [instructions or link]

-# Released [date] • Questions? Ask in <#CHANNEL_ID>
```

### Maintenance Notice

```
# ⚠️ Scheduled Maintenance @everyone

**When:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)
**Duration:** ~[X] minutes
**Impact:** [what will be unavailable]

> We'll update this channel when maintenance is complete.

-# Last updated <t:UNIX_TIMESTAMP:R>
```

### App / Product Launch

```
# 🎊 [App Name] is Live! @everyone

After [X months/weeks] of building, **[App Name]** is officially available on [platforms].

### What is it?
[One paragraph elevator pitch]

### Key Features
- **[Feature 1]** — [short description]
- **[Feature 2]** — [short description]
- **[Feature 3]** — [short description]

### Download / Try It
- 📱 iOS: [link]
- 🤖 Android: [link]
- 🌐 Web: [link]

> 🐛 Found a bug? Report it in <#CHANNEL_ID>
> 💡 Feature request? Drop it in <#CHANNEL_ID>

-# Built by <@USER_ID> • v1.0.0
```

### Giveaway / Contest

```
# 🎁 GIVEAWAY: [Prize Name] @everyone

**Prize:** [description of what they win]
**Winners:** [X] winner(s)
**Ends:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)

### How to Enter
1. React to this message with 🎉
2. [Optional: Follow @account]
3. [Optional: Invite a friend]

### Rules
- Must be a member of this server
- One entry per person
- Winner announced in <#CHANNEL_ID>

> *No purchase necessary. ||Winner selected randomly via [tool].||*

-# Hosted by <@USER_ID> • Good luck!
```

### Sale / Discount

```
# 💰 [Sale Name] — [X]% Off
@everyone

**What:** [product/service] is on sale
**Discount:** [details — code, automatic, etc.]
**Expires:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)

> 🛒 **Grab it here:** [link]

-# Limited time • No stacking with other offers
```

### Hiring / Open Position

```
# 📢 We're Hiring: [Role Title] @everyone

**Team:** [team name]
**Type:** [Full-time / Part-time / Contract]
**Location:** [Remote / City / Hybrid]
**Compensation:** [range or "competitive"]

### What You'll Do
- [Responsibility 1]
- [Responsibility 2]
- [Responsibility 3]

### What We're Looking For
- [Requirement 1]
- [Requirement 2]
- [Nice-to-have]

### How to Apply
> [Instructions — DM, link, email, etc.]

-# Applications close <t:UNIX_TIMESTAMP:D> • Questions? Ask <@USER_ID>
```

## Community & Moderation

### Rules / Guidelines

```
# 📋 Server Rules

### 1. Be Respectful
Treat everyone with dignity. No harassment, hate speech, or personal attacks.

### 2. Stay On Topic
Use the right channels. Check <id:browse> to find the right place.

### 3. No Spam
No unsolicited DMs, repeated messages, or self-promotion without permission.

### 4. Follow Discord TOS
> https://discord.com/terms

-# Updated <t:UNIX_TIMESTAMP:D> • Violations may result in mute or ban
```

### Welcome Message

```
# 👋 Welcome to [Server Name]!

Hey <@USER_ID>, glad you're here! Here's how to get started:

1. Read the rules in <#CHANNEL_ID>
2. Grab your roles in <id:customize>
3. Introduce yourself in <#CHANNEL_ID>
4. Check out <id:guide> for a full walkthrough

> **Need help?** Ping <@&ROLE_ID> anytime.
```

### Role Directory

```
# 🏷️ Role Directory

### Staff
- <@&ROLE_ID> — Server owner and administrators
- <@&ROLE_ID> — Community moderators

### Member Tiers
- <@&ROLE_ID> — New members (default)
- <@&ROLE_ID> — Active contributors (earned at [criteria])
- <@&ROLE_ID> — Veteran members (earned at [criteria])

### Opt-In Roles
Grab these in <id:customize>:
- <@&ROLE_ID> — Get pinged for [topic]
- <@&ROLE_ID> — Get pinged for [topic]
- <@&ROLE_ID> — Get pinged for [topic]

-# Roles managed by <@&ROLE_ID>
```

### Warning / Strike Notice

```
## ⚠️ Moderation Notice

**User:** <@USER_ID>
**Action:** [Verbal Warning / Mute / Temp Ban / Ban]
**Duration:** [if applicable]
**Reason:** [brief description of violation]

**Rule violated:** Rule #[X] — [rule name]

> [Quote of offending message or description of behavior]

-# Logged by <@USER_ID> • <t:UNIX_TIMESTAMP:f> • Strike [X] of [Y]
```

### Application / Form Template

```
# 📝 [Role/Position] Application

Copy this template and DM it to <@USER_ID> or post in <#CHANNEL_ID>.

```

**Discord Username:**
**Timezone:**
**Age (if required):**

**Why are you interested?**
[Your answer]

**Relevant experience:**
[Your answer]

**How active are you?**
[Your answer]

**Anything else we should know?**
[Your answer]

```

-# Applications reviewed within [X] days
```

### Partnership / Collab Request

```
## 🤝 Partnership Proposal

**Server/Brand:** [name]
**Size/Reach:** [member count, followers, etc.]
**Website:** [link]

### What We're Proposing
[Description of partnership — cross-promotion, event collab, shared project, etc.]

### What We Bring
- [Value 1]
- [Value 2]

### What We're Looking For
- [Value 1]
- [Value 2]

> **Interested?** DM <@USER_ID> or reply below.

-# Submitted <t:UNIX_TIMESTAMP:D>
```

### Server Boost Acknowledgment

```
# 💎 Thank You, Boosters!

Our server is at **Level [1/2/3]** with **[X] boosts** thanks to these legends:

<@USER_ID> • <@USER_ID> • <@USER_ID>

### Current Perks Unlocked
- ✅ [Perk 1 — e.g., 128kbps audio]
- ✅ [Perk 2 — e.g., custom banner]
- ✅ [Perk 3 — e.g., 50 emoji slots]

### Next Level ([X] more boosts)
- ⬜ [Next perk]
- ⬜ [Next perk]

-# Boost perks: https://discord.com/nitro
```

## Development & Technical

### Bug Report Template

````
## 🐛 Bug Report

**Summary:** [one-line description]

**Steps to Reproduce:**
1. Go to [location]
2. Click on [element]
3. Observe [unexpected behavior]

**Expected:** [what should happen]
**Actual:** [what happens instead]

**Environment:**
- OS: [e.g., Windows 11, macOS 14]
- Version: [e.g., v1.2.3]
- Browser: [if applicable]

```error log
paste relevant error output here
````

-# Reported by @username • <t:UNIX_TIMESTAMP:d>

```

### Code Review / PR Summary
```

## 📝 PR Summary: [PR Title]

**Branch:** `feature/branch-name` → `main`
**Changes:** [brief description]

### What Changed

- **[File/Area]** — [description of change]
- **[File/Area]** — [description of change]

### Testing

```bash
npm test           # ✅ All passing
npm run lint       # ✅ No warnings
npm run typecheck  # ✅ Clean
```

> **Review link:** [URL]

-# Ready for review • cc <@USER_ID>

```

### Changelog
```

# 📦 v[X.Y.Z] Changelog

### ✨ New

- [Feature description]
- [Feature description]

### 🐛 Fixes

- Fixed [issue description]
- Fixed [issue description]

### 🔧 Changes

- [Change description]
- [Change description]

### ⚠️ Breaking

- [Breaking change] — see ||migration guide in #channel||

-# Full diff: [link to release]

```

### API / Integration Docs
```

## 🔌 [API/Integration Name]

**Base URL:** `https://api.example.com/v1`
**Auth:** [API key / OAuth / Bearer token]
**Docs:** [link]

### Quick Start

```bash
curl -X GET https://api.example.com/v1/endpoint \
  -H "Authorization: Bearer YOUR_TOKEN"
```

### Common Endpoints

- `GET /resource` — list all
- `GET /resource/:id` — get one
- `POST /resource` — create
- `PATCH /resource/:id` — update

### Rate Limits

| Tier | Requests/min |
| ---- | ------------ |
| Free | 60           |
| Pro  | 300          |

> ❓ Issues? Post in <#CHANNEL_ID> with your error code.

-# Last updated <t:UNIX_TIMESTAMP:D>

```

### Outage / Incident Report
```

# 🔴 Incident Report: [Brief Title]

**Status:** 🔴 Investigating / 🟡 Identified / 🟢 Resolved
**Start:** <t:UNIX_TIMESTAMP:F>
**Resolved:** <t:UNIX_TIMESTAMP:F> / _ongoing_
**Duration:** [X hours/minutes]

### What Happened

[Clear explanation of the issue]

### Impact

[Who/what was affected]

### Timeline

- <t:TIMESTAMP:t> — [Event: issue detected]
- <t:TIMESTAMP:t> — [Event: root cause identified]
- <t:TIMESTAMP:t> — [Event: fix deployed]
- <t:TIMESTAMP:t> — [Event: confirmed resolved]

### Root Cause

||[Technical explanation — spoiler-tagged for non-technical readers]||

### Next Steps

- [ ] [Preventative measure 1]
- [ ] [Preventative measure 2]

-# Report by <@USER_ID> • Post-mortem in <#CHANNEL_ID>

```

### Feature Request Template
```

## 💡 Feature Request

**Title:** [Short, descriptive name]
**Priority:** 🔴 High / 🟡 Medium / 🟢 Low

### Problem

[What problem does this solve? Who has this problem?]

### Proposed Solution

[How should it work?]

### Alternatives Considered

[Other approaches you thought about]

### Additional Context

> [Mockups, screenshots, examples, or references]

-# Vote with 👍 if you want this • Submitted <t:UNIX_TIMESTAMP:d>

```

### Tech Stack / Architecture Overview
```

# 🏗️ Tech Stack

### Frontend

- **Framework:** [e.g., React Native / Expo]
- **Language:** [e.g., TypeScript]
- **Styling:** [e.g., NativeWind / Tailwind]

### Backend

- **Runtime:** [e.g., .NET 8]
- **Database:** [e.g., PostgreSQL via Supabase]
- **Auth:** [e.g., Supabase Auth]

### Infrastructure

- **Hosting:** [e.g., Cloudflare Workers]
- **CI/CD:** [e.g., GitHub Actions]
- **Monitoring:** [e.g., Sentry]

### Dev Tools

- `[tool]` — [purpose]
- `[tool]` — [purpose]
- `[tool]` — [purpose]

-# Updated <t:UNIX_TIMESTAMP:D> • Maintained by <@USER_ID>

```

## Events & Scheduling

### Event Announcement
```

# 🎉 [Event Name]

**When:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)
**Where:** [location / voice channel / link]
**What:** [description]

### Schedule

- <t:TIMESTAMP_1:t> — [Activity 1]
- <t:TIMESTAMP_2:t> — [Activity 2]
- <t:TIMESTAMP_3:t> — [Activity 3]

> **RSVP:** React with ✅ if you're coming!

-# Hosted by <@USER_ID>

```

### AMA (Ask Me Anything)
```

# 🎤 AMA with [Guest Name]

**Who:** [Brief bio — title, known for, etc.]
**When:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)
**Where:** <#CHANNEL_ID>

### How It Works

1. Drop your questions in this thread **before** the event
2. Upvote questions you want answered (react 👍)
3. [Guest] will answer live starting at <t:UNIX_TIMESTAMP:t>

### Topics They Can Cover

- [Topic 1]
- [Topic 2]
- [Topic 3]

> _Please keep questions respectful and on-topic._

-# Organized by <@USER_ID>

```

### Recurring Meeting / Standup
```

## 📅 [Meeting Name] — <t:UNIX_TIMESTAMP:D>

**Time:** <t:UNIX_TIMESTAMP:t> (<t:UNIX_TIMESTAMP:R>)
**Voice:** <#CHANNEL_ID>
**Agenda:** [link or see below]

### Agenda

1. [Topic 1] — [owner]
2. [Topic 2] — [owner]
3. Open floor

### Action Items from Last Meeting

- ✅ [Completed item] — <@USER_ID>
- 🔄 [In progress item] — <@USER_ID>
- ❌ [Not started] — <@USER_ID>

> Can't make it? Post your async update below.

-# Next meeting: <t:UNIX_TIMESTAMP:D>

```

### Workshop / Tutorial Session
```

# 🎓 Workshop: [Topic]

**Instructor:** <@USER_ID>
**When:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)
**Duration:** ~[X] minutes
**Skill Level:** 🟢 Beginner / 🟡 Intermediate / 🔴 Advanced

### What You'll Learn

- [Outcome 1]
- [Outcome 2]
- [Outcome 3]

### Prerequisites

- [Requirement 1 — e.g., Node.js installed]
- [Requirement 2 — e.g., basic JavaScript knowledge]

### Prep Work

> [Links to pre-read material, repos to clone, tools to install]

### Resources

- 📂 Repo: [link]
- 📝 Slides: [link]
- 🎥 Recording: _posted after the session_

-# React ✅ to reserve your spot • Limited to [X] attendees

```

### Game Night / Social Event
```

# 🎮 Game Night: [Game Name]

**When:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)
**Where:** <#CHANNEL_ID> voice
**Game:** [name] — [free/paid, platform]
**Players:** [min]-[max]

### How to Join

1. React ✅ below to sign up
2. Join <#CHANNEL_ID> at game time
3. [Any setup instructions — download, account, etc.]

> 🏆 **Prize:** [optional — bragging rights, role, etc.]

-# Hosted by <@USER_ID> • Casual vibes, all skill levels welcome

```

## Informational

### FAQ Entry
```

### ❓ [Question goes here?]

[Clear, concise answer.]

> **Example:**
> [example or demonstration]

-# See also: <#CHANNEL_ID>

```

### Status Update
```

## 📊 Status Update — [Project/Topic]

**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked

### Completed

- ✅ [Task 1]
- ✅ [Task 2]

### In Progress

- 🔄 [Task 3] — [brief status]
- 🔄 [Task 4] — [brief status]

### Blocked

- ❌ [Task 5] — blocked by [reason]

> **Next milestone:** <t:UNIX_TIMESTAMP:D>

-# Updated <t:UNIX_TIMESTAMP:R>

```

### Weekly Digest / Newsletter
```

# 📰 Weekly Digest — [Date Range]

### 🔥 Highlights

- [Big thing that happened this week]
- [Another notable event]

### 📈 Stats

- **New members:** [X]
- **Messages:** [X]
- **Most active channel:** <#CHANNEL_ID>

### 📝 Content Roundup

- [Article/video/resource] by <@USER_ID> — [brief description]
- [Article/video/resource] by <@USER_ID> — [brief description]

### 🗓️ Upcoming

- <t:TIMESTAMP:D> — [Event 1]
- <t:TIMESTAMP:D> — [Event 2]

### 💬 Quote of the Week

> "[memorable thing someone said]" — <@USER_ID>

-# Compiled by <@USER_ID> • See past digests in <#CHANNEL_ID>

```

### Tutorial / How-To Guide
```

# 📖 How to [Do the Thing]

### Overview

[1-2 sentence summary of what this guide covers]

### Step 1: [Action]

[Detailed instructions]

```
optional code block or example
```

### Step 2: [Action]

[Detailed instructions]

> 💡 **Tip:** [helpful tip for this step]

### Step 3: [Action]

[Detailed instructions]

### Common Issues

**Problem:** [description]
**Fix:** [solution]

**Problem:** [description]
**Fix:** [solution]

-# Written by <@USER_ID> • Feedback? Reply in thread

```

### Resource Collection / Link List
```

# 📚 [Topic] Resources

### Getting Started

- [Resource Name](URL) — [brief description]
- [Resource Name](URL) — [brief description]

### Intermediate

- [Resource Name](URL) — [brief description]
- [Resource Name](URL) — [brief description]

### Advanced

- [Resource Name](URL) — [brief description]
- [Resource Name](URL) — [brief description]

### Tools

- `[tool name]` — [what it does] — [link]
- `[tool name]` — [what it does] — [link]

> 📌 Have a resource to add? Reply in thread.

-# Curated by <@USER_ID> • Last updated <t:UNIX_TIMESTAMP:D>

```

### Feedback / Survey Request
```

# 📣 We Need Your Feedback!

**Topic:** [What you're gathering feedback on]
**Deadline:** <t:UNIX_TIMESTAMP:F> (<t:UNIX_TIMESTAMP:R>)

### Context

[Why are you asking? What will the feedback be used for?]

### Questions

1. [Question 1]
2. [Question 2]
3. [Question 3]

> **How to respond:** [Reply in thread / Fill out form / React below]
> 📋 **Form link:** [link if applicable]

-# All feedback is [anonymous/attributed] • Results shared in <#CHANNEL_ID>

```

### Pricing / Tier Comparison
```

# 💎 [Product/Service] Plans

### 🟢 Free

- [Feature 1]
- [Feature 2]
- [Limitation]

### 🔵 Pro — $[X]/mo

- Everything in Free, plus:
- [Feature 3]
- [Feature 4]
- [Higher limit]

### 🟣 Enterprise — Contact us

- Everything in Pro, plus:
- [Feature 5]
- [Feature 6]
- [Custom support]

> 🛒 **Get started:** [link]
> ❓ **Questions:** <#CHANNEL_ID> or DM <@USER_ID>

-# Prices in USD • Updated <t:UNIX_TIMESTAMP:D>

```

### Onboarding Checklist
```

# ✅ [Server/Project] Onboarding

Welcome! Complete these steps to get set up:

### Account Setup

- [ ] Read server rules in <#CHANNEL_ID>
- [ ] Grab your roles in <id:customize>
- [ ] Set your server nickname to [format]

### Get Connected

- [ ] Introduce yourself in <#CHANNEL_ID>
- [ ] Join the <#CHANNEL_ID> voice chat
- [ ] Follow <#CHANNEL_ID> for updates

### [Project-Specific]

- [ ] Clone the repo: `git clone [URL]`
- [ ] Set up your environment: see <#CHANNEL_ID>
- [ ] Say hi in <#CHANNEL_ID>

> **Stuck?** Ping <@&ROLE_ID> — we don't bite. Usually.

-# Last updated <t:UNIX_TIMESTAMP:D>

```

## Social Media & Content

### Content Drop / Creator Post
```

# 🎬 New [Video/Article/Podcast]: [Title]

**By:** <@USER_ID>
**Link:** [URL]
**Length:** [duration / read time]

### What It Covers

[2-3 sentence summary of the content]

> 💬 **Discussion:** React with your thoughts or reply in thread!

-# Posted <t:UNIX_TIMESTAMP:R> • Support the creator: [link]

```

### Social Media Cross-Post
```

## 📱 Follow Us Everywhere

Stay in the loop across all platforms:

- 🐦 **X/Twitter:** [@handle](https://x.com/handle)
- 📸 **Instagram:** [@handle](https://instagram.com/handle)
- 📺 **YouTube:** [Channel Name](https://youtube.com/@handle)
- 💼 **LinkedIn:** [Page Name](https://linkedin.com/company/name)
- 🌐 **Website:** [domain.com](https://domain.com)
- 📧 **Newsletter:** [Subscribe](https://link)

> 🔔 Turn on notifications so you never miss an update!

-# Links verified <t:UNIX_TIMESTAMP:D>

```

### Testimonial / Social Proof
```

# ⭐ What People Are Saying

> "[Testimonial quote 1]"
> — **[Name]**, [Title/Context]

> "[Testimonial quote 2]"
> — **[Name]**, [Title/Context]

> "[Testimonial quote 3]"
> — **[Name]**, [Title/Context]

-# Want to share your experience? DM <@USER_ID>

```

## Marketplace & Services

### Commission / Service Listing
```

# 🎨 [Service Type] — Open for Commissions

**Artist/Provider:** <@USER_ID>
**Portfolio:** [link]

### Tiers

- **Basic** — $[X] — [what's included]
- **Standard** — $[X] — [what's included]
- **Premium** — $[X] — [what's included]

### Turnaround

- Basic: [X] days
- Standard: [X] days
- Premium: [X] days

### Terms

- [Payment method — PayPal, etc.]
- [Revision policy]
- [Usage rights]

> **To order:** DM <@USER_ID> with [details needed]

-# Slots: [X] open • Status: 🟢 Open / 🔴 Closed

```

### Marketplace Listing
```

## 🏷️ [For Sale / For Trade / Free]

**Item:** [name/description]
**Condition:** [New / Used / Digital]
**Price:** $[X] / [trade for...] / Free
**Shipping:** [included / buyer pays / digital delivery]

[Optional: photo or screenshot link]

> **Interested?** React ✋ or DM <@USER_ID>

-# Listed <t:UNIX_TIMESTAMP:R> • [Server marketplace rules apply]

```

## Formatting Tricks

### Separator Line
Discord doesn't support `---` for horizontal rules. Use an empty block quote or code block as a visual separator:
```

\_ \_

```
Or use a unicode line:
```

─────────────────────

```

### Invisible Spacing
Use `_ _` (underscore, space, underscore) for an empty line that Discord won't collapse:
```

Line 1
\_ \_
Line 3 (with visible gap above)

```

### Color-Coded Text via Code Blocks
Discord doesn't support colored text natively, but `diff` blocks give you colored lines:
```

```diff
+ This line is green (added)
- This line is red (removed)
! This line is orange (in some themes)
# This line is gray (comment)
```

```

### Table-Like Formatting
Discord doesn't render markdown tables. Use code blocks for alignment:
```

```
Name        Role          Status
────────    ──────────    ────────
Alice       Admin         ✅ Online
Bob         Moderator     ⚫ Offline
Charlie     Member        🟡 Idle
```

````

### Embed-Like Formatting
Mimic embed styling using block quotes and formatting:
```
> ## 📌 Important Notice
>
> This is how you can simulate an embed-like
> appearance using block quotes and headers.
>
> **Field 1:** Value
> **Field 2:** Value
>
> *Footer text here*
```

### Progress Bar
Create visual progress bars using Unicode characters:
```
**Level Progress**
▓▓▓▓▓▓▓▓░░ 80%

**Upload Status**
█████████░ 90% complete
```

### Collapsible Content (Spoiler Sections)
Use spoiler tags to create expandable sections:
```
### Answers
||1. Answer to question one||
||2. Answer to question two||
||3. Answer to question three||

*Click to reveal each answer*
```

### Multi-Column Layout
Approximate columns with inline code and spacing:
````

```
🟢 ONLINE        🟡 IDLE          🔴 DND
───────────      ───────────      ───────────
Alice            Charlie          Eve
Bob              David            Frank
```

````

### Timestamp Quick Reference
Generate timestamps at [hammertime.cyou](https://hammertime.cyou) or [discordtimestamp.com](https://discordtimestamp.com):
```
Short time:    <t:1700000000:t>  →  2:13 PM
Long time:     <t:1700000000:T>  →  2:13:20 PM
Short date:    <t:1700000000:d>  →  11/14/2023
Long date:     <t:1700000000:D>  →  November 14, 2023
Full:          <t:1700000000:F>  →  November 14, 2023 2:13 PM
Relative:      <t:1700000000:R>  →  2 months ago
```

````


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)