a7b15298e0
Brings 47 local-only files from backup-local-main into the merge-upstream
branch at their pre-rename paths. Subsequent steps will rename these to
the ce-* convention and port shared-file merges.
Includes:
- Custom skills: john-voice, jira-ticket-writer, hugo-blog-publisher,
weekly-shipped, proof-push, ship-it, story-lens, sync-confluence,
excalidraw-png-export, python-package-writer, fastapi-style,
upstream-merge
- Custom agents: design-conformance-reviewer, tiangolo-fastapi-reviewer,
zip-agent-validator, python-package-readme-writer, lint
- Custom commands: essay-edit, essay-outline, pr-comments-to-todos,
resolve_todo_parallel, workflows/{plan,review,work}
- Local mods to ce-review/SKILL.md + review-output-template.md (will be
ported to ce-code-review in a later step)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
28 lines
2.2 KiB
Markdown
28 lines
2.2 KiB
Markdown
---
|
|
name: john-voice
|
|
description: "This skill should be used whenever writing content that should sound like John Lamb wrote it. It applies to all written output including Slack messages, emails, Jira tickets, technical docs, prose, blog posts, cover letters, and any other communication. This skill provides John's authentic writing voice, tone, and style patterns organized by venue and audience. Other skills should invoke this skill when producing written content on John's behalf. Triggers on any content generation, drafting, or editing task where the output represents John's voice."
|
|
allowed-tools: Read
|
|
---
|
|
|
|
# John's Writing Voice
|
|
|
|
This skill captures John Lamb's authentic writing voice for use across all written content. It is a reference skill designed to be called by other skills or used directly whenever producing text that should sound like John wrote it.
|
|
|
|
## How to Use This Skill
|
|
|
|
1. Determine the venue and audience for the content being produced
|
|
2. Load `references/core-voice.md` — this always applies regardless of context
|
|
3. Load the appropriate venue-specific tone guide from `references/`:
|
|
- **Prose, essays, blog posts** → `references/prose-essays.md`
|
|
- **Slack messages, quick emails, casual comms** → `references/casual-messages.md`
|
|
- **Technical docs, Jira tickets, PRs, code reviews** → `references/professional-technical.md`
|
|
- **Cover letters, LinkedIn, formal professional** → `references/formal-professional.md`
|
|
- **Personal reflection, journal, notes** → `references/personal-reflection.md`
|
|
4. For prose and essays, also load `references/signature-moves.md` — these are the techniques that make the writing move
|
|
5. Apply both the core voice and the venue-specific guide when drafting content
|
|
6. Before finishing, run `references/revision-checklist.md` — if any item flags, rewrite before delivering
|
|
|
|
## 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 (NO emdashes!), it's catastrophically wrong.
|