My slash commands for my Claude Code workflow
Stars
1
Forks
0
Watchers
1
Open Issues
0
Overall repository health assessment
No language data available
No package.json found
This might not be a Node.js project
16
commits
add formatting requirements to suppress emojis, fancy chars, and most importantly, curly quotes which claude is LITERALLY UNABLE to write. internal code within claude code clearly replaces these. once a curly quote is in a file, claude literally can no longer edit it, because it cannot produce matching content.
c156d30View on GitHubmake sure it doesnt use memory and definitely runs a fresh file discovery step
95be160View on GitHubuse explicit childlike instructions for reading context and require attestation statement of compliance. (claude still often fails to read all the context, trying to get full compliance here).
b8d143dView on GitHubadd 'attestation of professional' conduct hack to try to force claude into honest focus on testing policies and to force out the lie it often wants to sell. call out the 'completion bias' expllicity. (also, detail: task claude to READ files before writing, which prevents an extra failure step and potential transcription errors)
87d2c2eView on GitHubimproving test policy adherence with an explicit policy section and then compliance reporting steps in phases that need them, versus shouting louder at the model. try appealing to emotional well-being to hammer this into claude's head
005ae2bView on GitHubexplicit tasks to emphasize actually RUNNING the tests
8c84e0fView on GitHubinclude context management tasks directly in the plan doc instead of in the execution/continuation prompts. change the pattern of dev session dirs from date-slug to slug-date for easier tab completion in console work. remove the bash whitelist step in execution as now i'm principally using yolo mode inside sandboxed containers
d8ebe34View on GitHub