Add UK VAT blog post (#2747)

* Add UK VAT blog post

* format

* edit

* edit plots

* edit

* capital letter

* edit

* edit

* edit

* edit

* max comments

* edit

* max comments

* max comments

* edit tables and figs

* edit date

* edit numbers

* edit

* edit fig

* Improve UK VAT thresholds article clarity and conciseness

- Use active voice throughout with UK as subject
- Remove redundant explanations and duplicate table
- Eliminate unsupported adjectives/adverbs
- Tighten prose and reduce wordiness
- Clarify data construction attribution
- Improve title and subtitle for UK audience
- Add forward-looking conclusion without overcommitting

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

* Add article review standards based on VAT thresholds improvements

Document systematic improvements made to UK VAT thresholds article:
- Active voice and conciseness guidelines
- Data attribution and claims standards
- Structure and flow best practices
- Technical writing conventions
- Conclusion and title guidelines

These standards will help maintain consistent quality across all PolicyEngine articles and can be used to create automated review subagents.

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

* Fix markdown formatting to pass Prettier checks

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Max Ghenis <mghenis@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

Author: 3 people

CLAUDE.md

@@ -98,3 +98,48 @@
 - When describing higher-numbered deciles, prefer "higher-income" over "rich" or "wealthy"
 - When describing lower-numbered deciles, prefer "lower-income" over "poor"
 - Use precise language: "would" rather than "could" or "might" when describing modeled outcomes
+
+### Article Review Standards
+
+Based on our UK VAT thresholds article improvements, apply these standards to all PolicyEngine articles:
+
+#### 1. Active Voice and Conciseness
+
+- **Use active voice** with clear subjects (e.g., "The UK requires..." not "Businesses are required...")
+- **Remove redundancy** - Don't repeat information in multiple sentences
+- **Eliminate wordiness** - "We estimate that" → just state the finding
+- **Avoid empty phrases** - "It is important to note that" → just state the fact
+- **Combine related sentences** to reduce repetition
+
+#### 2. Data and Claims
+
+- **Only use adjectives/adverbs supported by data** - avoid "substantial," "significant," "slightly" unless quantified
+- **Be precise about data sources** - clearly attribute who constructed/analyzed what
+- **Remove obvious statements** - e.g., "Higher thresholds reduce revenue" when a chart shows this
+- **Avoid hedging without reason** - "approximately" only when rounding, not for exact model outputs
+
+#### 3. Structure and Flow
+
+- **Lead with findings** - put key results upfront, methodology details later
+- **Remove duplicate information** - don't present same data in both table and chart
+- **Keep introductions tight** - 1-2 paragraphs maximum
+- **Make transitions implicit** - avoid "In this section, we will..."
+
+#### 4. Technical Writing
+
+- **Spell out acronyms on first use** - "Retail Price Index (RPI)" then RPI thereafter
+- **Clarify baselines and assumptions** - be explicit about what's held constant
+- **Describe distributions accurately** - avoid "clustering" unless data shows clear bunching
+- **Use consistent terminology** - pick one term and stick with it
+
+#### 5. Conclusions
+
+- **Keep conclusions factual** - summarize findings without speculation
+- **Be specific about future work** - only mention planned analyses, not aspirations
+- **Avoid promotional language** - let the analysis speak for itself
+
+#### 6. Titles and Subtitles
+
+- **Make titles action-oriented** - "How X affects Y" rather than "Modelling X"
+- **Include key finding in subtitle** when possible
+- **Avoid redundant location markers** for country-specific sites (don't say "UK" on UK site)

changelog_entry.yaml

@@ -1,4 +1,4 @@
-- bump: patch
+- bump: minor
   changes:
-    fixed:
-      - Fixed UK behavioral response calculations returning zero FTE impacts by updating parameter names to match UK API expectations
+    added:
+      - A blog post for VAT threshold analysis tool for UK policy analysis