Skip to content

usage: expand Credit Optimization into eight actionable habits - #302

Open
alonlindy wants to merge 2 commits into
mainfrom
docs-usage-credit-optimization-tips
Open

usage: expand Credit Optimization into eight actionable habits#302
alonlindy wants to merge 2 commits into
mainfrom
docs-usage-credit-optimization-tips

Conversation

@alonlindy

Copy link
Copy Markdown
Collaborator

What

The #credit-optimization section on /account-billing/usage offered one lever (switch your default model), then sent users to /account-billing/credit-optimizations, which is entirely about the legacy workflow editor and isn't in the nav. Not much for an Assistant user to act on.

This expands it to eight tips, benchmarked against Viktor's credits guide and filtered for what actually applies to our product.

Changes

  • Pick the right model — keeps the existing steps, adds a line on which work runs fine on a cheaper model
  • New <AccordionGroup> with seven habits: one chat per topic, batch related asks, write specific briefs (with a costs-more / costs-less example), turn off unused routines, narrow meeting recording, reconnect dropped integrations, check usage weekly
  • <Tip> cross-linking the Usage Warning section above
  • Links out to Routines and Integrations

The ## Credit Optimization heading text is unchanged, so the live #credit-optimization anchor keeps resolving. No images or video added — this stays consistent with the current lean version of the page.

Applicability calls

Of Viktor's ten, seven carried over, two were rewritten, one was dropped:

  • Dropped "skip images" — image generation isn't an Assistant surface or a cost driver for us
  • Rewrote "use Ask First for expensive tools" — Guardrails are the closest analog, but they govern writes in shared Slack threads for safety reasons and wouldn't reliably cut credits, so claiming them as a cost lever would be misleading. The usage warning is the honest equivalent, so it became the cross-link <Tip> instead
  • Rewrote "audit your crons" against our actual Routines page, with the real path (left sidebar → Personal tab) and the real behavior (toggling off stops a routine without removing it)

Every UI path in the new copy is sourced from current pages on main: the Routines page and its built-in routines table, the Meeting note taking card's All / External only / Specific meetings options, and the Integrations page's per-connection health status.

One thing worth a look

Overages now appear twice — once in the weekly-check accordion and again in the standalone ## Overages section right below. Reads fine, but easy to trim if you'd rather.

🤖 Generated with Claude Code

The #credit-optimization anchor offered a single lever (switch your
default model) and then pointed users at the legacy workflow-editor
guide, which doesn't apply to Assistant users.

Adds seven habits as an AccordionGroup: one chat per topic, batching
related asks, writing specific briefs, turning off unused routines,
narrowing meeting recording, reconnecting dropped integrations, and a
weekly usage check. Links out to the Routines and Integrations pages,
and cross-links the Usage Warning section above. Heading text is
unchanged so the live #credit-optimization anchor keeps resolving.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mintlify

mintlify Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
lindyai 🟢 Ready View Preview Aug 19, 2026, 3:47 PM

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

Section headings sat 6.4px above their body copy (h2) and 4.8px (h3),
so every heading read as attached to the paragraph below it.

The existing bare h2/h3 margin rules never applied. Mintlify renders
page content inside Tailwind Typography, and .prose :where(h2) outranks
a bare element selector, so Tailwind's defaults won. Scoping the rules
to .mdx-content restores the intended rhythm: 3rem/1rem for h2 and
2.25rem/0.75rem for h3.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant