BriefDay turns Claude Code into a daily operating system. Get briefed every morning in 5 minutes. Never lose a decision, contact, or idea again. Now with an agent security layer, drift lint, and memory curation that keeps your context clean. One ZIP. 15 minutes to set up.
Built by a music tech executive who runs his entire business through this system.
All dogfooded in a production business for weeks before shipping. No vapor, no AI-generated "ideal workflow" theater.
Every skill file opens and closes with a
MANDATORY RULES block. Long-context models ignore
middle-of-file rules, so boundary anchoring reclaims compliance.
Layer: Tool Access
Every skill output ends with EVAL: PASS or
EVAL: FAIL [reason]. A Stop hook flags any output
missing its eval, so a worker cannot self-report "done" without a
verifier check.
Layer: Orchestration
SessionStart hook warns when memory.md crosses 180
lines, hard-warns at 200. Prevents silent context bloat as your
project count grows.
Layer: Memory
Three-category decision lens (Cat1 workflow, Cat2 ReAct, Cat3 multi-agent). Default answer: "No, it's Cat1." Kills 60-70% of over-engineered agent proposals.
Layer: Orchestration
Now self-classifies each component into Cat1/2/3 with a confidence score. Computes compounded uptime per category. You can override any classification.
Layer: Orchestration
Nine memory-integrity checks: broken pointers, orphan files, stale projects, inbox rot, duplicate entries, line budget, cross-ref overlap. Reports only, never auto-fixes.
Layer: Memory
Existing buyers: your download link in the original confirmation email always serves the latest ZIP. Re-download to get v3.0.
BriefDay is a complete configuration system for Claude Code. Skills, commands, agents, memory, RSS intelligence, and a daily rhythm that actually sticks.
/start, /sync, /wrap-up, /daily, /month-end. Your entire day in three touchpoints taking under 10 minutes total.
Claude Code now remembers across sessions natively. BriefDay is the discipline that keeps that memory clean: what to save, dedupe before writing, prune the rot at /month-end.
Drop files, articles, screenshots, PDFs into inbox/. BriefDay categorizes, scores, extracts insights, and archives everything.
14 starter feeds with scoring, keyword boosts, and deep-read delegation. Surfaces only what matters to your business.
Content reviewer catches AI writing tells. Intel analyst deep-reads articles in background. Model routing keeps costs down.
Hooks block destructive commands. Blast radius discipline on multi-file changes. Turn limits prevent agent runaway. Security audit skill checks your products before launch.
A tainted-input gate blocks state-mutating tools when their parameters came from untrusted content. Connector privilege audit flags dual-role servers. Supply-chain guards on every install.
A flag-only script checks stated counts against what is actually on disk, catches silently dead hooks, and surfaces stale instructions and agents missing tool grants. Never auto-fixes.
Anti-AI writing rules, ban lists for corporate fluff, position calibration so Claude writes at your level (not a beginner's).
Spaced-repetition motivation from 8 classic books. Context-aware triggers surface the right wisdom at the right moment.
LinkedIn ghostwriter, research digest, pitch deck builder, opportunity scanner, quality gate, skeptic review, reliability calculator, lint-brain, security hygiene, and more. All auto-activate.
Right-click any link or page to save it to your inbox. Next /sync picks it up, scores it, and archives it. Two-click capture from anywhere.
Create an inbox shortcut on your Desktop. Drag articles, PDFs, screenshots straight in. BriefDay processes everything at /start and /sync.
Unzip, run the setup script, fill in your context. Claude Code handles the rest.
The setup script asks your name, role, industry, and expertise level. Creates all directories and personalizes your config.
./setup.sh
Open CONTEXT.md and replace placeholders with your real info. The more specific you are, the better the AI performs.
CONTEXT.md
Open Claude Code and type /start. Your first personalized briefing runs in under 5 minutes. Drop a link in inbox/, type /sync, and watch it process. Memory builds over 5-7 sessions.
/start
Each skill is a markdown file with YAML frontmatter. Claude loads the right one based on what you're doing. No manual switching.
| Skill | What It Does |
|---|---|
| inbox-processor | Scores, categorizes, and archives inbox items with AI triage |
| linkedin-ghostwriter | Drafts LinkedIn posts in your voice with hook optimization |
| research-digest | Synthesizes articles and research into actionable briefs |
| rss-reader | Fetches and scores RSS feeds with keyword relevance |
| opportunity-scanner | Scans intel for business opportunities and partnership signals |
| context-engineering | RORE framework for building high-quality AI context |
| quality-gate | Multi-pass quality checks before any deliverable is final |
| skeptic-review | Adversarial review that stress-tests ideas and proposals |
| content-repurposer | Turns one piece of content into multiple formats |
| product-auditor | Audit any product for positioning, pricing, and market fit |
| planner-worker-judge | Multi-agent pattern: plan, execute, review |
| product-forge | Full product ideation to build pipeline |
| pitch-deck-builder | 3-phase pitch deck pipeline (Scout/Architect/Builder) |
| outreach-forge | B2B prospecting with parallel research agents |
| presentation-system | HTML slide decks with branded themes |
| security-audit | 3-category security, resilience, and scale audit with fix prompts |
| security-hygiene | Tainted-input gate, connector privilege audit, and supply-chain guards for agent workflows |
| reliability-calculator | Map agent stack to six infrastructure layers, score weakest link |
| lint-brain | 9 integrity checks on your memory system (broken pointers, orphans, rot) |
| open-loop-audit | Surface stalled projects and unresolved decisions |
| knowledge-search | Full-text search across your entire knowledge base |
60-70% of "I need an agent" problems are actually Category 1 deterministic workflows. Misclassifying costs you 10x in infrastructure, tokens, and debugging time. Here's the three-category lens BriefDay uses internally.
Fixed sequence, same input same output. No branching reasoning. Ships as a skill, hook, or bash script. Default answer: yes, it's Cat1. Typical uptime ceiling: 99.9%+.
Examples: inbox scoring, RSS fetch, daily brief generation, em dash detection, lint checks.
Tool loops with judgment. Iterative refinement, unpredictable paths, LLM decides next step. Ships as a subagent. Only promote here when Cat1 cannot model the problem. Typical uptime: 95-99%.
Examples: deep research, competitive analysis, adversarial review, exploratory web scraping.
Specialized agents collaborating. Red flag if proposed. Compounds handoff risk and failure modes. Almost never the right answer. Typical uptime: 90-98%.
Examples: truly open-ended goals with mandatory specialization. If you are not sure, it is not Cat3.
Default answer to "should this be an agent?" is "No, it's a Category 1 workflow." Only promote to Cat2 when the workflow literally cannot handle the branching. Never jump to Cat3.
Common failure mode: benchmarking Cat1 tools against Cat2 agents on
the same spreadsheet. They are architecturally different systems and
should not be compared on uptime or cost. BriefDay's
reliability-calculator skill
runs this classification on your stack and computes compounded
uptime per category.
BriefDay works for anyone who uses Claude Code and wants more than a chatbot.
"I already use Claude Code daily. I want a system, not a blank terminal. BriefDay gave me memory, agents, and a daily rhythm in 15 minutes."
"I don't code. I drop things in a folder, type /start, and get briefed. The inbox processing alone saved me an hour a day."
"I had Claude Pro but didn't know what to do with Claude Code. BriefDay showed me. Now I run /sync between meetings."
BriefDay was built by a music tech executive who runs multiple companies through this system daily. 20+ years in digital distribution, platform ops, and revenue strategy. Former SVP at a major Latin label. Co-founder of a boutique distribution company.
Every skill, command, and workflow in BriefDay exists because it solved a real problem in a real business. The memory system, the RSS intelligence, the inbox processing, the content pipeline: all battle-tested across 12+ months of daily sessions.
You're not buying a template. You're buying a year of refinement.
Less than one month of most AI subscriptions. Pays for itself in the first week. No tiers. No recurring fees.
14-day money-back guarantee. No questions asked.
By purchasing, you agree to our Terms of Service.
Free
The foundation BriefDay is built on. See how a real CLAUDE.md works before committing.
One email with the download. No spam.
$67 one-time
Everything in the Starter Kit, plus the complete operating system.
14-day money-back guarantee.
No. You unzip a folder, run a setup script, and type /start. The config files are markdown (plain text). If you can edit a text file, you can use BriefDay.
Claude Code (requires a Claude Pro, Team, or Enterprise subscription from Anthropic). macOS, Linux, or WSL. Python 3.8+ for the scripts.
BriefDay ships in safe mode. Hooks block destructive commands (rm -rf, force push, etc.). Memory gets backed up before edits. No skip-permissions required.
Custom instructions are a paragraph of text. BriefDay is an entire system: 21 skills that auto-activate, a curation discipline on top of Claude Code's native persistent memory, an agent security layer, RSS feeds, inbox processing, multi-agent delegation, and a daily workflow. It turns Claude Code into an operating system.
Every AI agent depends on six infrastructure layers: compute, identity, memory, tool access, billing, and orchestration. You handle compute and billing (Claude Code + Anthropic subscription). Claude Code now remembers natively, so BriefDay hardens the three that actually break: memory that stays clean instead of rotting, tools that work without configuration, and orchestration that doesn't lose your work when context compacts. v3.0 moves specific rules from "Claude should do X" to "the system ensures X."
No. Updates are included in your one-time purchase. The download link in your original confirmation email always serves the latest ZIP. Re-download to get v3.0. Your existing CLAUDE.md will not be overwritten, the setup script will ask before touching any file.
That's the entire point. The setup script personalizes your config. CONTEXT.md is a fill-in-the-blank profile. Add your own RSS feeds, contacts, decision filters, and voice rules. Three industry examples are included.
BriefDay's CLAUDE.md is modular. You can merge sections into your existing config or use BriefDay's as a fresh start. The setup script won't overwrite anything without asking.
Yes. v3.0 "Native" shipped 2026-07-13 with an agent security layer, drift lint, and memory curation on top of Claude Code's native persistent memory. Every prior feature (memory guardrails, EVAL terminators, agent taxonomy lens, /lint-brain) carries forward. Updates are included for all future versions. The system is also designed to be extended by you over time.
14 days, no questions asked. If BriefDay isn't for you, email us and you get a full refund.
Most people hit the habit around session 5. That's when /sync saves you real time and memory starts carrying context you didn't have to re-type. If you don't see value in 14 days, full refund.
One-time, forever yours. No subscription. You get all updates to the current major version. v3.0 is the latest.
You could. It took 12 months to build this one. BriefDay gives you the system, the skills, the scripts, the memory architecture, and the daily workflow out of the box. You customize it. You don't have to build it from scratch.
BriefDay is a framework, not a rigid template. The setup script asks your name, role, and industry. CONTEXT.md is fill-in-the-blank. Voice.md adapts to your writing style. Three examples ship (consultant, developer, founder), but the system works for any knowledge worker.
BriefDay is a single-user system (one license = one person). Each person gets their own config, memory, and context. Looking for a team setup? Email [email protected] and we'll work something out.