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

How to set one brand palette and reuse shared navigation across screens with Quilt

Define tokens once and edit a shared tab bar or sidebar to update every screen that uses it.

Who it is forA designer or developer who keeps the same navigation and colors across many generated screens and wants one place to change them.

The problemRe-styling each screen by hand and fixing the same tab bar in ten places is error-prone.

The outcomeA design system with a brand palette and a shared component that re-bakes every screen that references it, with no model calls.

What you need first

  • Node.js 22 or newer and pnpm 11
  • Chrome or Edge installed, or run `npx playwright install chromium` once
  • A generation channel: a logged-in `claude` CLI, an Anthropic or Gemini API key, or an OpenAI-compatible endpoint added in the settings panel
  • Port 3100 and 3101 free on 127.0.0.1

Steps

  1. Start Quilt with node apps/cli/bin/quilt.js and open the canvas at http://127.0.0.1:3100.
  2. Set a seed color or an explicit light and dark brand palette in the design system panel.
  3. Turn an existing tab bar, app bar, or sidebar into a project-level shared component.
  4. Edit the component once, from the composer or by hand, and confirm every screen that uses it updates.
  5. Save the design system as a preset to apply to the next project.

Prompt for your agent

In the Quilt project <project-name>, update the design system with the brand palette <palette> using update_design_system, then edit the shared component <component-name> with edit_component. Report how many screens were re-baked. Verify that the active link is marked correctly on each route.

Caveat. Shared components only update screens that reference them, so screens built without the component keep their own markup.

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