DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to match diagrams to your site's brand with Diagram Design

Onboard the skill to your site so every new diagram uses your palette and fonts.

Who it is forA marketer, founder or writer who publishes diagrams on a website and wants them to look like the rest of the site.

The problemGeneric diagram output clashes with the site's look, so each diagram needs manual restyling.

The outcomeDiagrams that follow the palette and fonts pulled from your site after onboarding.

What you need first

  • An agent host that reads Agent Skills, such as Claude Code, Codex, Cursor or GitHub Copilot
  • A terminal that can run `npx skills add` or the host's plugin commands
  • A web browser to open the generated .html file

Steps

  1. Install the skill with npx skills add cathrynlavery/diagram-design.
  2. Ask your agent: "Onboard Diagram Design to https://yoursite.com".
  3. Ask for any diagram, for example a quadrant of Q2 projects by impact vs effort.
  4. Compare the new diagram's colors and fonts with your site.
  5. Ask the agent to adjust the palette if one color is off.

Prompt for your agent

Using the diagram-design skill from cathrynlavery/diagram-design, onboard to <site URL> so it pulls the site's palette and fonts. Then draw a quadrant diagram of <topic> and write one self-contained .html file. Verify that the accent color and fonts match the site.

Caveat. Onboarding pulls palette and fonts from the URL you give, so check the result against your site before you publish diagrams.

Share: X LinkedIn Hacker News Email Copy link

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