interfluence
Deprecated. Replaced by intervoice.
interfluence routed between voices by per-project file glob; intervoice reads one global multi-register profile (the shape voice profiles are actually kept in) and selects a register by name or inference. intervoice ports the useful parts (apply, compare, analyze, optimize, the voice-analyzer agent) and drops the MCP server, the corpus model, and the edit-logging hook. Do not run both installed at once; this plugin's PostToolUse hook is disabled to prevent double-logging during migration. Existing .interfluence/ profile data is preserved, not deleted.
A Claude Code plugin that learns how you write and makes Claude sound like you.
What this Is
Claude is excellent at generating documentation, READMEs, commit messages, and all the other text artifacts that accrue around a software project: but it doesn't sound like you. It sounds like a helpful, slightly over-eager assistant who has read too many style guides and not enough actual blog posts. interfluence fixes that.
You feed it samples of your writing (blog posts, docs, even emails), it builds a voice profile, and then you can apply that profile to anything Claude generates. The profile is prose, not numbers: turns out Claude follows "use em dashes for mid-sentence pivots and drop cultural references without explaining them" much better than "formality: 0.6, humor: 0.4."
How it works
The plugin has an MCP server that handles all the boring file management (corpus storage, profile CRUD, config), and Claude does all the actual NLP. This is a deliberate split: the server is a filing cabinet, Claude is the literary analyst. The voice analyzer runs on Opus and produces genuinely interesting analysis: it picks up on things like your relationship to parenthetical asides, whether you tend to front-load or back-load your punchlines, and which cultural references you reach for when you need a metaphor.
There's also a passive learning hook that quietly logs your edit diffs whenever you change something Claude wrote. Over time, those diffs tell interfluence what you keep fixing: and the next time you run /interfluence refine, it folds those patterns back into your profile. Capability is forged, not absorbed; the profile gets better as you use it.
Getting started
First, add the interagency marketplace (one-time setup):
/plugin marketplace add mistakeknot/interagency-marketplace
Then install the plugin:
/plugin install interfluence
Then:
-
Ingest your writing: /interfluence ingest: point it at files, directories, or URLs. More samples means a better profile, but even a single long blog post gives it enough to work with.
-
Analyze: /interfluence:voice-analyze: this runs the voice analyzer agent, which reads your entire corpus and produces a detailed prose profile covering sentence structure, vocabulary, tone, cultural references, and anti-patterns (things your voice would never do).
-
Apply: /interfluence apply: take any AI-generated content and rewrite it in your voice. You can also run /interfluence compare to see the original and voice-adapted versions side by side, which is helpful for calibrating how aggressive you want the restyling to be.
Architecture
.claude-plugin/plugin.json → Plugin manifest + MCP server declaration
server/src/ → MCP server (corpus CRUD, profile, config, learnings)
skills/ → ingest, analyze, apply, refine, compare
agents/ → voice-analyzer (Opus, deep literary analysis)
hooks/ → learn-from-edits.sh (PostToolUse on Edit)
commands/ → /interfluence router
Per-project data lives in .interfluence/: voice profile, config, corpus, and the raw learnings log. Nothing is stored globally; each project can have its own voice (or share one, if you copy the profile over).
Configuration
Manual mode by default: you explicitly call /interfluence apply when you want it. If you trust the profile enough to let it run automatically:
# .interfluence/config.yaml
mode: auto
autoApplyTo:
- "*.md"
- "docs/**"
But starting in manual mode and running /interfluence compare a few times first is the way to go. Verify the vibes before automating them.
Design decisions
A few choices worth calling out:
-
Prose profiles, not numeric scores. Claude follows "favor medium-to-long sentences with natural clause stacking" better than "sentence_length: 0.7." Natural language instructions are the native interface; why fight it?
-
Batched learning, not real-time. The edit hook logs diffs silently. You review them during /interfluence refine rather than having the profile mutate under you. This keeps the profile stable and predictable: you're always in control of what it learns.
