Every published module, all in one place.
130 modules
Writing → Copywriting
Rules for writing UX microcopy across buttons, labels, error messages, and empty states: verb-first buttons, error messages that state what to do next, no blame, no jargon, placeholder versus label use, and confirmation copy.
by @markdowners
Video & Audio → Youtube Content
Rules for writing YouTube video scripts that hold retention: the first 15 seconds, open loops, chapter structure, writing for the ear, retention edits, and CTA placement.
Testing & Quality → E2e Testing
Writing end-to-end tests that stay reliable and fast: covering critical user journeys not everything, resilient role/test-id selectors, waiting on conditions instead of sleeping, test data isolation, treating flakiness as a bug, and keeping the suite runnable.
Study & Research → Other
Rules for writing academic essays with a clear argument: the thesis as one arguable sentence, paragraph structure of claim plus evidence plus analysis, counterargument handling, intro and conclusion discipline, signposting, and separating the editing pass from drafting.
Project Setup → Git Workflow
Git workflow rules for teams: small atomic commits with imperative messages, branch naming, rebase versus merge policy, pull request size caps, never force-pushing shared branches, why-focused commit bodies, and .gitignore hygiene.
Business Docs → Other
Rules for writing job descriptions that attract the right candidates: real responsibilities over buzzwords, must-have versus nice-to-have separation, salary transparency, inclusive language, and cutting requirement inflation.
Data & AI Features → LLM Integration
How to integrate an LLM API into a production application: never trust model output blindly, streaming UX, retry with backoff on rate limits, token budget management, PII-aware prompt/response logging, fallback behavior on failure, cost monitoring, and model version pinning.
Social & Marketing → Newsletters
Rules for writing email newsletters that get opened and read: subject line discipline, preview text, one job per email, scannable structure, send rhythm, and what makes people archive on sight.
Business Docs → PRDs & Specs
Rules for writing business proposals that win work: opening with the client's problem in their own words, scope with explicit exclusions, options with a clear recommendation, pricing presentation, and a strong next-step close.
Writing → Resumes Cover Letters
Rules for writing and rewriting a resume that passes ATS screening and reads well to a human: one-page defaults, metric-driven achievement bullets, tailoring to a job description, and what to cut.
Writing → Storytelling
Rules for writing speeches meant to be heard, not read: short spoken-length sentences, the rule of three, callbacks, opening strong and closing stronger, rhythm and pause marks, and the read-aloud test.
Writing → Tone Of Voice
Rules for defining and applying a consistent brand voice: naming voice traits with do/don't pairs, calibrating formality, keeping consistency across channels, distinguishing voice from tone, and maintaining a banned-phrases list.
Frameworks → Vue & Nuxt
Vue and Nuxt conventions: Composition API defaults, composables for shared logic, props-down-events-up data flow, computed over methods for derived data, single-file component structure, and Nuxt server routes and data fetching.
Rules for pairing YouTube titles and thumbnails as one packaging unit that drives clicks: complementary information, honest curiosity gaps, title length limits, and thumbnail composition for click-through rate.
Writing → Editing Proofreading
Rules for editing and proofreading any draft: a structure-to-clarity-to-line-to-proof pass order, cutting 10-20% of length, catching passive voice and filler words, consistency checks, and preserving the author's voice.
Study & Research → Study Plans
Rules for the final stretch of exam preparation: past-paper practice under timed conditions, error logs, topic triage by marks-per-effort, the last-week taper, day-of routine, and what cramming can and cannot do.
Translation & Languages → Glossaries
Rules for building and maintaining a terminology glossary for translation or domain-specific writing: one canonical term per concept, a consistent entry format (term, definition, context, forbidden synonyms), source-of-truth maintenance, domain scoping, and when to add versus prune entries.
Personal Productivity → Journaling
Rules for journaling prompts that produce real reflection instead of a blank page: specific over generic, morning vs evening formats, concrete gratitude, decision journaling, rereading cadence, and keeping the habit alive.
Translation & Languages → Localization
Rules for building genuinely localizable products: externalized strings, no string concatenation, ICU pluralization, locale-aware date/number/currency formatting, text expansion room, RTL awareness, meaning-first translation, and translator context.
Rules for writing product requirements documents that engineering can actually build from: problem before solution, user stories with acceptance criteria, non-goals, success metrics, and open questions.
Frameworks → Python & Django
Django project conventions: fat models thin views, queryset optimization with select_related and prefetch_related, migrations discipline, forms/serializers for validation, per-environment settings, and app boundaries.
Rules for writing blog posts that rank and read well: search-intent match, one primary keyword with natural variants, title and H2 structure, scannability, internal linking, meta descriptions, and refreshing old posts.
Rules for narrative structure in any written piece: stakes before detail, concrete specifics over abstraction, one protagonist, conflict as the engine, show-then-tell, and how to find the story in dry material like case studies and data.
Integrations → Email Sending
Rules for sending transactional email correctly: separation from marketing streams, immediate delivery, fact-based subject lines, self-contained body content, SPF/DKIM/DMARC deliverability basics, and plain-text fallback.