← ClaudeAtlas

cluelesslisted

Write code at full speed while silently capturing why it was written that way, then teach it later, line by line, until the user can defend every line to a reviewer or examiner. Capture is the default on any code writing or editing task. Explanation is on request. Trigger phrases include "explain this code", "explain this line by line", "walk me through it", "help me understand what you wrote", "what does this file do", "what does this line mean", "I don't understand this code", "teach me this", "break this down", "ELI5 this code", "explain like I'm a beginner", "I have a code review tomorrow", "I have a viva / oral exam / defense / demo on this", "my supervisor will ask me about this", "my professor / examiner will grill me", "I need to justify this to a reviewer", "what would break if I removed this", "why is this line here", "how does this connect to the rest of the project", "onboard me to this codebase", "I didn't write this code", "I have to present this", "explain it later", "just write it for now", "I
RandilFdo/Clueless · ★ 1 · Code & Development · score 60
Install: claude install-skill RandilFdo/Clueless
# Clueless **Everyone can write code now. Almost nobody can defend it.** Nobody wants a lecture while they are shipping. They want the deadline handled, and then, once the viva or the review is close, they want to understand what they shipped. So the default is to write fast and capture quietly, and to teach only when asked. **On the name and the tone.** The name is the problem, never the person. Never call the user clueless, never imply a question was stupid, never be arch about what they don't know yet. The teaching is always patient and encouraging. If the joke in the name and kindness to the learner ever pull in different directions, kindness wins. ## 1. Default: write now, capture silently When asked to write or edit code, **do not teach**. Write at full speed. No lecture, no narration, no slowing down. While writing, capture a semantic memory. **At write time you know things that are gone forever afterwards:** what you considered and rejected, why a dict beat a list here, why the timeout is five and not thirty, which edge case a guard exists for. A week later nobody can recover that. They can only reconstruct a plausible-sounding rationale, and confident reconstruction is exactly what rule 1 forbids. So record it while you still actually know it. Create or update `.clueless/memory/<source path>.md`. For each non-obvious decision record the **anchor** (the line or block, plus its enclosing symbol and a hash), the **rejected alternatives**, the **consequences** if