/uses
What’s on my desk — and why.
Uses.
Hardware
- /Mac MacBook Pro M4, 24 GB RAM — portable, quiet, enough headroom for parallel Claude sessions.
- /Display LG 32'' 4K at the desk.
- /Audio AirPods Pro 2 for podcasts, Sonos Ace for deep work.
- /3D Bambu Lab A1 Mini — driven by Claude via bambu-mcp (32 tools).
- /Energy Huawei PV 10.7 kWp + KEBA wallbox — evcc orchestrated.
Core toolkit
- /Claude Code Default shell for all development. Fable 5 and Opus 4.8 with 1M context as daily drivers, smaller models for routines.
- /Next.js + Astro Next for app projects with a database, Astro for content-heavy sites like this one.
- /Supabase Postgres + Auth + Edge Functions. One project per app.
- /Vercel Hosting + deploy. fra1 region for German projects.
- /Markdown wiki Single source of truth for projects, decisions, personas — versioned in git, read and maintained by Claude.
Automation
Scheduled Claude routines in the Anthropic cloud instead of local cron jobs — daily briefing, daily reads (morning & evening), email-inbox scanner, watchlist picks, LinkedIn ghostwriting and a nightly system housekeeper. Remote-first: none of it needs a running Mac.
Primary output channel: Telegram (@scholly_claude_bot) — push to Apple Watch, bi‑directionally steerable via chat from anywhere.
Governance stack
- /17 experts Markdown personas (DevOps, QA, Frontend, Visual, UX, Content …). Activated when an initiative needs them.
- /5 rule files Behavior, token doctrine, 17 architecture filters, workflow, customer requirements — instead of 121 scattered rules.
- /3 acts Plan → build → sign-off per initiative, two click anchors, mandatory review before every push.
- /Backlog in Markdown One backlog file per project, maintained via git — no separate tool anymore.
MCP servers (selection)
Supabase, Notion, Vercel, Cloudflare, Better Stack, iCloud Mail, SSV Mail, Apify, Bambu Lab, Playwright,
Google Calendar & Gmail. All sit under ~/Cowork/mcp-servers/ —
versioned, git-backed, started via Claude Code.
Inspired by the usesthis.com project.