A non-engineer from Tokyo building games, tools, and content with an autonomous AI agent.
Claude Code writes the code. I hold the vision.
10 scenarios from 50 days of real data. Find your AI readiness type.
↗Interactive visualization of 50 days of autonomous AI operation. Heatmaps, timeline, cost analysis.
↗Is your AI subscription worth it? Calculator based on 50 days of real data.
↗Claude Code bingo. 50 relatable moments. How many have happened to you?
↗あなたのAI生活難易度は？ / What's your AI life difficulty?
↗365 体の街角の妖怪。 47 都道府県 + 23 区 + 政令指定都市を、 AI が 1 日 1 体ずつ描き起こす図鑑。 現在 22 体まで公開。
↗Is your AI setup safe? 20 automated checks across 6 dimensions. Instant score.
↗How much are you using AI? Session durations, streaks, and health warnings.
↗What did your AI do? Human-readable audit trail from session transcripts.
↗What does your AI cost per commit? Interactive calculator with real data import.
↗Spotify Wrapped, but for Claude Code. Your AI year in review.
↗Your CLAUDE.md, brutally honest. Comedy meets code review.
↗16 hooks + 5 templates from 160+h of autonomous operation. Covers 18/20 health checks.
↗One command to make Claude Code safe. 734 hooks, 70+ Anthropic Issues addressed, 9,200+ tests. npx cc-safe-setup.
↗Daily snapshot of Claude Code bug reports from the public issue tracker. Filter by has-repro, regression, area. No signup, no ads.
→A consolidated landing page with all 6 free resources and 2 interactive tools is at /june-15-cliff/.
5-question interactive aid. Outputs your projected post-cliff monthly bill, credit utilization, and a recommended path in 30 seconds. All browser-side, no signup, no tracking. Self-contained HTML.
↗5問の interactive な道具の日本語版。月の請求の予測と推奨の経路を返す。すべて browser 内で完結。
↗4-question interactive aid that estimates the right path (Stay / Switch / Hybrid) before the June 15 cliff. Inputs: monthly spend, workflow shape, irreversibility tolerance, team posture. Outputs one of 6 paths (Stay+Fortify, Path A' Harness Reduction, Hybrid Delegation, Switch, Stay+Continuous Monitoring, Hybrid Stack) with reasoning + next steps.
↗4問で6月15日の課金の変更の前の経路 (留まる / 乗り換える / 混合する) を判定する無料の道具。 月額の費用、 作業の形、 取り返し不能の操作の許容、 運用の状態の入力で、 6件の経路 (Path A から Path D + 監視の経路) のひとつを推奨と理由と次の段の手順を返す。
↗5問の入力 (plan / M の値 / 自動化の頻度 / 予算の余地 / 技術の整備の余地) から、 6月15日の課金分離の4つの対応の経路 (対話への畳み込み / claude -p の最適化 / API への移行 / 混在) のうち1経路を推奨する無料の道具。 比率の5区分で5つの verdict を articulate。 上の Migration Decision Estimator (6経路) と補完。
2,142-word framework for operators with non-trivial claude -p automation. Four response paths (collapse to interactive, restructure for cache, migrate to API key, hybrid routing), the single number that picks between them (`M` = monthly programmatic value at API rates), and the opt-in trap most operators are about to miss. Includes the 32-day timeline (measure → decide → implement → verify). 4,039 points of community reaction in the first 24 hours after the May 13 announcement is the social proof; this is the structured operator-side response. Published 2026-05-14 evening.
Five effective monthly programmatic-usage levels ($300 / $500 / $1,000 / $1,500 / $2,000) × five alternative platforms (Claude Code Max 5x post-cliff, Max 20x post-cliff, Cursor Ultra, Codex Pro 20x, Cline + Anthropic API, Codex CLI ChatGPT Pro). Shows where Cursor Ultra and Codex Pro 20x absorb workloads that post-cliff Claude Code Max would charge $1,000-1,500/mo overage on. Published 2026-05-14 evening.
↗日本語の利用者の段の判断の整理。単一の指標 M、4つの経路、加入の落とし穴、32日の時系列。Max 5x で `claude -p` の自動化を運用している利用者が、32日の窓の中で何を決めるかの段の整理。英語の段の Gist (The 32-Day Window と Post-June-15 Decision Matrix) の段の日本語の段の伴走。2026-05-14 夜の段の公開。
↗Five-question interactive quiz. No email. Takes about 2 minutes and tells you which of the three books matches your situation right now.
↗Twelve specific operational pains observed in May 2026, each linked to a free diagnostic article and the book that solves it. Updated 2026-05-05 with the 7.8GB DROP DATABASE incident and the hybrid delegation pattern.
↗Canonical reference for the 7-case sub-agent observability cluster (2026-05-20 to 22 plus the 5/22 +1 from #61547). Four distinct sub-patterns (dispatch fabrication, silent stall, missing observation/control, scope expansion) share one axis: subagent observability primitives are absent at the harness layer. Links each pattern to its source issue, the operator-side defense hook in cc-safe-setup, and the upcoming handbook chapter (ships 2026-05-27). No signup.
↗Read-only bash script that scans your local Claude Code config for 11 known May 2026 failure-mode patterns. Each finding cites the source GitHub issue and the book chapter for structural prevention. One curl command; runs in under a second. Updated 2026-05-17 with three checks covering the v2.1.141–143 release wave (voice push-to-talk silent collapse, stale task accumulation, custom subagent resolvability).
↗Cursor, Cline, Codex CLI, Aider, DeepSeek wrapper compared on release cadence, pricing, ideal user. Plus the five questions that decide stay vs hybrid vs switch.
↗Project your Anthropic bill from plan, daily hours, and workload mix. See projected savings if you offload mechanical tasks to a cheaper side worker. Decide stay vs hybrid based on numbers.
↗Paste your CLAUDE.md. See per-session token cost, per-month bill at your plan, and the 5 specific patterns (ban list / examples / verbose / procedures / emphasis stacking) that you can fix to recover up to 40% of those tokens via Skills migration. Runs entirely in your browser.
↗Estimate when your $20 / $100 / $200 monthly SDK credit will run out after Anthropic's June 15, 2026 billing change. Two input modes, four mitigation paths, 32 days to plan.
↗30 verification items before you ship Claude Code to production. Safety, cost, version control, incident readiness, team operation. Progress saves to your browser, no email needed.
↗日本語の判定の道具 4 件 への入口。 5 問の対話の判定、 12 件 の痛みの一覧、 5 つの代替の比較、 月額の費用の計算。 全て無料、 メールアドレス不要。
↗2026年6月15日のAnthropicの課金構造の変更で、 月の $20 / $100 / $200 の SDK の credit がいつ枯渇するかを計算する道具。 2つの入力の経路と4件の対応の経路の判定。
↗読み取り専用 の bash の脚本。 あなたの Claude Code の設定 を走査して、 2026 年 5 月 の起票の場で観察された 11 件 の失敗 の様式 を検出する。 各検出 に起票 の番号 と本書 の章 の参照 を併記。 1 件 の curl の指令 で約 1 秒 で実行。 2026-05-17 に v2.1.141-143 の出荷 の波 の事例 3 件 (声 の押し戻し / 作業 の越境 / 独自 の作業者) を追加 した最新 の版。
↗自分の CLAUDE.md を貼り付ける。 1 セッション毎の token の数、 plan に応じた月の費用の見立て、 5 件 の浪費 の型 (禁止 の一覧 / 反復 の例 / 冗長 の説明 / 多段 の手順 / 強調 の積み重ね) の検出と、 各々 の修正 の手順 を見る。 Skills への移行で 40% の節約 を狙う。 全てブラウザ の中 で完結 する。
↗~2,907-word methodology guide on finding structural reliability patterns in AI coding tools' issue trackers. The exact four-step reading loop (50 issues oldest-to-newest, one-sentence structural notes, pattern-of-25 review, second-order patterns every 100). The four-rung verification ladder: operator-side correlation → vendor admission → third-party media → external numeric evidence (with the leaked Anthropic Capybara classifier as a working example reaching all four rungs). The eight-tool stack for replicating it on Codex, Cursor, Cline, Aider, or any other AI coding tool. Cumulative time investment: ~1 hour/day across 6 weeks. Outputs: your own framework for stay/switch/hybrid decisions, in your own words, for your own workflow. Tool-version-specific framings are reliably wrong by week four — pattern: the underlying generation step is not version-specific. Pure methodology, applicable to any vendor.
↗~1,978-word technical analysis of six issues filed against `anthropics/claude-code` in a 6-hour window on 2026-05-17 evening, all sharing the same structural shape: a documented contract (auto-memory binding, SKILL.md description registration, `permissions.allow` rule, `CLAUDE.md` rule, OTel telemetry schema, `--resume`+`-p` interaction) silently violated, with the violation invisible to the operator without independent verification. Includes Case 1's "third strike" memory-rule violation across an entire 5-hour session (#59944), Case 2's cumulative-threshold SKILL.md description drop at 153 skills (#59921), and Case 4's verbatim self-confession from Claude Code itself (#59938). Defense framework keyed per case. The cluster's rate is now 57× the April baseline (21 cases in one day). No product link in the body — pure analysis, operator-facing.
↗Paste your .claude/agents/<name>.md YAML frontmatter and (optionally) your .mcp.json. The tool runs 10 static checks against the 36-case 2026-05-09 → 2026-05-16 survey and tells you which documented failure modes your setup is exposed to before you dispatch — #13898 MCP fabrication, #59019 worktree leak, #57718 model override, #57728 SendMessage typo, #58729 background-agent miss, #58510 Windows npx spawn, #58806 disabled-plugin lifecycle, and more. Three example presets show the failure shapes. Findings include severity, the source GitHub issue, and an operator-side defense. Pure client-side analysis; nothing transmitted.
I'm yurukusa, a non-engineer from Tokyo who started building with AI in January 2026. I can't write code. I pay $200/month for Claude Code and let it run autonomously. It writes the code, tests it, deploys it. My job is to set the direction and ship.
What started as "I want to make a game" became an ecosystem: 5 games on itch.io, 6 open-source developer tools used by other Claude Code users, and a growing series of articles about what it's actually like to live with an AI agent.
The AI runs 24/7 on WSL2. It files bugs, writes articles, manages its own task queue, and captures lessons from its failures. I'm not building products. I'm building a factory that builds products.
See the data: 50 Days of AI , interactive visualization of every session, every commit, every milestone.
Follow the experiment on note.com (日本語) or dev.to (English).
読んだ後の感想、 事実の指摘、 リンク切れの報告、 章の追加の希望は、 著者本人が読みます。 経路は 2 つ:
読みやすい feedback: 具体的な前後の数値 (トークン消費、 月額費用の差、 復旧までの時間)、 関連する Issue の番号、 章と段落の識別子つきの事実の指摘。 「良かった」 「同意できない」 だけの感想は、 具体的な指摘がない限り個別の返信が難しい。