Daniel Rosehill Hey, It Works!
A writing workspace for Claude Code that respects your voice
· Daniel Rosehill

A writing workspace for Claude Code that respects your voice

A structured workspace template for writing projects with Claude Code, built around preserving authorial voice and systematic version control.

One of the things I keep coming back to with Claude Code is how well it works as a writing environment, not just a coding one. The Claude Writing Space Template is a repository template I built to turn a Git repo into a structured writing workspace with AI-assisted editing, proofreading, and publishing workflows.

danielrosehill/Claude-Writing-Space-Template View on GitHub

The core philosophy: never overwrite originals

The biggest concern I had when building this was preserving authorial voice. AI editing tools have a tendency to homogenize writing, smoothing out the quirks and personality that make your writing yours. This template is built around a hard rule: edits always create new versions. Your original draft is never touched.

The versioning system is straightforward: draft-v1.md, draft-v2.md, draft-v3.md, and so on. Each version is a complete file, and you can always go back to any previous iteration. Combined with Git's own version history, you get an extremely detailed record of how a piece evolved.

Specialized agents and commands

The template ships with three agents and a set of slash commands designed around a typical writing workflow. The proofreader agent fixes typos and grammar while explicitly respecting your style. The version-manager handles creating incremental drafts with specific edits. And the archive-manager keeps your workspace tidy by organizing old versions into dated folders.

The slash commands map onto a natural writing flow: /setup to initialize a project, /proofread to clean up a draft, /new-version to create a revision with specific changes, and /publish to prepare content for your CMS or blog.

CMS integration

One of the features I'm most excited about is the headless CMS support. The /publish command can guide you through preparing content for platforms like Ghost, Strapi, or anything else with an available MCP server. Since Claude Code supports MCP integrations natively, you can go from draft to published post without leaving the terminal.

The directory structure keeps things organized: active drafts in working/, research materials in research/, brainstorming in notes/, and old versions neatly tucked away in archive/. It's the kind of setup that makes a long-running writing project manageable.

If you write regularly and already use Claude Code, give the template a try. It's MIT licensed and designed to be forked and customized.

danielrosehill/Claude-Writing-Space-Template View on GitHub