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

How to build a matching favicon and OG card set with Codex Bridge

Generate one icon family with a shared style and derive all sizes from a master.

Who it is forA developer launching a project who needs favicons, app icons, and a social preview card that match.

The problemAsking for each asset separately produces icons with different palettes, stroke weights, and margins.

The outcomeA set of favicon and OG card files that share one style, saved in your project.

What you need first

  • Claude Code (any current version)
  • Codex CLI installed with `npm i -g @openai/codex` or `brew install codex`
  • Logged in with `codex login`, confirmed by `codex login status`
  • A ChatGPT Plus, Pro, or Team plan
  • macOS or Linux (Windows is not tested)

Steps

  1. Complete the install steps for the Codex CLI, codex login, and the plugin.
  2. Install ImageMagick so the size variants can be made locally. (inferred, check the README)
  3. In Claude Code, ask: set up favicons and an OG card for this project.
  4. Generate a large square master with codex-imagegen and pass earlier icons with --ref so the style carries over.
  5. Review each output image and ask Claude to regenerate any that miss the style.

Prompt for your agent

In the Sateezg/codex-bridge plugin setup, generate a square master icon for <project-name> with codex-imagegen, then create favicon and OG card sizes from it. Report the list of output file paths. Verify that every file exists and that the set uses one palette.

Caveat. Custom sizes must meet Codex limits, so for sizes such as a 1200x630 OG card the plugin generates a large master and resamples it locally.

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