todai
Saturday, 18 April
5 min read · 883 words
  • BasedHardware/omi — 821★ today (9,683★ total) — open-source wearable AI that sees your screen, listens to conversations, and surfaces context in real time | https://github.com/BasedHardware/omi

TODAY'S ITEMS

1. Claude Design launches: design → Claude Code handoff in one instruction

  • Anthropic Labs' new product lets you build prototypes, slides, one-pagers, and marketing assets by describing what you need — Claude builds it, you refine through conversation, inline comments, or custom sliders. The standout feature: when a design is ready, Claude packages a handoff bundle you pass to Claude Code with a single instruction.
  • Source: Anthropic
  • Why it matters: Point it at your codebase during onboarding for automatic brand/design-system application, then export directly to Claude Code for implementation — the design-to-dev loop for small teams just got much shorter. Available now at claude.ai/design on Pro/Max/Team/Enterprise.
  • Verified

2. Opus 4.7 workaround: disable adaptive thinking, set effort to high

  • The Opus 4.7 HN thread (1,924 points, 1,406 comments) has surfaced a concrete fix for the reasoning regression: disabling adaptive thinking and explicitly setting effort to high restores baseline reasoning performance. Claude Code creator Boris Cherny confirmed on HN that "the specific turns where it fabricated had zero reasoning emitted" — and multiple developers report that switching off adaptive mode resolves the issue.
  • Source: Hacker News
  • Why it matters: In API calls, use thinking: {type: "enabled", budget_tokens: 8000} instead of relying on adaptive mode — and in Claude Code, set thinking effort to high rather than leaving it on adaptive; this is the community-confirmed workaround, not "wait for Anthropic to patch it."
  • Emerging

3. Claude Code 6-month workflow: plan first, one step at a time, session retro

  • A senior full-stack dev's thread (874 upvotes r/ClaudeAI) distils six months of daily Claude Code use into six habits: always use plan mode before any implementation, ask for only step one (never the whole feature), let Claude fix its own bugs rather than patching them yourself, run /simplify before reviewing, and close every session with "what did you learn?" — then save the output.
  • Source: r/ClaudeAI
  • Why it matters: The "ask for only step one" rule prevents the most common Claude Code failure mode (runaway implementation that's hard to review), and the end-of-session retro is how you turn one-off sessions into cumulative project knowledge — today's Prompt of the Day is a copy-paste version of this technique.
  • Emerging

NEW TOOL / PRODUCT SPOTLIGHT

  • Claude-Code-Game-Studios — Turn a single Claude Code session into a full 49-agent game dev studio: Directors (Opus), Department Leads (Sonnet), and Specialists (Sonnet/Haiku) organised into a real studio hierarchy. Includes 72 slash-command workflow skills (/start, /design-system, /create-epics, /dev-story, /story-done), 12 hooks for automated validation, 11 path-scoped coding rules, and 39 document templates. Copy .claude/ into your game project and type /start.
  • git clone https://github.com/Donchitos/Claude-Code-Game-Studios && cp -r Claude-Code-Game-Studios/.claude/ <your-project>/
  • https://github.com/Donchitos/Claude-Code-Game-Studios

PROMPT OF THE DAY

We've finished this Claude Code session. Before we
close out, run a session retrospective:

1. What went well — patterns or decisions that
   worked cleanly and are worth repeating
2. What got messy — bugs, dead ends, regressions,
   or things we had to undo
3. What to add to CLAUDE.md — specific rules or
   context that would have prevented issues this
   session
4. Tech debt logged — anything to revisit before
   shipping

Format your response as a CLAUDE.md addendum
I can paste directly into the project.

Build institutional knowledge across Claude Code sessions — the end-of-session retro. Use at the end of any non-trivial build session in Claude Code. Source: Inspired by r/ClaudeAI 6-month workflow tips thread (874 upvotes) | https://www.reddit.com/r/ClaudeAI/comments/1sn27yu/

LANDSCAPE NOTES

TRY THIS WEEKEND

Claude Design launched today — run it end-to-end on a real project:

  1. Open claude.ai/design and complete onboarding by pointing it at your codebase or existing design files
  2. Describe a feature UI, landing page, or pitch deck for something you're actually building
  3. Refine through conversation until it's right, then use the Handoff to Claude Code export
  4. Pass the handoff bundle to a fresh Claude Code session and watch it implement

Expected outcome: a working design-to-implementation pipeline in about an hour, plus you'll know where Claude Design's limits actually are before relying on it in production. Resource: https://www.anthropic.com/news/claude-design-anthropic-labs