writing-general
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
What this skill does
# General Writing Rules (Strunk & White)
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
## Core Principles
### The Iron Law of Good Writing
**Omit needless words.**
Every word must earn its place. Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences.
### Critical Rules
| Rule | Explanation |
|------|-------------|
| Write in prose | Avoid bullet points and lists unless explicitly requested |
| Use active voice | "The committee approved the plan" not "The plan was approved" |
| Be concrete | Specific details over vague abstractions |
| Put statements in positive form | Say what something is, not what it isn't |
| Use definite language | Avoid hedging, qualifiers, and weasel words |
### Red Flags - Stop If You Think
| Thought | Why It's Wrong | Do Instead |
|---------|----------------|------------|
| "I'll add some qualifiers to be safe" | Weakens the writing | Make definite assertions |
| "Let me list these points" | Bullet points are lazy | Write in prose paragraphs |
| "I should sound more formal" | Formality often means wordiness | Write naturally, then edit |
| "This needs more emphasis" | Overemphasis dilutes meaning | Let strong words speak |
## Rationalization Table - STOP If You Think:
| Excuse | Reality | Do Instead |
|--------|---------|------------|
| "The passive voice is fine here" | Passive voice hides the actor; name them | REWRITE in active voice |
| "This adverb adds emphasis" | Strong verbs don't need adverbs | DELETE the adverb, pick a stronger verb |
| "The reader needs this context first" | Lead with the point, add context after | MOVE the point to the front |
| "This paragraph needs one more sentence" | If the paragraph is complete, stop | STOP writing and move on |
| "I should vary the sentence structure" | Clarity beats variety; don't complexify for style | KEEP the clear structure |
### Delete & Restart Triggers
**If you catch yourself writing ANY of these, DELETE THE SENTENCE and START FRESH:**
| Anti-Pattern | Restart Approach |
|---|---|
| "It is [adjective] that..." | Rewrite as direct assertion |
| "There are [X] reasons" | Replace with direct list or synthesis |
| "In order to" | Replace with "to" |
| Sentence > 40 words with nested clauses | Break into 2-3 sentences |
| Passive voice hiding the actor | Name the actor, use active voice |
After deleting, restart the sentence with THE POINT first, then evidence.
**Skipping the deletion pass is NOT HELPFUL — the user publishes bloated prose that buries their argument.** Identify violations and purge them.
## Drive-Aligned Framing
**Skipping the sentence-level check is NOT HELPFUL — the user publishes weak prose that undermines their credibility.** Reading your own output and thinking "looks good" is not editing.
- You skip the style check because the content is correct. The prose reads as AI slop — your content expertise is hidden behind bad writing.
## Editing Checklist
### Sentence Level
- Remove unnecessary words ("in order to" → "to")
- Replace weak verbs ("is able to" → "can")
- Convert passive to active voice
- Eliminate redundancies ("past history" → "history")
### Paragraph Level
- Ensure each paragraph has one main idea
- Check topic sentences lead clearly
- Verify logical flow between paragraphs
### Word Level
- Replace abstract nouns with concrete ones
- Use specific verbs over vague ones + adverbs
- Cut filler words ("very", "really", "quite", "rather")
## Quick Reference: Common Fixes
| Weak | Strong |
|------|--------|
| utilize | use |
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| prior to | before |
| subsequent to | after |
| with regard to | about |
| a large number of | many |
| is able to | can |
## Progressive Disclosure
For comprehensive guidance, consult:
- **`references/elements-of-style.md`** - Complete Strunk & White guide covering:
- Elementary Rules of Usage (commas, colons, participles)
- Elementary Principles of Composition (paragraph unity, active voice)
- Words and Expressions Commonly Misused
- Style guidance and literary reminders
## Examples
**Weak original:**
> It is important to note that there are a variety of different factors that contribute to the overall success of the project in question.
**Strong revision:**
> Several factors determine project success.
**Weak original:**
> The report was written by the team and was subsequently reviewed by management prior to being distributed to stakeholders.
**Strong revision:**
> The team wrote the report, management reviewed it, and stakeholders received it.
## Integration
After completing any writing task, invoke `/ai-anti-patterns` to check for AI writing indicators.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.