Style inline code as monospace chips

[andrewleesteele]

Summary

Inline code variables in the docs were rendering in the global Inter (proportional) font with no visual treatment — weird spacing, wrong size, and no code-like appearance, so they read as malformed prose instead of code.

Root cause: the site's fonts.family: Inter config applies broadly, and bare inline <code> spans (e.g. payload, runtimeContext, App) had no dedicated styling to override it. Code blocks were unaffected since they live inside <pre>/.code-group with their own mono styling.

This adds a scoped :not(pre) > code rule in style.css:

• monospace font stack
• subtle background chip + border (respects the site-wide border-radius: 0)
• normal letter-spacing and 0.875em sizing

Includes a dark-mode variant using the same neutral tokens already used elsewhere in the file.

Test page

Set up as a test on the Developing page, which is dense with inline variables. If it looks good, the same treatment covers inline code across all docs pages (the rule is global). Preview once the Mintlify branch build is up.

Notes

• No page content changed — CSS only.
• Table inline code keeps its existing dedicated sizing/padding (higher specificity) and picks up the new mono font.

🤖 Generated with Claude Code

---

Note

Low Risk
Presentation-only CSS with scoped selectors; no content, auth, or data paths touched.

Overview
Adds global style.css rules for inline <code> (via :not(pre) > code) so bare variables pick up a monospace stack, subtle gold-tinted chip background/border, and normalized sizing/letter-spacing instead of inheriting Inter from the site font config. <pre> blocks are unchanged.

A html.dark override bumps background and border opacity for the same inline treatment in dark mode.

^{Reviewed by Cursor Bugbot for commit 32e25d3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 5, 2026, 4:00 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Aug 5, 2026 10:48pm

[cursor]

Stale comment

Risk assessment: Very Low

Verdict: Already approved — no re-approval needed

Evidence (from diff only)

• 1 file changed: style.css (+23 / −0)
• Presentational CSS only: monospace stack, sizing, padding, and green-tinted chip styles for :not(pre) > code, plus a dark-mode variant
• No markdown/content, JS/TS, config, infra, auth, or schema changes
• No CODEOWNERS file in the repo

Why Very Low

• Small, cosmetic styling change on a documentation site
• No production application logic or shared backend systems
• Blast radius is visual only (inline code appearance); <pre> code blocks are excluded by the selector

Re-evaluation

• Prior approval from this automation is on the current HEAD (9e8d605)
• Diff and risk level are unchanged — approval stands; not re-approving

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Verdict: Already approved — risk unchanged after synchronize; approval stands (not re-approving)

Evidence (from diff only)

• 1 file changed: style.css (+22 / −0 vs base)
• Presentational CSS only: monospace stack, sizing, padding, and gold-tinted chip styles for :not(pre) > code, plus a dark-mode variant
• Latest commit vs prior approved HEAD (9e8d605 → 32e25d3): color-token swap only (green → light gold rgba values / comment text)
• No markdown/content, JS/TS, config, infra, auth, or schema changes
• No CODEOWNERS file in the repo

Why Very Low

• Small, cosmetic styling change on a documentation site
• No production application logic or shared backend systems
• Blast radius is visual only (inline code appearance); <pre> code blocks are excluded by the selector

Re-evaluation

• Prior approval from this automation was on 9e8d605; PR synchronized to 32e25d3
• Risk level remains Very Low — no increase, so approval is not revoked and is not re-issued

  

_{Sent by Cursor Automation: Assign PR reviewers}