ima-claude 2.14.1 → 2.16.0

package/plugins/ima-claude/skills/ima-email-creator/references/wp-transactional.md

@@ -0,0 +1,77 @@
+# PHP Email Template Patterns for WordPress
+
+## Architecture: Pure Function + WordPress Wrapper
+
+The IMA codebase separates email generation from sending:
+- **Pure functions** generate HTML/text with zero WordPress dependencies (testable)
+- **WordPress wrappers** handle side effects (wp_mail, user lookups, logging)
+
+## Brand Alignment Note
+
+WordPress transactional emails use the **ima-brand plugin colors**: `#00066F` Indigo headers, `#00B8B8` Aquatic Pulse CTAs, `#494949` Gravel text — applied via `ima_brand_email_wrapper()`.
+
+Marketing emails (BeeFree/EspoCRM drip and campaign) are now aligned to the same brand book colors: `#00B8B8` Aquatic Pulse CTAs, `#494949` Gravel text — replacing the old `#0296a1`/`#374751` palette. The only distinction is that transactional emails also use `#00066F` Indigo for headers (via `ima_brand_email_wrapper()`), which marketing email templates handle in their own header blocks.
+
+## The Brand Wrapper
+
+`ima_brand_email_wrapper()` from `ima-brand` plugin provides:
+- Consistent outer HTML structure (header with logo, footer)
+- Brand colors and typography
+- Location: `wp-content/plugins/ima-brand/includes/email-template.php`
+
+```php
+$html = ima_brand_email_wrapper($inner_html, $subject);
+```
+
+## Pure Template Pattern
+
+```php
+// inc/pure/email-templates.php
+declare(strict_types=1);
+
+function ima_build_invitation_email(array $data): string {
+    // Pure function — no WordPress calls, no side effects
+    $name = htmlspecialchars($data['name'], ENT_QUOTES, 'UTF-8');
+    // ... build HTML with inline styles ...
+    return $html;
+}
+```
+
+## WordPress Wrapper Pattern
+
+```php
+// inc/invitation-emails.php
+function ima_send_invitation_email(int $user_id, string $code): bool {
+    $user = get_userdata($user_id);
+    $html = ima_build_invitation_email([
+        'name' => $user->display_name,
+        'code' => $code,
+    ]);
+    $wrapped = ima_brand_email_wrapper($html, 'Your Invitation');
+    return wp_mail($user->user_email, 'Your Invitation', $wrapped, [
+        'Content-Type: text/html; charset=UTF-8',
+    ]);
+}
+```
+
+## Existing Email Modules
+
+| Module | Location | Purpose |
+|--------|----------|---------|
+| Invitations | child theme `inc/pure/email-templates.php` | Invitation, activation, application emails |
+| Payments | `ima-payments` plugin | Receipt emails with PDF attachments |
+| Memberships | `ima-memberships` plugin | Retention and welcome emails |
+| Registration | `ima-registration` plugin | Email verification codes |
+| Contact forms | `ima-forms` plugin | Form submission notifications |
+
+## Key Rules
+
+- Always escape: `htmlspecialchars($value, ENT_QUOTES, 'UTF-8')`
+- Set content type header: `Content-Type: text/html; charset=UTF-8`
+- Use `do_action('ima_log_info', 'Email sent to: ' . $email)` for logging
+- Plain text fallback via `wp_mail` multipart (optional but good practice)
+
+## When to Use This vs. Newsletter/Campaign
+
+- **This pattern**: System-triggered emails (verification, receipts, notifications) — lives in PHP, runs in WordPress
+- **Newsletter/Campaign**: Marketing emails created in Claude, pasted into EspoCRM — platform-agnostic HTML

package/plugins/ima-claude/skills/ima-email-creator/scripts/css-inliner.py

@@ -0,0 +1,47 @@
+#!/usr/bin/env python3
+"""
+Inline <style> blocks into element style attributes.
+
+Uses premailer to handle CSS specificity correctly. Designed for emails
+built with style blocks (e.g. BeeFree exports) that need inlining for
+Gmail compatibility.
+
+Usage:
+    python3 css-inliner.py input.html
+    python3 css-inliner.py input.html --out output.html
+"""
+
+import argparse
+import sys
+import premailer
+
+
+def inline_css(html: str) -> str:
+    return premailer.transform(
+        html,
+        remove_classes=False,
+        strip_important=True,
+        keep_style_tags=False,
+    )
+
+
+def main():
+    parser = argparse.ArgumentParser(description="Inline CSS for email compatibility")
+    parser.add_argument("input", help="Input HTML file")
+    parser.add_argument("--out", help="Output file (default: stdout)")
+    args = parser.parse_args()
+
+    with open(args.input, "r", encoding="utf-8") as f:
+        html = f.read()
+
+    result = inline_css(html)
+
+    if args.out:
+        with open(args.out, "w", encoding="utf-8") as f:
+            f.write(result)
+    else:
+        sys.stdout.write(result)
+
+
+if __name__ == "__main__":
+    main()

package/plugins/ima-claude/skills/ima-email-creator/scripts/espocrm-prep.py

@@ -0,0 +1,52 @@
+#!/usr/bin/env python3
+"""
+Extract body content from any HTML email and wrap it in a styled div.
+
+Strips document-level tags (<html>, <head>, <body>) and migrates body styles
+to a wrapping div. Works on BeeFree exports, IMA emails, or any HTML.
+
+Usage:
+    python3 espocrm-prep.py input.html
+    python3 espocrm-prep.py input.html --out output.html
+"""
+
+import argparse
+import sys
+from bs4 import BeautifulSoup
+
+
+def extract_body_content(html: str) -> str:
+    soup = BeautifulSoup(html, "html.parser")
+    body = soup.find("body")
+
+    if body is None:
+        return html
+
+    style = body.get("style", "")
+    inner_html = body.decode_contents()
+
+    if style:
+        return f'<div style="{style}">{inner_html}</div>'
+    return inner_html
+
+
+def main():
+    parser = argparse.ArgumentParser(description="Prepare HTML email for EspoCRM")
+    parser.add_argument("input", help="Input HTML file")
+    parser.add_argument("--out", help="Output file (default: stdout)")
+    args = parser.parse_args()
+
+    with open(args.input, "r", encoding="utf-8") as f:
+        html = f.read()
+
+    result = extract_body_content(html)
+
+    if args.out:
+        with open(args.out, "w", encoding="utf-8") as f:
+            f.write(result)
+    else:
+        sys.stdout.write(result)
+
+
+if __name__ == "__main__":
+    main()

package/plugins/ima-claude/skills/ima-email-creator/scripts/requirements.txt

@@ -0,0 +1,2 @@
+beautifulsoup4>=4.12
+premailer>=3.10

package/plugins/ima-claude/skills/prompt-starter/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: prompt-starter
+description: Zero-friction prompt templates (quick, brainstorm, plan-implement). Selects template, pre-fills from Jira, opens in GUI editor, reads back on close.
+---
+
+# Prompt Starter
+
+Load a structured prompt template, pre-fill it with Jira context, open it in the user's GUI editor, and execute the result when they close the file.
+
+**Trigger words:**
+- `brainstorm`, `research`, `explore` → `references/brainstorm.md`
+- `plan`, `implement`, `build`, `execute` → `references/plan-implement.md`
+- `quick`, or a short one-liner task → `references/quick.md`
+- Just a Jira key with no clear workflow → ask the user which template
+
+## Relationship to prompt_coach.py
+
+- **prompt-starter** = "What should my prompt say?" (template + context + editor)
+- **prompt_coach.py** = "Is my prompt good enough?" (quality evaluation)
+
+Different lanes, complementary. The coach may fire on the final prompt — that's fine.
+
+---
+
+## Template Selection
+
+Match the user's trigger words to select a template. Examples:
+
+| User says | Template |
+|---|---|
+| "brainstorm FNR-1234" | brainstorm.md |
+| "research auth options" | brainstorm.md |
+| "plan and implement FNR-567" | plan-implement.md |
+| "build the PDF export" | plan-implement.md |
+| "quick task: add validation" | quick.md |
+| "FNR-1234" (ambiguous) | Ask which workflow |
+
+---
+
+## Flow
+
+### Step 1: Select template
+
+Read the appropriate template from `references/`.
+
+### Step 2: Fetch Jira context (if Jira key present)
+
+Use mcp-atlassian to fetch the issue. Extract:
+- **Summary** → fills the one-line goal / user story
+- **Description** → fills the Problem section
+- **Acceptance Criteria** (from description or subtasks) → fills Acceptance / Test sections
+
+Map Jira fields to template `[bracket]` placeholders naturally — don't create a rigid substitution engine. Use judgment: if the Jira description is rich, use it; if sparse, leave the bracket hint for the user to fill in.
+
+### Step 3: Check prior work (plan-implement only)
+
+For plan-implement templates, search Serena memory for `{feature-name}-brainstorm`. If found, pre-fill the **Prior Work** section with a reference to it and incorporate key decisions into the **Plan** section.
+
+### Step 4: Write the pre-filled template
+
+Create the prompt directory if needed:
+```bash
+mkdir -p ~/.claude/prompts
+```
+
+Write the pre-filled template to `~/.claude/prompts/{session-name}.md` where session-name is descriptive:
+- `brainstorm-pdf-export.md`
+- `quick-email-validation.md`
+- `plan-fnr-1234.md`
+
+### Step 5: Open in editor (or present inline)
+
+**Quick template exception:** Quick templates are short (12 lines). Present them inline in the conversation — no editor spawn. Skip to Step 7.
+
+**For brainstorm and plan-implement templates**, spawn the user's GUI editor.
+
+#### Editor Resolution
+
+Claude Code owns the terminal, so terminal editors (nano, vim) cannot be used — the user can't interact with them. Only GUI editors work.
+
+Resolution order:
+1. `$VISUAL` — the Unix convention for GUI editors
+2. `$EDITOR` — but **only** if it's a known GUI editor: `zed`, `code`, `subl`, `gedit`, `kate`
+3. Auto-detect: check `which zed`, then `which code`, then `which subl` — use the first found
+4. **Fallback:** no suitable editor found → present inline and modify via conversation
+
+#### Spawning the editor
+
+Use Bash with `run_in_background: true`:
+```bash
+zed --wait ~/.claude/prompts/{session-name}.md
+```
+
+All GUI editors use `--wait` so the process blocks until the user closes the file/tab.
+
+Tell the user:
+> Template is open in {editor}. Edit and close the tab when done — I'll pick up from there.
+
+### Step 6: Read the result
+
+When the background task completes (editor closed), read the file back:
+```
+Read ~/.claude/prompts/{session-name}.md
+```
+
+### Step 7: Confirm and execute
+
+Present the final prompt to the user. Ask for confirmation:
+> Here's your prompt. Ready to execute, or want to adjust anything?
+
+On confirmation, treat the prompt content as working instructions and execute accordingly.
+
+---
+
+## Editor Notes for Team Onboarding
+
+Team members should set `$VISUAL` in their shell profile for the best experience:
+
+```bash
+# Zed
+echo 'export VISUAL="zed --wait"' >> ~/.bashrc
+
+# VS Code
+echo 'export VISUAL="code --wait"' >> ~/.bashrc
+
+# Sublime Text
+echo 'export VISUAL="subl --wait"' >> ~/.bashrc
+```

package/plugins/ima-claude/skills/prompt-starter/references/brainstorm.md

@@ -0,0 +1,25 @@
+[One-line goal as a user story]
+
+## Problem
+[What's broken or missing. Be specific about the symptom.]
+
+## Context
+[Repo, branch, related systems, infrastructure details]
+
+## Research
+- [Specific things to investigate, with scoped locations]
+- [Reference patterns to follow: "like X" or "see Y"]
+
+## Q&A
+After completing research, interview me using the AskUserQuestion tool.
+Dig into edge cases, tradeoffs, and constraints — skip obvious questions.
+
+- [Seed questions/concerns you already have]
+
+## Document
+Save the outcome to Serena memory as `{feature-name}-brainstorm`.
+Include:
+- Original user story and problem statement
+- Key findings from research
+- Decisions and tradeoffs from Q&A
+- Recommended approach (not a full plan — just direction)

package/plugins/ima-claude/skills/prompt-starter/references/plan-implement.md

@@ -0,0 +1,35 @@
+[One-line goal as a user story]
+Save this prompt and plan to Serena memory as `{feature-name}-plan`.
+
+## Problem
+[What's broken or missing. Be specific about the symptom.]
+
+## Prior Work
+[Reference brainstorming: "See Serena memory `{feature-name}-brainstorm`"]
+
+## Context
+[Repo, branch, infrastructure — if not already in brainstorming]
+
+## Plan
+- [Approach, informed by brainstorming outcomes]
+- [Open implementation questions with `?`]
+- [Constraints: "prefer X unless evidence shows Y"]
+
+## Implement
+[Numbered deliverables in priority order]
+
+For each story: Implement → Test → Review, then repeat for the full picture.
+
+## Test
+- [How to verify EACH deliverable]
+
+## Review
+- [Which review tool/agent and what to check for]
+
+## Document
+- [Explicit list of files to update]
+
+## Agents (recommended for multi-story work)
+- ima-claude:implementer for [phase] with skills: [...]
+- ima-claude:tester with /unit-testing
+- ima-claude:reviewer after implementation

package/plugins/ima-claude/skills/prompt-starter/references/quick.md

@@ -0,0 +1,11 @@
+[One-line goal — what and where]
+
+## Context
+[Repo/branch/file if not obvious from working directory]
+
+## Constraints
+- [Pattern to follow: "like X" or "match Y"]
+- [What NOT to do, if relevant]
+
+## Acceptance
+- [How to verify it works]