PraxisPlaybooks
00 ·Praxis Playbooks · Documented Production Systems
Praxis Playbooks is the working-systems library. Each playbook documents a production workflow: the architecture, the setup, the decision points, the runbook, the gotchas. No opinion pieces. No AI news recaps. Read one, build one. Biweekly target. Free.
01 ·Published
01 ·Lead intakeLive
Form submission lands in your CRM with the right owner, the right tag, and a Claude-classified urgency. Replaces the manual "who picks this up" Slack thread that runs every morning.
Read the playbook02 ·Signal digestLive
Daily Apify run pulls from your watch list, Claude summarizes the signal worth reading, your team gets one digest in #signal-feed at 8am instead of fifteen tabs at 11pm.
Read the playbook02 ·Coming soon
03 ·MCP integrationComing · Jun '26
A real data source (Airtable, Notion, Stripe, your DB) plumbed into your team's Claude Desktop or Cowork projects so the model reads the live state, not pasted screenshots. The full setup, including the auth handoff and the security boundary discussion most MCP guides skip.
Subscribe to be notified04 ·Cowork projectComing · Jul '26
How to turn a department's tribal knowledge into an LLM-native workspace where teammates can run "show me last week's churn signals" or "draft the weekly client update" with Claude using your real data, not hypotheticals. Includes the skills authoring conventions Praxis uses and the deploy-skill mechanism for distribution.
Subscribe to be notified05 ·Form to CRMComing · Aug '26
The depth version of the lead-intake playbook: multi-step form ingestion, dedup against existing records, multi-stage classification (industry, urgency, fit), automatic owner assignment, edge-case handling for malformed submissions. Reads as the Build-shape version of the Starter-shape playbook in #01.
Subscribe to be notified06 ·Daily briefingComing · Sep '26
The internal Praxis briefing system, documented end to end. Pulls from Calendar, Slack, Gmail, and project state. Composes against a written voice spec. Renders into a structured layout you read in five minutes. Includes the compliance lint pattern that catches voice drift before render.
Subscribe to be notified03 ·How these work
Each playbook documents a real production system. The architecture sits at the top: inputs, routing, integrations, outputs, edge handling. The setup walkthrough takes you through the build, step by step, on the canonical stack. Decision points flag where you might diverge from the canonical version. The runbook covers the actual operating pattern, not just the build. Gotchas are the edge cases we hit and how we handled them.
Playbooks are not opinion pieces and not AI news recaps. The goal is for an operating team to read a playbook on Tuesday and have a working version of the system shipped by the following Tuesday.