DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to make every diagram match your website's colors and fonts with diagram-design

Give the skill your site URL once and every later diagram uses your palette and fonts.

Who it is forFounder or marketer who needs diagrams for decks, docs and blog posts that look like their own brand

The problemGeneric diagrams clash with a branded site or deck and need manual recoloring each time.

The outcomeA saved brand profile so each new diagram comes out in your palette and typography without extra prompting.

What you need first

  • An Agent Skills compatible host such as Claude Code, Codex, Cursor, Qoder, GitHub Copilot, Gemini CLI, Cline, Windsurf or Amp
  • Node.js for the npx install command
  • A browser to open the generated HTML file
  • Optional: a public website URL for brand onboarding

Steps

  1. Install the skill with: npx skills add cathrynlavery/diagram-design
  2. Ask your agent: Onboard diagram-design to https://yoursite.com
  3. Let it pull your palette and fonts, then request a first diagram and compare it with your site.
  4. Ask for tweaks to the style if a color or font is off, then keep using the same profile.

Prompt for your agent

Onboard diagram-design to <my website URL>, then draw a <diagram type> of <topic> in that brand. Tell me which colors and fonts you picked up so I can confirm they match.

Caveat. The skill sends your site URL over the network during onboarding, and the README points to PRIVACY.md for exactly what leaves your machine. Read it before onboarding a private or staging site.

About diagram-design

An agent skill that draws clean diagrams as a single HTML and SVG file in your brand. Part of this week's top 10 repos: ranked #8 on Repo Radar. View cathrynlavery/diagram-design on GitHub.

More with diagram-design

See all use cases for cathrynlavery/diagram-design

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page