ima-claude 2.20.0 → 2.26.0

package/plugins/ima-claude/skills/ima-editorial-scorecard/SKILL.md

@@ -7,7 +7,7 @@ metadata:
 
 # IMA Editorial Scorecard
 
-Score any piece of IMA content against editorial best practices and brand standards. Honest grades that help writers improve.
+Score IMA content against editorial best practices and brand standards. Honest grades that help writers improve.
 
 ## Invocation
 
@@ -16,16 +16,12 @@ Score any piece of IMA content against editorial best practices and brand standa
 /scorecard [content type: newsletter | webinar | blog | press-release | fundraising | op-ed | social]
 ```
 
-If content type isn't specified, auto-detect from structure and formatting cues.
-
----
+Auto-detect content type if not specified.
 
 ## Process
 
 ### Step 1: Identify Content Type
 
-Detect or confirm the format:
-
 | Content Type | Key Signals |
 |-------------|-------------|
 | Newsletter | "Dear {Person.firstName}", Quick Links block, multiple sections |
@@ -38,29 +34,26 @@ Detect or confirm the format:
 
 ### Step 2: Load Scoring References
 
-Read the appropriate reference files:
-- **[references/scoring-rubrics.md](references/scoring-rubrics.md)** — Grade-level criteria for all 5 categories
-- **[references/format-expectations.md](references/format-expectations.md)** — Voice check and structural expectations by content type
+- **[references/scoring-rubrics.md](references/scoring-rubrics.md)** — grade criteria for all 5 categories
+- **[references/format-expectations.md](references/format-expectations.md)** — voice and structural expectations by content type
 
 ### Step 3: Score Across Five Categories
 
-Evaluate the content against each category. Be honest — inflated scores help nobody.
-
 | Category | What to Evaluate |
 |----------|-----------------|
-| **Brand Voice** | Does this sound like IMA? Tone match for channel? Terminology compliance? |
-| **Evidence Quality** | Are claims supported? Sources cited? Precision of language? |
-| **Audience Clarity** | Will the target reader understand AND respect this? Plain language with precision? |
-| **Structural Craft** | Does the format follow IMA patterns? Logical flow? Scannable? |
-| **CTA Effectiveness** | Does the reader know what to do? Are CTAs specific and well-placed? |
+| **Brand Voice** | Sounds like IMA? Tone match for channel? Terminology compliance? |
+| **Evidence Quality** | Claims supported? Sources cited? Precise language? |
+| **Audience Clarity** | Target reader understands AND respects this? Plain language with precision? |
+| **Structural Craft** | Follows IMA format patterns? Logical flow? Scannable? |
+| **CTA Effectiveness** | Reader knows what to do? CTAs specific and well-placed? |
 
 ### Step 4: Assign Grades
 
-**Formatting rules (non-negotiable):**
-- Use **exact emoji characters**: `🟢` `🟡` `🔴` — never text substitutes
-- Use **whole letter grades only**: A, B, C, D, F — no `+` or `-` modifiers
-- Format as `🟢 A` (emoji + space + letter)
-- Notes column: 5-15 words max. The scorecard is a glance, not a report.
+**Non-negotiable formatting rules:**
+- Exact emoji: `🟢` `🟡` `🔴` — never text substitutes
+- Whole letter grades only: A, B, C, D, F — no `+` or `-`
+- Format: `🟢 A` (emoji + space + letter)
+- Notes: 5-15 words max
 
 | Grade | Indicator | Meaning |
 |-------|-----------|---------|
@@ -72,8 +65,6 @@ Evaluate the content against each category. Be honest — inflated scores help n
 
 ### Step 5: Compile & Present
 
-Present the scorecard in this exact format:
-
 ```markdown
 ## Editorial Scorecard
 
@@ -90,70 +81,54 @@ Present the scorecard in this exact format:
 > Reviewed: YYYY-MM-DD · Content Type: [type]
 ```
 
-Then provide the editorial memo:
-
-**What's Working** (2-3 bullets)
-- Specific things the content does well
-- Quote or reference the actual text
+Then provide editorial memo:
 
-**Priority Fixes** (2-3 bullets, ordered by impact)
-- Most impactful improvements first
-- Be specific: "Change X to Y" not "Improve the tone"
+**What's Working** (2-3 bullets) — specific strengths, quote actual text
 
-**Line-Level Notes** (if applicable)
-- Flag specific sentences, phrases, or sections
-- Suggest rewrites for the most critical issues
-- Call out AI tells, terminology violations, or unsupported claims
+**Priority Fixes** (2-3 bullets, ordered by impact) — "Change X to Y" not "Improve the tone"
 
----
+**Line-Level Notes** (if applicable) — flag specific sentences, suggest rewrites, call out AI tells or unsupported claims
 
 ## Special Checks
 
 ### AI Detection Flags
 
-Scan for these patterns and flag them in notes:
-
-- **AI openers**: "In today's rapidly evolving...", "In the realm of..."
-- **AI transitions**: Repeated "Moreover," "Furthermore," "It's worth noting"
-- **AI hedges**: "That being said," "It is important to note that"
-- **AI closers**: "In conclusion," at paragraph start
-- **Generic filler**: "Navigate the complexities," "At its core," "Delve into"
-- **Unnatural formality**: Passive constructions where active voice is standard for IMA
+Flag these patterns; if 3+ detected, deduct one letter grade from Brand Voice:
 
-If 3+ AI tells are detected, automatically deduct one letter grade from Brand Voice and note it explicitly.
+- Openers: "In today's rapidly evolving...", "In the realm of..."
+- Transitions: Repeated "Moreover," "Furthermore," "It's worth noting"
+- Hedges: "That being said," "It is important to note that"
+- Closers: "In conclusion," at paragraph start
+- Filler: "Navigate the complexities," "At its core," "Delve into"
+- Unnatural formality: passive constructions where IMA uses active voice
 
 ### Disclaimer Check
 
-For any content containing health information, verify:
-- Medical disclaimer present (or appropriate for format)
+For health content, verify:
+- Medical disclaimer present
 - "Not medical advice" language where needed
-- "Consult your physician" or equivalent for patient-facing content
+- "Consult your physician" for patient-facing content
 
 ### Independence Signal
 
-Verify that at least one of these independence markers appears:
+Verify at least one marker:
 - "Independent" in organizational description
 - "No pharma funding" or equivalent
 - "501(c)(3) nonprofit" identification
 - "funded by people/donors" language
 
-**Note:** Social posts are exempt from the independence signal check on individual posts — the profile bio and linked website carry this. Flag only if a statement or long-form social post lacks it.
-
----
+Social posts exempt from individual independence check — profile bio carries it.
 
 ## Guidelines
 
-- **Honest scores only.** A scorecard that says everything is an A is useless.
-- **Notes are terse.** 5-15 words per note. The scorecard is a glance.
-- **Format-aware grading.** A newsletter shouldn't be scored like a press release. A social post shouldn't be scored like a blog.
-- **Prioritize fixes by impact.** What single change would improve this most?
-- **Show, don't just tell.** When suggesting a rewrite, write the actual improved version.
-- **Date stamp every scorecard** so teams know how fresh the review is.
-- **Non-editorial team members** should be able to read and act on this feedback.
-
----
+- Honest scores only — an all-A scorecard is useless
+- Notes are terse: 5-15 words per note
+- Grade format-aware: newsletter ≠ press release ≠ social post
+- Prioritize fixes by impact — what single change improves this most?
+- Show rewrites, don't just describe them
+- Date stamp every scorecard
 
 ## Related Skills
 
-- **ima-copywriting**: Write new content or rewrite existing drafts
-- **ima-brand**: Source of truth for voice, tone, terminology
+- `ima-copywriting` — write or rewrite drafts
+- `ima-brand` — source of truth for voice, tone, terminology

package/plugins/ima-claude/skills/ima-editorial-workflow/SKILL.md

@@ -7,165 +7,120 @@ metadata:
 
 # IMA Editorial Workflow
 
-Orchestrates every editorial request through a structured sequence. This skill is the traffic controller — it manages the process and delegates writing to `ima-copywriting` and scoring to `ima-editorial-scorecard`.
+Traffic controller for all editorial requests. Delegates writing to `ima-copywriting`, scoring to `ima-editorial-scorecard`.
 
-## Invocation
+## Commands
 
 ```
 /write [type]          → Plan and draft new content
-/rewrite               → Review existing content, then improve it
-/social [category]     → Plan and draft a social media post
-/brainstorm [topic]    → Explore ideas and angles before committing
+/rewrite               → Review existing content, then improve
+/social [category]     → Plan and draft social post
+/brainstorm [topic]    → Explore ideas before committing
 ```
 
-Also triggers on natural language: "draft a newsletter," "improve this," "write a press release," "help me with this blog post," etc.
+Also triggers on: "draft a newsletter," "improve this," "write a press release," etc.
 
-**Content types for `/write`:**
-`newsletter` · `webinar` · `blog` · `press-release` · `fundraising` · `op-ed` · `social`
+**Content types (`/write`):** `newsletter` · `webinar` · `blog` · `press-release` · `fundraising` · `op-ed` · `social`
 
-**Categories for `/social`:**
-`video` · `statement` · `action` · `media-hit` · `announcement` · `journal` · `webinar-promo`
+**Categories (`/social`):** `video` · `statement` · `action` · `media-hit` · `announcement` · `journal` · `webinar-promo`
 
----
-
-## The Workflow
-
-Every editorial request follows this sequence. No diving straight into a draft. No three rounds of follow-up questions. Gather context once, execute cleanly, review honestly.
+## Workflow Sequence
 
 ```
-PLAN    → Identify intent, content type, gather missing context
-WRITE   → Draft using ima-copywriting + format reference + ima-brand
-REVIEW  → Score against standards using ima-editorial-scorecard
-APPROVE → Present for human decision with clear next actions
-LEARN   → Capture what worked for future drafts
+PLAN → WRITE → REVIEW → APPROVE → LEARN
 ```
 
----
-
-## PLAN (Always Runs First)
-
-Every editorial request starts with planning. Even quick ones. Especially quick ones.
+No diving straight into drafts. Gather context once, execute, review honestly.
 
-### Step 1: Detect Intent
+## PLAN
 
-| Command or Signal | Intent | Workflow Path |
-|-------------------|--------|---------------|
-| `/write`, "draft," "create," "new" | **Create** new content | Plan → Write → Review → Approve |
-| `/rewrite`, "improve," "fix," "edit," "make better" | **Rewrite** existing content | Plan → Review → Write → Review → Approve |
-| `/social` | **Create** social post | Plan → Write → Review → Approve |
-| `/brainstorm` | **Explore** before committing | Brainstorm → Plan (when ready) |
-| Pastes content, no instructions | **Ambiguous** | Ask: "Score this or rewrite it?" |
-| "Continue," "next version," "apply fixes" | **Iterate** | Skip Plan → Write |
+### Intent Detection
 
-**Note:** `/scorecard` is handled directly by the `ima-editorial-scorecard` skill, not this workflow.
+| Signal | Intent | Path |
+|--------|--------|------|
+| `/write`, "draft," "create," "new" | Create | Plan → Write → Review → Approve |
+| `/rewrite`, "improve," "fix," "edit," "make better" | Rewrite | Plan → Review → Write → Review → Approve |
+| `/social` | Create social | Plan → Write → Review → Approve |
+| `/brainstorm` | Explore | Brainstorm → Plan (when ready) |
+| Content pasted, no instructions | Ambiguous | Ask: "Score this or rewrite it?" |
+| "Continue," "next version," "apply fixes" | Iterate | Skip Plan → Write |
 
-### Step 2: Identify Content Type
+`/scorecard` handled directly by `ima-editorial-scorecard`, not this workflow.
 
-From the command argument, or detect from context, or ask.
+### Context Gathering (One Prompt, Not a Chain)
 
-### Step 3: Gather Context (One Prompt, Not a Chain)
+Use `ask_user_input` widget. Collect 2–3 answers in single structured prompt. Skip already-answered questions. Default aggressively — ask only what's genuinely missing. For iteration requests, skip Plan entirely. If user says "just do it," write with available context, note assumptions, flag gaps with `[brackets]`.
 
-**Use the `ask_user_input` widget** to collect 2–3 answers in a single structured prompt. Do not ask questions one at a time across multiple messages.
+**`/write [type]`:**
+- Core message — ONE takeaway
+- Reader action (widget: Read / Watch / Donate / Share / Sign / Attend / Download)
+- Source material (widget multi-select: Study · Webinar · Quote · Press release · External article · None)
+- Subject matter expert (optional)
+- Responding to external events? (optional)
+- Audience segment (widget: General supporters · Healthcare pros · Donors · Media · New subscribers)
 
-**Rules:**
-- If the user already provided enough context, skip answered questions. Don't ask "what's the content type?" when they said `/write press-release`.
-- Default aggressively. If someone says `/write fundraising` about the year-end campaign, you already know the audience, tone, and CTA structure. Ask only for what's genuinely missing.
-- For iteration ("apply the fixes," "next version"), skip Plan entirely.
-- If the user says "just do it," respect that. Write with available context, note assumptions, flag gaps with `[brackets]`.
-
-### Context Gathering by Command
-
-**`/write [type]` — Creating new content:**
-- Core message — what's the ONE takeaway? (open text)
-- Reader action — what should they do? (widget: Read / Watch / Donate / Share / Sign / Attend / Download)
-- Source material available? (widget multi-select: Study · Webinar · Quote from leader · Press release · External article · None yet)
-- Subject matter expert? (open text)
-- Responding to external events? (open text, optional)
-- Audience segment? (widget: General supporters · Healthcare pros · Donors · Media · New subscribers)
-
-**`/rewrite` — Improving content:**
-- What's wrong with it? (open text)
+**`/rewrite`:**
+- What's wrong with it?
 - Keep structure or rebuild? (widget: Keep structure · Rebuild)
-- Preserve specific elements? (open text, optional)
+- Preserve specific elements? (optional)
 
-**`/social [category]` — Social media post:**
-- Category, if not specified (widget: Video/Research · Statement · Action/Campaign · Media Hit · Announcement · Journal · Webinar Promo)
-- What are you promoting/announcing? (open text)
-- Link or media to attach? (open text)
-- Quote to feature? (open text, optional)
+**`/social [category]`:**
+- Category if not specified
+- What are you promoting/announcing?
+- Link or media to attach?
+- Quote to feature? (optional)
 
-**`/brainstorm [topic]` — Exploring angles:**
-- What's the topic or event? (open text)
-- Any format preference, or open to suggestions? (widget: Newsletter angle · Blog angle · Social angle · Op-ed angle · No preference)
-- What's the goal? (widget: Drive awareness · Drive action · Respond to news · Celebrate a win · Educate)
-
----
+**`/brainstorm [topic]`:**
+- Topic or event
+- Format preference (widget: Newsletter · Blog · Social · Op-ed · No preference)
+- Goal (widget: Drive awareness · Drive action · Respond to news · Celebrate win · Educate)
 
 ## WRITE
 
-After planning, load tools and draft:
+1. Load `ima-brand` (always)
+2. Load `ima-copywriting` (format template for content type)
+3. Check project Files for published examples as style benchmarks
+4. Write draft
+5. Self-check against Quality Checklist in `ima-copywriting`
 
-1. Load `ima-brand` skill (always — voice/tone authority)
-2. Load `ima-copywriting` skill (writing principles + format template for this content type)
-3. Check project Files for published examples of this format as style benchmarks
-4. Write the draft
-5. Self-check against the Quality Checklist in ima-copywriting
-
-**Deliver the draft with a brief note** on key editorial choices: why you opened this way, which template you followed, what still needs user input.
-
-**Use placeholder brackets** for anything you don't have: `[study name]`, `[specific finding]`, `[dollar amount]`, `[date]`. Never invent evidence.
-
----
+Deliver draft with brief note on key editorial choices. Use `[brackets]` for missing data. Never invent evidence.
 
 ## REVIEW
 
-Run the editorial scorecard — on your own draft (self-review) or user-submitted content.
-
-1. Load `ima-editorial-scorecard` skill
-2. Auto-detect content type or use what was specified
-3. Score across five categories: Brand Voice · Evidence Quality · Audience Clarity · Structural Craft · CTA Effectiveness
-4. Present scorecard table first, then What's Working, Priority Fixes, Line-Level Notes
+1. Load `ima-editorial-scorecard`
+2. Auto-detect content type or use specified
+3. Score: Brand Voice · Evidence Quality · Audience Clarity · Structural Craft · CTA Effectiveness
+4. Present: scorecard table → What's Working → Priority Fixes → Line-Level Notes
 
-**For self-review after writing:**
-- Be honest. If the draft you wrote has a weak opening or missing independence signal, say so.
-- Separate what *you* can fix on the next pass from what the *user* needs to provide (missing data, quotes, approvals).
+For self-review: be honest. Separate what you can fix from what the user must provide (missing data, quotes, approvals).
 
-**For user-submitted content:**
-- Score first, then ask if they want a rewrite.
-
----
+For user-submitted content: score first, then ask if they want a rewrite.
 
 ## APPROVE
 
-Present the work for human decision. Use the `ask_user_input` widget to offer clear next actions:
-
-| Option | What Happens Next |
-|--------|-------------------|
-| ✅ Approve | Content is ready. Move to Learn. |
-| 🔄 Revise | Apply specific changes. Return to Write. |
-| 🔁 Rebuild | Different approach. Return to Plan. |
-| 💬 Discuss | Talk through a section before deciding. |
+Present via `ask_user_input` widget:
 
----
+| Option | Next |
+|--------|------|
+| Approve | Ready. Move to Learn. |
+| Revise | Apply changes. Return to Write. |
+| Rebuild | Different approach. Return to Plan. |
+| Discuss | Talk through section before deciding. |
 
 ## LEARN
 
-After approval, briefly capture what worked or what the user corrected:
+After approval, capture what worked:
 
-> "Noted for future [content type] drafts:
-> - [Pattern worth reusing or correction to remember]"
+> "Noted for future [content type] drafts: [pattern or correction]"
 
 Examples:
-- "Noted: Dr. Varon prefers 'the IMA' in formal quotes, not just 'IMA.'"
+- "Noted: Dr. Varon prefers 'the IMA' in formal quotes."
 - "Noted: Year-end fundraising leads with match mechanic, not mission statement."
-- "Noted: Thread format (1/4) works well for journal promotions on social."
 
-If the learning should persist across sessions, ask: "Want me to remember this for future drafts?" and use memory.
-
----
+If learning should persist, ask: "Want me to remember this?" and use memory.
 
 ## Related Skills
 
-- **ima-brand**: Voice, tone, terminology, visual identity (ALWAYS load alongside)
-- **ima-copywriting**: Format templates, writing principles, CTA patterns, quality checklist
-- **ima-editorial-scorecard**: Scoring rubric for content review (handles `/scorecard` independently)
+- **ima-brand**: Voice, tone, terminology (ALWAYS load alongside)
+- **ima-copywriting**: Format templates, writing principles, quality checklist
+- **ima-editorial-scorecard**: Scoring rubric (handles `/scorecard` independently)

package/plugins/ima-claude/skills/ima-email-creator/SKILL.md

@@ -12,13 +12,9 @@ description: >-
 
 # IMA Email Creator
 
-Renders IMA-branded email HTML from editorial copy. Platform-agnostic — runs in any Claude environment.
+Renders IMA-branded email HTML from editorial copy. Platform-agnostic.
 
-## Core Principle
-
-**Email HTML is not web HTML.** Tables for layout, inline CSS only, 600px max width, test across clients.
-Gmail strips `<style>` blocks. Outlook uses Word's rendering engine, which breaks CSS floats and flexbox.
-Every layout decision must survive both.
+**Email HTML is not web HTML.** Tables for layout, inline CSS only, 600px max width. Gmail strips `<style>` blocks. Outlook uses Word's rendering engine — breaks CSS floats and flexbox.
 
 ## Decision Tree
 
@@ -30,7 +26,7 @@ What type of email?
 │   → references/drip-sequence.md
 ├── WordPress transactional (PHP)
 │   → references/wp-transactional.md
-├── Need EspoCRM compatibility info?
+├── EspoCRM compatibility info?
 │   → references/espocrm-compat.md
 └── General email CSS questions?
     → references/email-css-safe.md
@@ -38,9 +34,9 @@ What type of email?
 
 ## Quick Start
 
-1. Get copy from `ima-copywriting` (or user provides it)
-2. Choose email type above → load appropriate reference
-3. Render HTML using base template from `assets/base-template.html`
+1. Get copy from `ima-copywriting` (or user provides)
+2. Choose email type → load appropriate reference
+3. Render HTML using `assets/base-template.html`
 4. Write to `~/.claude/output/{name}.html` for browser preview
 5. Run EspoCRM prep if needed: `python3 scripts/espocrm-prep.py output.html`
 6. User pastes result into EspoCRM source view
@@ -52,7 +48,7 @@ What type of email?
 | `espocrm-prep.py` | Extract body, migrate styles to div wrapper | `python3 scripts/espocrm-prep.py input.html [--out output.html]` |
 | `css-inliner.py` | Inline style blocks into element attributes | `python3 scripts/css-inliner.py input.html [--out output.html]` |
 
-Install deps once: `pip install -r scripts/requirements.txt`
+Install once: `pip install -r scripts/requirements.txt`
 
 ## IMA Brand Colors
 
@@ -71,30 +67,28 @@ Install deps once: `pip install -r scripts/requirements.txt`
 
 - Tables for ALL layout — Outlook's Word engine breaks floats and flexbox
 - Inline CSS only — Gmail strips `<style>` blocks
-- 600px max width — universal client safe zone
-- Typography: Lato for headings (bold 700). Fallback: Arial, Helvetica, sans-serif. Open Sans for body text (regular 400). Fallback: Helvetica Neue, Helvetica, Arial, sans-serif
-- 16px minimum body text (accessibility for 50+ audience), 28px main headings, 20px section headings
-- Images: absolute URLs, explicit `width`/`height`, `display:block`, meaningful `alt`, 5px border-radius, max-width 580px in content area
+- 600px max width
+- Typography: Lato bold 700 for headings (fallback: Arial, Helvetica, sans-serif); Open Sans regular 400 for body (fallback: Helvetica Neue, Helvetica, Arial, sans-serif)
+- 16px minimum body text, 28px main headings, 20px section headings
+- Images: absolute URLs, explicit `width`/`height`, `display:block`, meaningful `alt`, 5px border-radius, max-width 580px
 - `role="presentation"` on all layout tables
-- Medical disclaimer in footer for any health content
+- Medical disclaimer in footer for health content
 - UTM parameters on all links (utm_term, utm_medium, utm_source, utm_content, utm_campaign)
 
 ## EspoCRM Variables
 
-Single-brace syntax (NOT Handlebars double-brace):
+Single-brace syntax (NOT Handlebars):
 - `{Person.firstName}` — first name (newsletters)
 - `{Person.name}` — full name (campaigns)
 - `{optOutLink}` — unsubscribe link (all emails, in footer)
 
 ## Builder Context
 
-Production emails are built in BeeFree and exported. Generate HTML that matches BeeFree's output patterns: `nl-container` → `row` → `row-content` stack → `column` structure. This ensures visual parity when HTML is imported back into BeeFree or compared against production exports.
+Production emails are built in BeeFree and exported. Match BeeFree output patterns: `nl-container` → `row` → `row-content` stack → `column`. Ensures visual parity on import.
 
-> **Brand evolution note:** Production emails prior to Brand Book v4.0 used Montserrat/#0296a1/#374751/14px.
-> New emails should follow the brand book values above. The structural patterns (BeeFree DOM, VML buttons,
-> CSS resets, EspoCRM variables) remain the same regardless of color/font choices.
+> Brand evolution: emails prior to Brand Book v4.0 used Montserrat/#0296a1/#374751/14px. New emails follow the values above. Structural patterns (BeeFree DOM, VML buttons, CSS resets, EspoCRM variables) remain the same.
 
-## Integration Points
+## Related Skills
 
 | Skill | Role |
 |-------|------|

package/plugins/ima-claude/skills/ima-forms-expert/SKILL.md

@@ -13,24 +13,13 @@ description: |
 
 # IMA Forms Expert
 
-WordPress form component library with Bootstrap 5 + functional programming patterns.
-
-## When to Use This Skill
-
-- Building custom forms using IMA Forms component library
-- Implementing template-driven validation (v1.3.0+)
-- Understanding validators-at-registration architecture (v1.4.0+)
-- Adding field types or container components
-- Creating repeater/dynamic field patterns
-- Integrating forms with WordPress (ACF, custom post types, AJAX)
-- Debugging form submission issues
+WordPress form component library — Bootstrap 5 + functional programming patterns.
 
 ## Core Principles
 
-- **Template IS the definition**: Field rendering auto-registers validation specs + validators
+- **Template IS definition**: Field rendering auto-registers validation specs + validators
 - **Validators at registration**: Field functions build closures at registration time (v1.4.0)
 - **Security by default**: Nonce verification, sanitization, escaping
-- **Component-based**: Reusable field and container components
 - **Bootstrap 5 native**: Uses Bootstrap utilities and components
 
 ## Architecture (v1.4.0 - Unified Validator Registry)
@@ -57,7 +46,7 @@ ima-forms/
 
 ### Validators-at-Registration Pattern (v1.4.0)
 
-**Key change from v1.3.0**: Validators are now built as closures at field registration time, not rebuilt by the engine via type-switching.
+Validators built as closures at field registration, not rebuilt by engine via type-switching.
 
 ```php
 // Inside ima_forms_email_field_register():
@@ -80,17 +69,12 @@ ima_forms_register_field_spec($name, [
 ]);
 ```
 
-**Benefits**:
-- Single source of truth: field function defines validation once
-- No type switching: validators are closures, just iterate and run
-- Testable: validators are pure functions captured at registration time
+Single source of truth — field function defines validation once, no engine type-switching.
 
 ## Key Patterns
 
 ### Template-Driven Validation
 
-Field functions auto-register specs + validators. Validate entire form in one call:
-
 ```php
 $result = ima_forms_validate_form('templates/forms/my-form', $_POST, 'my-form');
 
@@ -101,7 +85,7 @@ if (!$result['valid']) {
 $sanitized = $result['sanitized'];  // Ready to use
 ```
 
-→ **Details**: See [references/validation-engine.md](references/validation-engine.md)
+→ Details: [references/validation-engine.md](references/validation-engine.md)
 
 ### Enhanced Email Validation
 
@@ -148,28 +132,28 @@ add_action('wp_ajax_nopriv_contact_submit', 'contact_submit_handler');
 
 | File | Read When |
 |------|-----------|
-| [validation-engine.md](references/validation-engine.md) | Using `ima_forms_validate_form()`, understanding validator registry, custom validators |
-| [field-components.md](references/field-components.md) | Adding specific field types, customizing field behavior, repeaters |
-| [container-components.md](references/container-components.md) | Using cards, sections, column layouts, fieldsets |
-| [examples.md](references/examples.md) | Implementing complete new forms, testing patterns, anti-patterns |
+| [validation-engine.md](references/validation-engine.md) | Using `ima_forms_validate_form()`, validator registry, custom validators |
+| [field-components.md](references/field-components.md) | Adding field types, customizing behavior, repeaters |
+| [container-components.md](references/container-components.md) | Cards, sections, column layouts, fieldsets |
+| [examples.md](references/examples.md) | Complete form implementations, testing patterns, anti-patterns |
 | [quick-reference.md](references/quick-reference.md) | Function signatures, version features, filters |
 
 ## Common Tasks
 
 | Task | Approach |
 |------|----------|
-| Add a simple form | Use `ima_forms_form()` + field components + `ima_forms_validate_form()` |
-| Add custom validation | Filter: `add_filter('ima_forms_validate_{form-id}', ...)` |
-| Block spam emails | Set `enhanced_validation => true` on email fields |
-| Add repeater rows | Use `ima_forms_repeater()` with row callback |
-| Create multi-column layout | Use `ima_forms_column_layout(['columns' => 3, ...])` |
-| Debug validation | Use `ima_forms_debug_field_specs()` or `ima_forms_debug_validation_summary($specs)` |
+| Add simple form | `ima_forms_form()` + field components + `ima_forms_validate_form()` |
+| Add custom validation | `add_filter('ima_forms_validate_{form-id}', ...)` |
+| Block spam emails | `enhanced_validation => true` on email fields |
+| Add repeater rows | `ima_forms_repeater()` with row callback |
+| Multi-column layout | `ima_forms_column_layout(['columns' => 3, ...])` |
+| Debug validation | `ima_forms_debug_field_specs()` or `ima_forms_debug_validation_summary($specs)` |
 
 ## Success Indicators
 
-- ✅ Template-driven validation (no manual field maps)
-- ✅ Enhanced email validation on user-facing forms
-- ✅ Standardized form wrappers (`ima_forms_form()`)
-- ✅ Nonce verification in all AJAX handlers
-- ✅ Sanitized data used for processing (never raw `$_POST`)
-- ✅ Validators built at registration, not in engine
+- Template-driven validation (no manual field maps)
+- Enhanced email validation on user-facing forms
+- Standardized form wrappers (`ima_forms_form()`)
+- Nonce verification in all AJAX handlers
+- Sanitized data used for processing (never raw `$_POST`)
+- Validators built at registration, not in engine