elements-of-style
Elements of Style
Apply these principles to produce clear, vigorous prose.
Core Principles
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 |
More from verygoodopensource/vgv-wingspan
create
Scaffolds a new project by routing to the right companion plugin's create skill. Use when user says "create a project", "new flutter app", "start a dart package", "scaffold", or asks to set up a new codebase.
4debrief
Produces a structured post-incident analysis — timeline, root cause, and actionable follow-ups — while context is fresh. Use when user says "debrief", "post-mortem", "incident review", or "root cause analysis".
4hotfix
Applies a minimal, targeted fix for emergency bugs — enforces review and testing without brainstorm or planning phases.
4rebase
Rebases the current feature branch onto the base branch (main/master/develop). Use when user says "rebase", "sync branch", or "update branch".
4build
Executes an implementation plan — writes code and tests, runs quality review, and ships a pull request. Use when user says "build this", "implement the plan", "start coding", "execute the plan", or "ship it".
4plan
Turns high-level brainstorming and ideas into well-structured, actionable implementation plans. Use when user says "plan this", "create a plan", "how should we implement", or "write an implementation plan".
4