Logging plan and daily fix list
Broken features, stuck users, slow steps: ranked by users affected, with log lines; the worst one already has a test.
357 saves on X, as of Posted
Step 1: add proper logging
Help me plan logging for this app so we can fully replay one user's experience: what they did, the key steps inside the app, and what they saw in the end. Give every session an ID, and never log passwords, tokens or personal data. Store the logs where an agent running on a daily schedule can read them. Show me the plan first, and don't write any code until I approve it.Step 2: run once a day
Read this app's logs from the past 24 hours. Find broken features, places where users got stuck, and steps that are slow or unnecessary. Rank them by how many users each one affects, and quote the log lines behind each one. Turn the worst one into a test that reproduces it. Don't change any code yet.Next Send Step 1 to your agent in the app’s project, then paste Step 2 into /schedule in Claude Code.
Almost any app can improve itself a little every day. All it takes is two prompts.
In Claude Code, type /schedule and paste the Step 2 prompt in. It runs in the cloud and keeps going with your laptop closed, as long as it can read your logs.
Step 3: every morning, read the ranked list and pick one to fix. The worst one already has a test, so just have your agent fix it until that test passes.
Share this tip
