| name | yuumi:edit |
| description | Use when a document carries inline {curly-brace} edit notes to apply in place, or when scattered edits across long drafts or multiple files must stay consistent — no copy-paste round-trips |
| version | 1.6.4 |
Edit (Spatial Editing)
Overview
Position IS context. Instead of bringing text TO Claude, leave instructions WHERE they belong using {curly brace comments}.
When to Use
- Editing long documents with multiple scattered changes
- Making consistent edits across multiple files
- Draft revision workflow where you want to mark issues in-place
- Any situation where copy-paste back-and-forth is annoying
Not for: Single, focused edits where you can just describe what to change
The Command
/edit # File under discussion, or search for {thoughts}
/edit draft.md # Specific file
/edit draft.md notes.md # Multiple files
If no file is specified and none is obvious from the conversation, search the working directory for marker comments:
rg "\{[^}]+\}" --type md -l
The search defaults to documents because code files are full of literal braces. A code file the user explicitly names is fair game — handled by the instruction-vs-literal rule below.
Syntax
Mark edit instructions with curly braces {your instruction here}:
# Why Vaults Matter
Vaults give claude memory
{feels abstract - add concrete mechanism}
Without persistent storage claude forgets everything between sessions
{this is the key point, make it hit harder}
The solution is simple
{dont say simple, show it instead}
Processing Rules
- Read the file and identify all
{...} comments
- Tell instructions apart from literal braces. A
{...} is an edit instruction only when it reads as a natural-language note to the editor. Braces that belong to the content itself — code, template variables, JSON, math — are not instructions. When genuinely ambiguous, leave the text untouched and list the marker in the summary instead of guessing.
- Each comment applies to its surrounding context (paragraph, sentence, or section)
- Apply edits based on the instruction
- Remove the
{...} markers after processing
- Output summary of changes made
Output Format
After processing, show a summary:
Processed 3 edits in why-vaults-matter.md:
1. "feels abstract" → added concrete mechanism
2. "make it hit harder" → expanded with specific pain points
3. "dont say simple" → replaced with direct statement
Multi-File Consistency
When editing multiple files, ensure references stay consistent:
/edit api.md docs.md changelog.md
If api.md has {rename this endpoint to /users/profile}, update all references in other files too.
The Workflow
- Write your draft without stopping
- Quick read - drop
{thoughts} wherever something feels off
- Run
/edit
- Review changes
Common Instructions
| Instruction | Meaning |
|---|
{expand} | Add more detail |
{cut} | Remove this |
{too vague} | Make specific |
{example?} | Add an example |
{tone} | Adjust voice/style |
{→ section X} | This relates to another section |
