Vol. I · No. 001 · v1.0 · The Consulting Edition

The Claude Compendium

Compiled by SuRaM
Principal Consultant, Forcey
April 2026
— an opinionated field guide to every feature, how it maps to the market, and one hundred ways to put it to work —
I

The Lay of the Land

what you're actually buying into

Claude is no longer just a chatbot. In the last six months it has grown limbs — a design studio, an autonomous teammate, a coding agent that ships PRs, a browser operator, and a spreadsheet/slide native. The surface area is now wide enough that keeping a client current is itself a consulting deliverable.

The consulting read. Treat Claude as a platform, not a product. The billable insight isn't "use Claude" — it's knowing which surface (Web, Desktop, CLI, Excel, Chrome, Slack, API) fits which workflow, and which incumbent it credibly threatens this quarter.

This compendium is organised in four parts. The Feature Catalog lists every shipped capability with platform availability. Vs. The Industry maps each feature to the incumbents it displaces, enhances, or respects. 100 Use Cases is the imagination library — tagged by domain, stack, and platform. The Daily Digest Playbook is the meta-layer: how to use Claude itself to stay ahead of Claude.

40+
Shipped Features
7
Surfaces / Clients
100
Use Cases Catalogued
1M
Token Context (Max)
Opus 4.7
Flagship Model
Apr '26
Claude Design Debut

Numbers shift weekly. The Digest Playbook at the back of this volume is how you keep them honest.

II

The Feature Catalog

every surface, every capability
Available Partial / Beta Not on this surface
III

Vs. The Industry

who loses sleep, who shrugs

A frank assessment. "Displaces" means the incumbent is at real risk for the stated job-to-be-done. "Enhances" means Claude makes the incumbent more valuable, not less. "Respects" means the moat still holds.

IV

One Hundred Ways

creative, practical, billable
V

The Digest Playbook

use Claude to stay ahead of Claude

The fastest way to stay current on Claude is to put Claude to work on it. Here is a four-layer system — a daily artifact you'll actually open, powered by the same tools you're tracking.

LAYER 01 · COLLECTION

A Cowork Project that wakes up before you do

In the Claude Desktop app, create a Cowork Project named Claude Daily Brief. Drop in the four canonical source URLs below as context files. Cowork Projects support scheduled recurring tasks — set one for 06:30 local time.

Every weekday at 06:30: 1. Fetch the Anthropic News, Release Notes, and Claude Code changelog pages. 2. Web-search "Claude" from the last 24h, filtering X/Reddit/LinkedIn/Hacker News. 3. Deduplicate. Cluster by theme. 4. Write a 400-word brief with: • What shipped (official) • What's being built with it (community) • What press is saying (analysts) • One "consulting angle" per item. 5. Save to this Project as today's date.
  • Official
    anthropic.com/news
  • Changelog
    code.claude.com/docs/en/changelog
  • Community
    r/ClaudeAI, X list, LinkedIn
  • Press
    TechCrunch, The Information, VentureBeat
LAYER 02 · CURATION

A Skill that enforces your editorial voice

Raw research isn't a digest. Build a custom Skill called Consulting Digest Format that defines your house style: BLUF at top, "So what for the client" paragraph, one crisp recommendation, no hype language. The Skill auto-activates whenever the Cowork task runs.

Skill rules: • Max 400 words, scannable in 90 seconds • Banned words: "revolutionary", "game-changer", "disrupting", "AI-powered" • Every item ends with: "Billable angle: …" • Flag breaking changes with [BREAKING] • Flag preview/research features with [PREVIEW]
LAYER 03 · PRESENTATION

An Artifact that renders the brief

Ask Claude to produce the brief as an HTML Artifact — a newspaper-style single page, dated, with anchor links and a "forward this to a client" button that copies a cleaner plaintext version. Pin the Artifact to your Project. Each day's Artifact is a permanent, searchable record.

Output contract: • Standalone HTML Artifact (one file) • Three sections: Shipped / Built / Said • Footer: next three things to watch • Copy-as-plaintext control • Dark serif headline, mono metadata
LAYER 04 · DISTRIBUTION

MCP connectors that close the loop

Connect Gmail and Slack via MCP. Extend the scheduled task to email the Artifact to yourself and post a three-bullet TL;DR to a private Slack channel. For consulting, add a second task that runs weekly on Fridays to synthesise the five daily briefs into a client-ready PDF via Claude's file creation.

Weekly Friday 16:00 task: 1. Read all 5 daily briefs from this week. 2. Synthesise into: Themes / Movers / Risks. 3. Produce a branded PDF (docx skill). 4. Draft 3 LinkedIn post options. 5. Email to me with subject "Weekly Claude Brief — week of {date}"
Why this works for consulting. You end up with a dated, searchable archive of every Claude shift — proof-of-currency for RFPs, raw material for thought-leadership posts, and a gift you can send to clients without breaking your morning. The entire system is meta: it uses Cowork Projects, Skills, MCP, Artifacts, and file-creation — precisely the features you're tracking.