/sopStandard operating procedure document. Formal, complete, checklist-style.
Category: Productivity Hacks
Before / After
Document this process.
/sop How we onboard a new engineer in their first week.
What changes in Claude's response
Formal document: title, owner, last reviewed, scope, prerequisites, numbered steps with sub-steps, escalation path, related docs. /sop is what you write when 'how we do this' needs to be the same regardless of who's doing it.
Full deep dive locked
The complete analysis for /sop — including when NOT to use it, the failure modes, and the codes it stacks with — is in the full cheat sheet along with 119 other tested prefixes.
Lifetime updates · 7-day refund · 3 tiers
More Productivity Hacks codes
/tldrawSketch a workflow in plain English, get the implementation.
/templateGenerates a reusable template from a one-off output. Variables become `{{placeholders}}`.
/recipeStep-by-step recipe format. Ingredients, steps, time estimate, common mistakes.
/cheatsheetOne-page cheat sheet on any topic. Dense, scannable, no fluff.
/quickrefQuick reference card. Even denser than /cheatsheet — designed for one screen.
Get new codes + workflows weekly
Join 30+ developers getting tested prompt codes, skill files, and Claude workflows. One email when there’s something worth sharing.