Every published module, all in one place.
130 modules
Payments → Stripe
Stripe-specific integration rules on top of payment-system-basics: key handling, Elements, SCA/3DS, and treating webhooks as the source of truth.
by @markdowners
Testing & Quality → Other
A pragmatic testing pyramid and CI discipline focused on tests that actually catch real regressions, not coverage-number theater.
Translation & Languages → Translation Style
Rules for producing translations that are faithful and natural at once: register, glossary discipline, false friends, locale formatting, and what to leave untranslated.
E-commerce → Cart
Rules for abandoned cart recovery email sequences: send timing, showing actual cart contents, single-CTA restoration, incentive escalation discipline, objection handling, stop rules, and non-creepy subject lines.
UI & Frontend → Accessibility
Baseline accessibility rules — semantic HTML, keyboard operability, contrast, and screen-reader support — built in from the first component.
Social & Marketing → Ads Copy
Rules for writing paid ad copy that converts across Facebook, Google, and other placements: one promise per ad, benefit before feature, message match to the landing page, compliance basics, and single-variable testing.
AI Behavior → Code Style Rules
How an AI coding assistant should match a codebase rather than impose its own preferences: mirror existing style, avoid drive-by refactors, keep diffs minimal, comment only where code can't speak, never leave placeholder code, respect the project's stack choices, and ask before adding dependencies.
AI Behavior → Safety Guardrails
Guardrails for an autonomous AI agent with real permissions: confirm destructive actions, never print or commit secrets, strict scope discipline, flag external side effects before executing, state uncertainty honestly, never fabricate source-of-truth content.
API & Backend → Other
Rules for writing API reference documentation developers can actually use: runnable examples per endpoint, realistic request/response pairs, a full error catalog, auth explained first, breaking-change changelogs, a five-minute quickstart, and generating docs from source of truth.
API & Backend → Background Jobs
Build reliable background job and queue systems: idempotent handlers, retry with backoff and dead-letter queues, small payloads, timeouts, at-least-once delivery, queue-depth monitoring, and graceful worker shutdown.
Design & Art → Brand Identity
Rules for building a brand style guide that actually gets used: logo usage constraints, exact color codes with usage ratios, typography hierarchy, a short voice summary, do/don't examples, and length discipline.
Business Docs → Reports
Rules for writing business reports that get acted on: conclusion-first BLUF structure, data presented with context, one chart per message, clear recommendation sections, and appendix discipline.
Database → Caching
Apply a disciplined caching strategy: cache-aside as the default pattern, TTLs on everything, explicit invalidation on writes, stampede protection, versioned cache keys, what to never cache, and measuring hit rates.
E-commerce → Checkout
Rules for ecommerce checkout flows that convert: mandatory guest checkout, form field minimalism, upfront cost visibility, progress indication, payment method breadth, error recovery, and trust signal placement.
Deployment & Infra → CI/CD
Building CI/CD pipelines that catch problems early and deploy safely: fast feedback ordering, fail fast, dependency caching, secrets via the platform's store, deploying from main only, a rollback plan, and no manual production steps.
Study & Research → Citations
Rules for formatting citations correctly and consistently: choosing one style (APA, MLA, or Chicago) and sticking to it, in-text versus bibliography formatting, citing only sources actually read, quote-versus-paraphrase discipline, plagiarism-safe practice, and reference manager hygiene.
Project Setup → Documentation
Documentation rules for codebases: a README that answers install, run, and deploy in minutes, comments that explain why never what, docs colocated with code, examples that actually run, deleting stale docs, and ADRs for decisions.
Testing & Quality → Code Review
Running code review that actually improves code: correctness before style, small diffs for better review quality, severity-labeled comments, asking instead of commanding, responding to every comment, clear approval criteria, and automating what linters can catch.
Business Docs → Email Etiquette
Rules for writing B2B cold outreach emails that get replies instead of being marked as spam: earning the send, subject lines that read as internal, under-120-word structure, real personalization, and follow-up cadence.
Design & Art → Typography Color
Rules for building a UI color palette that works in practice: the 60-30-10 distribution, a single accent job, reserved semantic colors, WCAG text contrast ratios, light/dark variants, and naming tokens by role.
Social & Marketing → Other
Rules for managing a brand's social community day to day: response time and tone, handling public criticism, when to move a conversation to DM, moderation lines, rewarding contributors, and never arguing with trolls.
Rules for writing executive summaries that stand alone: decision-oriented content, strict length caps, what belongs versus what doesn't, and why the summary should always be written last.
API & Backend → Graphql
Design GraphQL APIs that scale: schema-first modeling, deliberate nullability, connection-style pagination, DataLoader batching, structured errors, and query depth/complexity limits.
SEO & Growth → Other
Rules for keyword research that maps to a real content strategy: search intent classification, long-tail versus head terms, difficulty-versus-relevance tradeoffs, clustering into topics, mapping keywords to pages, and avoiding cannibalization.