Skip to content

chore: glow up README + diagrams — hero banner, marketing callout#96

Merged
brentrager merged 1 commit into
mainfrom
chore/readme-glowup
Jun 13, 2026
Merged

chore: glow up README + diagrams — hero banner, marketing callout#96
brentrager merged 1 commit into
mainfrom
chore/readme-glowup

Conversation

@brentrager

Copy link
Copy Markdown
Contributor

Applies the Smoo AI README glow-up (v2) to smooth (the th CLI), using the shared Smoo-family banner generator for a consistent sub-brand look.

What changed

  • Hero banner — replaced the logo + H1 + tagline block with a gradient .github/banner.png (shared Smoo family mark, "smooth" name, tagline, kicker). SVG source kept alongside.
  • Badges — the 3 primary badges (The Line, Smoo AI platform, license) are now for-the-badge + labelColor=020618; Rust/release badges stay flat-square.
  • Marketing calloutPart of Smoo AI now leads with smoo.ai/th and links sibling repos (smooth-operator, deploy, logger, config).
  • Diagrams (5) — all five mermaid blocks rebranded with the dark init directive + warm/teal classDefs (dropping the off-brand per-node style lines and the elk renderer override) and simplified:
    • Agent loop — collapsed verbose <small> labels, chained edges.
    • Architecture — collapsed the 3-operative fan-out and the host sub-services into single nodes; one flowchart TB.
    • Inside each MicroVM — merged Narc's two edges, shortened port labels.
    • Security model — collapsed tool/pearl/MCP allowlists into one node, trimmed labels; kept the 3-tier subgraphs.
    • Access negotiation (sequenceDiagram) — themed actors/notes to the brand palette.

All real content (install, CLI reference, cast table, tech stack, workspace layout, dev commands) preserved. No .smooth/dolt touched.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Jun 13, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 811c8f7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@brentrager brentrager enabled auto-merge (squash) June 13, 2026 21:51
@brentrager brentrager merged commit f701f46 into main Jun 13, 2026
3 of 4 checks passed
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