writing-econ
Internal skill for economics and finance writing. Loaded by /writing when style=econ. Based on McCloskey's "Economical Writing".
What this skill does
# Economics and Finance Writing
Style guide for economics journal articles, working papers, and finance analysis based on Deirdre McCloskey's *Economical Writing*.
## On Skill Load
**Step 1: Load base writing rules**
Read `${CLAUDE_SKILL_DIR}/../../skills/writing/SKILL.md` and follow its instructions.
**Step 2: Check for active workflow**
If `.planning/ACTIVE_WORKFLOW.md` exists and `workflow: writing`, update `style: econ`.
If no `.planning/PRECIS.md` exists in the project:
- Suggest: "No PRECIS.md found. Consider `/writing` to set up thesis, audience, and claims first."
**Step 3: Apply econ-specific rules below**
## When to Use
Invoke this skill for:
- Economics journal articles and working papers
- Finance analysis and market commentary
- Policy briefs and economic reports
- Editing economics/finance prose for clarity
**For general writing**: Use `/writing` skill (Strunk & White)
**For legal writing**: Use `/writing-legal` skill (Volokh)
## Enforcement
### IRON LAW #1: NO BOILERPLATE WITHOUT DELETE & RESTART
If you write ANY of these, DELETE the draft and START OVER:
- "This paper discusses..."
- Table-of-contents paragraph
- "As we shall see"
- "It is interesting to note that..."
- "The rest of this paper is organized as follows..."
These signal you haven't found your hook. Start fresh with a compelling finding.
### IRON LAW #2: NO ELEGANT VARIATION
One concept = One word. If you catch yourself varying terms ("industrialization" / "development" / "growth") for the same concept, you are confusing the reader. Pick ONE term and use it consistently.
### Rationalization Table - STOP If You Think:
| Excuse | Reality | Do Instead |
|--------|---------|------------|
| "But journals use boilerplate" | Bad journals do | HOOK reader with finding |
| "Elegant variation shows vocabulary" | Shows you don't know what you mean | USE same word for same thing |
| "Readers need roadmap paragraph" | They skip it | DELETE table-of-contents para |
| "This terminology is standard in field" | Doesn't make it good | USE concrete Anglo-Saxon words |
| "Need to sound academic" | Sounds pompous instead | WRITE like human being |
| "Passive voice sounds objective" | Sounds evasive | USE active voice |
| "Technical writing must be formal" | Technical ≠ turgid | BE clear AND technical |
### Drive-Aligned Framing
**Describing an empirical strategy without understanding the identification assumption is NOT HELPFUL — the referee rejects the paper for a fatal methodological gap.** Pattern-matching from similar papers is not econometric reasoning.
- You opened with "In recent years..." to seem academic. The reader recognizes it as AI filler — your opening destroyed credibility.
- You called the same variable "cost," then "expense," then "outlay" to avoid repetition. The reader thinks these are different concepts — your style created confusion.
- You described the empirical approach without addressing endogeneity. The referee rejects the paper — your omission was fatal.
### Red Flags - STOP Immediately If You Think:
- "Let me write a standard introduction" → NO. Find your hook first.
- "I'll improve this later" → NO. Fix boilerplate NOW or restart.
- "This varies the language nicely" → NO. Consistency > variation.
- "Readers expect this phrase" → NO. Expectations can be wrong.
### Delete & Restart Pattern
**When to delete and restart:**
1. **Boilerplate detected in first paragraph** → Delete entire intro, write finding-first
2. **Three different terms for same concept** → Delete section, pick ONE term
3. **Table-of-contents paragraph exists** → Delete it, no replacement needed
4. **Metric conversions every time** → Delete all but first, trust reader
**How to restart:**
```
Old: "This paper discusses the relationship between X and Y..."
New: "Trade liberalization increased wages by 15% for skilled workers."
```
Restart with THE FINDING, not with throat-clearing.
## Core Principles
### Speak to One Reader
Choose an implied reader and stick with her. A skeptical but sympathetic colleague. Keep the prose at one level of difficulty. If it embarrasses you to imagine how she would read it, the stuff is embarrassing.
### Avoid Boilerplate
| Anti-Pattern | Why It Fails |
|--------------|--------------|
| "This paper discusses..." | Bores the reader; use a hook instead |
| Table-of-contents paragraph | Readers skip it; they can't understand until they've read the paper |
| Background/padding | If you discovered it was beside the point, don't include it |
| "As we shall see" | Useless anticipation; the reader will see soon enough |
| Metric conversions every time | Shows you think the reader is an ignoramus |
Never repeat without apologizing ("as I said earlier"). If apologizing too much, you're repeating too much.
### Control Tone
- Avoid invective: "This is pure nonsense" arouses suspicion the argument is weak
- Delete every "very" and "absolutely" - most things aren't
- Use wit to compensate for strong opinions
- Relax the pose of The Scientist; write like a human being
### One Point Per Paragraph
End each paragraph with a simple, street-talk encapsulation. The paragraph can be technical as long as the last sentence comes down a notch. It makes the paragraph sing.
### Make Tables Self-Explanatory
The reader should understand the table without the main text. Use words in headings, not acronyms. "Logarithm of Domestic Price" not "LPDOM". Follow Tufte: no chart junk, have a point.
Use meaningful labels in equations: "Quantity of Grain = 3.56 + 5.6(Price of Grain)" not "Q = 3.56 + 5.6P where Q is..."
### Make Writing Cohere
Repeat key words to link sentences. (AB)(BC)(CD) is easy to understand. The figure is called polyptoton. English achieves coherence by repetition, not by "not only...but also" which marks you as incompetent.
## Word Choice
### Avoid Elegant Variation
Use one word to mean one thing. A paper used: "industrialization," "growing structural differentiation," "economic and social development," "development," "economic growth," "growth," and "revolutionized means of production" to mean the same thing. Don't.
When uncertain, look back and use the same word.
### Key Principles
| Principle | Example |
|-----------|---------|
| Be concrete | "sheep and wheat" not "natural resource-oriented exports" |
| Untie Teutonisms | "equalization of the prices of factors" not "factor price equalization" |
| Avoid ersatz economics | Never use "skyrocketing," "fair prices," "vicious cycle," "exploit" |
| Avoid this-ism | Replace *this*, *these*, *those* with *the* |
See `references/economical-writing-full.md` for extended bad words list, Teutonism examples, and ersatz economics vocabulary.
## Quick Reference
| Problem | Solution |
|---------|----------|
| "This paper discusses X" | Hook the reader with the finding |
| Table-of-contents paragraph | Delete it; readers skip it anyway |
| "As we shall see" | Delete; anticipation is useless |
| Elegant variation | Use the same word for the same thing |
| Five-dollar words | Anglo-Saxon roots are more concrete |
| Noun pile-ups | Untie with "of" |
| This/that/these/those | Replace with "the" |
| "Not only...but also" | Just use "and" |
## Progressive Disclosure
For comprehensive guidance, consult:
### Reference File
- **`references/economical-writing-full.md`** - Complete McCloskey guide covering:
- 35 rules with full explanations and examples
- Extended bad words list with usage notes
- Historical and etymological context
### When to Load Reference
Load the full reference when:
- Encountering specific vocabulary questions
- Needing detailed examples for economics jargon
- Working on substantial manuscript revision
- Teaching economics writing
## Integration
After completing any economics writing task, invoke `/ai-anti-patterns` to check for AI writing indicators. The `/writing` skill covers general prose principles (active voice, omit needless words) that complement this skill.
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.