voice updates
This commit is contained in:
1
bun.lock
1
bun.lock
@@ -1,5 +1,6 @@
|
|||||||
{
|
{
|
||||||
"lockfileVersion": 1,
|
"lockfileVersion": 1,
|
||||||
|
"configVersion": 0,
|
||||||
"workspaces": {
|
"workspaces": {
|
||||||
"": {
|
"": {
|
||||||
"name": "compound-plugin",
|
"name": "compound-plugin",
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
{
|
{
|
||||||
"name": "compound-engineering",
|
"name": "compound-engineering",
|
||||||
"version": "2.35.1",
|
"version": "2.36.0",
|
||||||
"description": "AI-powered development tools. 25 agents, 23 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
|
"description": "AI-powered development tools. 25 agents, 23 commands, 20 skills, 1 MCP server for code review, research, design, and workflow automation.",
|
||||||
"author": {
|
"author": {
|
||||||
"name": "Kieran Klaassen",
|
"name": "Kieran Klaassen",
|
||||||
"email": "kieran@every.to",
|
"email": "kieran@every.to",
|
||||||
|
|||||||
@@ -22,4 +22,4 @@ This skill captures John Lamb's authentic writing voice for use across all writt
|
|||||||
|
|
||||||
## Key Principle
|
## Key Principle
|
||||||
|
|
||||||
John prizes simplicity and clarity above all else. He writes to convey meaning, not to sound smart. If the output uses words John wouldn't say aloud to a friend, it's wrong. If it obscures meaning behind fancy language, it's wrong. If it sounds like a corporate press release or a ChatGPT default, it's catastrophically wrong.
|
John prizes simplicity and clarity above all else. He writes to convey meaning, not to sound smart. If the output uses words John wouldn't say aloud to a friend, it's wrong. If it obscures meaning behind fancy language, it's wrong. If it sounds like a corporate press release or a ChatGPT default (NO emdashes!), it's catastrophically wrong.
|
||||||
|
|||||||
@@ -72,13 +72,19 @@ John writes in first person almost exclusively. He uses "I" freely and without a
|
|||||||
|
|
||||||
He addresses the reader directly: "You'd be forgiven for thinking...", "You can see if there are any other cars near the spot", "Don't overthink it!"
|
He addresses the reader directly: "You'd be forgiven for thinking...", "You can see if there are any other cars near the spot", "Don't overthink it!"
|
||||||
|
|
||||||
|
## Diagrams Over Walls of Text
|
||||||
|
|
||||||
|
John believes a good diagram communicates faster and more clearly than paragraphs of explanation. When a concept involves relationships between components, flows, or architecture, default to including a diagram. A three-box flowchart with labeled arrows will land in seconds where three paragraphs of prose might lose the reader.
|
||||||
|
|
||||||
|
When the `excalidraw-png-export` skill is available, use it to generate hand-drawn style diagrams and export them as PNG files. This applies to technical explanations, architecture overviews, process flows, and anywhere a visual would reduce the reader's cognitive load. If the output is going somewhere that supports images (docs, PRs, Slack threads, emails), a diagram should be the first instinct, not an afterthought.
|
||||||
|
|
||||||
## Structure
|
## Structure
|
||||||
|
|
||||||
John's writing follows a consistent arc:
|
John's writing follows a consistent arc:
|
||||||
1. **Hook** — A concrete story, observation, or scenario (never an abstract thesis)
|
1. **Hook** — A concrete story, observation, or scenario (never an abstract thesis)
|
||||||
2. **Context** — Background the reader needs, delivered conversationally
|
2. **Context** — Background the reader needs, delivered conversationally
|
||||||
3. **Core argument** — The insight, always grounded in the concrete example
|
3. **Core argument** — The insight, always grounded in the concrete example
|
||||||
4. **Evidence/exploration** — More examples, data, or personal experience
|
4. **Evidence/exploration** — More examples, data, or personal experience (diagrams where visual clarity helps)
|
||||||
5. **Gentle landing** — A question, invitation, or understated conclusion (never a lecture)
|
5. **Gentle landing** — A question, invitation, or understated conclusion (never a lecture)
|
||||||
|
|
||||||
He almost never ends with a declarative thesis statement. He prefers to leave the reader with a question or a quiet observation.
|
He almost never ends with a declarative thesis statement. He prefers to leave the reader with a question or a quiet observation.
|
||||||
|
|||||||
Reference in New Issue
Block a user