Links & mentions

Cabinet has three link surfaces: standard markdown links, wiki-links, and @-mentions for AI context.

Standard markdown links

Type [label](url) or paste any URL with text selected. Renders as a link, source stays plain markdown.

[Browse cabinets.sh ↗](https://cabinets.sh)

External URLs open in a new tab; internal ./relative/ and /absolute/ paths stay in-app.

Wiki-links

Type and start typing a page title. Cabinet autocompletes by slug.

See [[GTM Lead</a> for the launch ownership story.

Wiki-links resolve at build time (in the docs site) and at render time (in the app). If the target page is renamed, links don't break — Cabinet re-resolves by slug. Refactor your titles freely.

@-mentions in the AI panel

In the AI panel composer (or any agent task prompt) type @ and start typing:

FormWhat it attaches
@PageNameThe full page contents as agent context.
@folder/The folder's directory listing plus its index page.
@chat:slugA past conversation, by chat slug.
@agent:slugAnother agent's persona — useful when leads dispatch.
@skill:slugA skill, scoped to this run only.

Mentions become attached context tokens — the agent sees the file, but you don't have to copy-paste it.

AGENTS.md — the auto-attached context file

Drop an AGENTS.md at any folder root and Cabinet auto-attaches it to every agent run that touches that folder. Use it like a working agreement:

# Marketing — agent rules
- All launch artifacts live in /launches/.
- Default tone: direct, ≤3 sentences per recommendation.
- Always link competitor briefs by name (no <a data-wiki-link="true" href="#brief" class="wiki-link">Brief #</a>).
- Don't post to LinkedIn before legal review.

Cabinet treats AGENTS.md like a per-folder system prompt that augments (never replaces) the persona.

Page anchors

Headings get auto-generated anchors. Click any heading on this docs site to copy a deep link. In source:

## Provider routing

[Jump to provider routing](#provider-routing)

Read on