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

How to turn pinned frames into durable style rules for agents with Doop

Pin exemplar frames and let the guideline distiller propose rules every agent follows.

Who it is forA design lead who wants consistent output from every agent working on the same canvas.

The problemEach agent or designer drifts in style, and the decisions behind a design are lost.

The outcomeA set of distiller-proposed style rules, backed by pinned exemplars and captured decisions, that agents read before designing.

What you need first

  • Git and bun installed (the README says Doop builds and installs with bun, and the server runs on Node)
  • Claude Code or another MCP client, for connecting an agent over OAuth
  • Docker, only if self-hosting the production build
  • An ANTHROPIC_API_KEY, only if you want the built-in Doop Agent to run

Steps

  1. Set ANTHROPIC_API_KEY in .env, since the distiller uses that key and turns off without it
  2. Run bun run dev and open your canvas at http://localhost:4300
  3. Pin two or three exemplar frames that show the style you want
  4. Capture a few design decisions in the canvas
  5. Run the distiller and review the proposed rules before accepting them

Prompt for your agent

In the repo kgoedecke/doop, with ANTHROPIC_API_KEY set, pin three exemplar frames on canvas <canvas-id>, then run the guideline distiller. Report the rules it proposes and state whether each one cites a pinned frame or a captured decision.

Caveat. The README does not say how the distiller chooses rules or how to edit them afterward, so review every proposal before treating it as a team standard.

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