brainstorm
Explores requirements and approaches through collaborative dialogue before planning implementation.
Applies Strunk's Elements of Style principles when writing or editing prose.
$ npx -y skills add VeryGoodOpenSource/vgv-wingspan --skill elements-of-style --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/elements-of-styleContext preview
The summary Claude sees to decide when to auto-load this skill.
Applies Strunk's Elements of Style principles when writing or editing prose.
name: elements-of-style user-invocable: false description: Applies Strunk's Elements of Style principles when writing or editing prose. when_to_use: Triggers on "write clearly," "edit for style," "improve writing," or tasks requiring clear, vigorous English — documents, emails, reviews. compatibility: Designed for Claude Code (or similar products)
Apply these principles to produce clear, vigorous prose.
**Omit needless words.** Every word must earn its place. Cut filler phrases:
| Cut | Keep | |-----|------| | the question as to whether | whether | | owing to the fact that | since | | the fact that he failed | his failure | | he is a man who | he | | in a hasty manner | hastily |
**Use active voice.** Direct and forcible:
| Passive | Active | |---------|--------| | The first experiment was performed | We performed the first experiment | | It was believed by the committee | The committee believed |
**Put statements in positive form.** Avoid hedging with "not":
| Negative | Positive | |----------|----------| | He was not very often on time | He usually came late | | did not remember | forgot | | did not have confidence in | distrusted |
**Use concrete, specific language.** Vague abstractions weaken prose:
| Abstract | Concrete | |----------|----------| | A period of unfavorable weather set in | It rained every day for a week | | He showed satisfaction as he took possession of his reward | He grinned as he pocketed the coin |
**Keep related words together.** Subject and verb should not be separated unnecessarily. Place modifiers next to what they modify.
**Place emphatic words at the end.** The sentence's most important element belongs at its close.
**Avoid loose sentence chains.** Don't string clauses with "and," "but," "which." Vary structure: use semicolons, periodic sentences, or break into separate sentences.
**Express parallel ideas in parallel form:**
| Broken | Parallel | |--------|----------| | Formerly by textbook, while now the laboratory method | Formerly by textbook; now by laboratory |
| Avoid | Prefer | |-------|--------| | interesting | (make it interesting, don't announce it) | | certainly | (overused intensifier) | | kind of/sort of | rather, somewhat | | one of the most | (threadbare opening) | | along these lines | (vague) | | literally | (often misused for emphasis) | | case, character, nature | (usually redundant) |
Before finalizing any prose:
1. Can any words be cut without losing meaning? 2. Are verbs active where possible? 3. Are statements positive rather than hedged negatives? 4. Is language concrete and specific? 5. Do emphatic ideas land at sentence ends? 6. Is parallel structure consistent?
🦋 AI-assisted workflows that follow Very Good Ventures best practices and standards. Developed with 💙 by Very Good Ventures 🦄
Explores requirements and approaches through collaborative dialogue before planning implementation.
Executes an implementation plan — writes code and tests, runs quality review, and ships a pull request.
Stage, commit, push, and open a pull request following project conventions and the Conventional Commits spec. Accepts optional…
Scaffolds a new project by routing to the right companion plugin's create skill.
Produces a structured post-incident analysis — timeline, root cause, and actionable follow-ups — while context is fresh.
Applies a minimal, targeted fix for emergency bugs — enforces review and testing without brainstorm or planning phases.