ima-claude 2.16.0 → 2.20.0

package/plugins/ima-claude/skills/mcp-atlassian/references/direct-api-sprints.md

@@ -0,0 +1,158 @@
+# Atlassian Direct API — Sprint & Board Management
+
+MCP gap: no Scrum/Kanban board or sprint tools. The Agile API uses a different base path.
+
+See [direct-api-auth.md](direct-api-auth.md) for auth setup.
+
+All examples use Gateway (Bearer) auth. The Agile API base is:
+```
+https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0
+```
+
+---
+
+### List Boards
+
+**API:** `GET /rest/agile/1.0/board`
+**When:** Finding the board ID for a project.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/board?projectKeyOrId=PROJ" \
+  | jq '.values[] | {id, name, type}'
+```
+
+#### Notes
+- Filter by project with `projectKeyOrId` param
+- `type` is `scrum` or `kanban`
+- Board ID is needed for all subsequent sprint operations
+
+---
+
+### Get Active Sprint
+
+**API:** `GET /rest/agile/1.0/board/{boardId}/sprint?state=active`
+**When:** Finding the current sprint to add issues to.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/board/42/sprint?state=active" \
+  | jq '.values[] | {id, name, state, startDate, endDate}'
+```
+
+#### Notes
+- `state` filter accepts: `future`, `active`, `closed`
+- Multiple states: `state=active,future`
+- Only Scrum boards have sprints — Kanban boards return empty
+
+---
+
+### Get Issues in a Sprint
+
+**API:** `GET /rest/agile/1.0/sprint/{sprintId}/issue`
+**When:** Reviewing what's in a sprint.
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100/issue?fields=summary,status,assignee" \
+  | jq '.issues[] | {key, summary: .fields.summary, status: .fields.status.name}'
+```
+
+#### Notes
+- Use `fields` param to limit response size (same as Jira REST API v3)
+- Supports `jql` param for additional filtering within the sprint
+- Paginated: use `startAt` and `maxResults` for large sprints
+
+---
+
+### Move Issues to a Sprint
+
+**API:** `POST /rest/agile/1.0/sprint/{sprintId}/issue`
+**When:** Adding issues to a sprint (sprint planning).
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"issues": ["PROJ-101", "PROJ-102", "PROJ-103"]}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100/issue"
+```
+
+#### Notes
+- Accepts issue keys or issue IDs
+- Issues are moved from their current sprint (or backlog) to the target sprint
+- No response body on success (HTTP 204)
+- To move to backlog: use `POST /rest/agile/1.0/backlog/issue` with same body
+
+---
+
+### Create a Sprint
+
+**API:** `POST /rest/agile/1.0/sprint`
+**When:** Setting up a new sprint.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Sprint 42",
+    "originBoardId": 42,
+    "startDate": "2026-04-06T09:00:00.000Z",
+    "endDate": "2026-04-20T17:00:00.000Z",
+    "goal": "Complete auth migration"
+  }' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint" \
+  | jq '{id, name, state}'
+```
+
+#### Notes
+- `originBoardId` is required — use the board ID from "List Boards"
+- Dates are ISO 8601
+- Sprint starts in `future` state
+
+---
+
+### Start or Close a Sprint
+
+**API:** `PUT /rest/agile/1.0/sprint/{sprintId}`
+**When:** Starting a planned sprint or closing a completed one.
+
+```bash
+# Start a sprint
+curl -s -X PUT \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"state": "active"}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100"
+
+# Close a sprint (must specify where incomplete issues go)
+curl -s -X PUT \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"state": "closed"}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/sprint/100"
+```
+
+#### Notes
+- Only one sprint can be `active` per board at a time
+- When closing, incomplete issues move to the backlog by default
+- To move incomplete issues to a specific sprint, close the sprint via the Jira UI (API doesn't support the move-to-sprint parameter natively)
+
+---
+
+### Move Issues to Backlog
+
+**API:** `POST /rest/agile/1.0/backlog/issue`
+**When:** Removing issues from a sprint without deleting them.
+
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $ATLASSIAN_BEARER_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"issues": ["PROJ-101", "PROJ-102"]}' \
+  "https://api.atlassian.com/ex/jira/$ATLASSIAN_CLOUD_ID/rest/agile/1.0/backlog/issue"
+```

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

@@ -1,11 +1,13 @@
 ---
 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.
+description: Build better prompts from rough ideas. Selects template, pre-fills from Jira, opens in GUI editor, returns refined prompt. Does NOT execute the work — only crafts the prompt.
 ---
 
 # 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.
+**You are a prompt builder, not an executor.** Your job is to take a rough idea and produce a well-structured, context-rich prompt. You NEVER execute the work described in the prompt — you only craft and return it.
+
+Load a structured prompt template, pre-fill it with Jira context, open it in the user's GUI editor, and return the refined prompt for the user to run.
 
 **Trigger words:**
 - `brainstorm`, `research`, `explore` → `references/brainstorm.md`
@@ -103,12 +105,13 @@ When the background task completes (editor closed), read the file back:
 Read ~/.claude/prompts/{session-name}.md
 ```
 
-### Step 7: Confirm and execute
+### Step 7: Present the finished prompt — STOP
+
+Present the final prompt to the user. Your job is done.
 
-Present the final prompt to the user. Ask for confirmation:
-> Here's your prompt. Ready to execute, or want to adjust anything?
+> Here's your refined prompt. You can paste it into a new conversation, adjust it further, or tell me to run it.
 
-On confirmation, treat the prompt content as working instructions and execute accordingly.
+**CRITICAL: Do NOT execute the prompt.** The user decides when and where to run it. If the user explicitly says "run it" or "execute this", only then should you treat it as working instructions. Unsolicited execution defeats the entire purpose of this skill — the value is in the better prompt, not in skipping ahead to the work.
 
 ---
 

package/plugins/ima-claude/skills/wp-ddev/SKILL.md

@@ -0,0 +1,264 @@
+---
+name: "wp-ddev"
+description: "Run WordPress WP-CLI commands in DDEV environments. Database queries, plugin management, user ops, themes, cache, cron. Zero config from any DDEV project dir. Supply chain isolated package management. Triggers on: ddev wp, ddev setup, ddev import, wp plugin, wp db, wp user, wp option, wp-cli, DDEV."
+---
+
+# WordPress WP-DDEV
+
+Execute WP-CLI commands in DDEV WordPress environments. Zero configuration — just be in a DDEV project directory.
+
+## Quick Start
+
+**Prerequisites**: Docker + DDEV v1.25+ installed.
+
+```bash
+# Start your DDEV project
+ddev start
+
+# Run WP-CLI commands directly
+ddev wp plugin list
+ddev wp user list
+ddev wp db query "SELECT * FROM wp_posts LIMIT 5"
+
+# View project info (URLs, ports, credentials)
+ddev describe
+```
+
+## How It Works
+
+1. DDEV auto-detects `.ddev/config.yaml` in project directory
+2. WP-CLI runs inside the web container with correct PHP, MySQL, and WordPress paths
+3. No environment pollution — host session stays clean
+4. No UUIDs, no socket paths, no wrapper scripts
+
+## Common Commands
+
+### Database Operations
+`ddev wp db query <sql>` · `ddev wp db export [file]` · `ddev wp db import <file>` · `ddev wp search-replace <old> <new>`
+```bash
+ddev wp db query "SELECT * FROM wp_users"
+ddev wp db export dump.sql
+ddev wp db import dump.sql
+ddev wp search-replace 'old.com' 'new.com' --dry-run
+ddev wp search-replace 'old.com' 'new.com' --all-tables
+```
+
+### Plugin Management
+`ddev wp plugin list` · `ddev wp plugin activate <plugin>` · `ddev wp plugin deactivate <plugin>` · `ddev wp plugin install <plugin> [--activate]`
+```bash
+ddev wp plugin list
+ddev wp plugin list --status=active --format=json
+ddev wp plugin activate my-plugin
+ddev wp plugin deactivate my-plugin
+ddev wp plugin install contact-form-7 --activate
+ddev wp plugin is-installed woocommerce && echo "yes"
+```
+
+### User Operations
+`ddev wp user list` · `ddev wp user create <login> <email> [--role=<role>]` · `ddev wp user update <user> [--field=value]`
+```bash
+ddev wp user list
+ddev wp user list --role=administrator --format=table
+ddev wp user create testuser test@example.com --role=editor
+ddev wp user update 1 --display_name="Admin User"
+ddev wp user add-role 2 editor
+```
+
+### Theme Operations
+`ddev wp theme list` · `ddev wp theme activate <theme>` · `ddev wp theme status <theme>`
+```bash
+ddev wp theme list
+ddev wp theme activate twentytwentyfour
+ddev wp theme status flavor
+```
+
+### Cache & Transients
+`ddev wp cache flush` · `ddev wp transient delete --all` · `ddev wp transient get <key>`
+```bash
+ddev wp cache flush
+ddev wp transient delete --all
+ddev wp transient get my_transient_key
+ddev wp transient list --format=table
+```
+
+### Options
+`ddev wp option get <key>` · `ddev wp option update <key> <value>` · `ddev wp option list [--search=<pattern>]`
+```bash
+ddev wp option get siteurl
+ddev wp option update blogname "New Site Name"
+ddev wp option list --search="woocommerce_*" --format=table
+ddev wp option delete my_old_option
+```
+
+### Post & Content
+`ddev wp post list [--post_type=<type>]` · `ddev wp post create` · `ddev wp post update <id>` · `ddev wp post delete <id>`
+```bash
+ddev wp post list --post_type=page --format=table
+ddev wp post list --post_status=draft --fields=ID,post_title
+ddev wp post create --post_type=post --post_title="Test" --post_status=publish
+ddev wp post update 42 --post_title="Updated Title"
+ddev wp post delete 42 --force
+ddev wp post meta get 42 _thumbnail_id
+ddev wp post meta update 42 custom_field "new value"
+```
+
+### Taxonomy & Terms
+`ddev wp term list <taxonomy>` · `ddev wp term create <taxonomy> <term>` · `ddev wp term update <taxonomy> <term-id>`
+```bash
+ddev wp term list category --format=table
+ddev wp term create category "New Category" --slug=new-category
+ddev wp term update category 5 --name="Renamed"
+ddev wp term delete category 5
+```
+
+### Menu
+`ddev wp menu list` · `ddev wp menu item list <menu>` · `ddev wp menu item add-post <menu> <post-id>`
+```bash
+ddev wp menu list --format=table
+ddev wp menu item list primary-menu
+ddev wp menu item add-post primary-menu 42
+ddev wp menu item add-custom primary-menu "Link" https://example.com
+```
+
+### Rewrite Rules
+`ddev wp rewrite flush` · `ddev wp rewrite list` · `ddev wp rewrite structure <structure>`
+```bash
+ddev wp rewrite flush
+ddev wp rewrite list --format=csv
+ddev wp rewrite structure '/%postname%/'
+```
+
+### Scaffold
+`ddev wp scaffold plugin <slug>` · `ddev wp scaffold child-theme <slug>` · `ddev wp scaffold post-type <slug>`
+```bash
+ddev wp scaffold plugin my-plugin --plugin_name="My Plugin"
+ddev wp scaffold post-type product --plugin=my-plugin
+ddev wp scaffold taxonomy genre --post_types=product --plugin=my-plugin
+ddev wp scaffold child-theme flavor-child --parent_theme=flavor
+```
+
+### Eval & Shell
+`ddev wp eval <code>` · `ddev wp eval-file <file>`
+```bash
+ddev wp eval "echo home_url();"
+ddev wp eval "var_dump(wp_get_current_user());"
+ddev wp eval "echo get_option('active_plugins') | print_r;"
+ddev wp eval-file test-script.php
+```
+
+## DDEV Project Commands
+
+```bash
+# Lifecycle
+ddev start            # Start containers
+ddev stop             # Stop (preserves database)
+ddev restart          # Restart after config changes
+
+# Information
+ddev describe         # URLs, ports, DB credentials, PHP version
+ddev list             # All DDEV projects on this machine
+
+# Shell & Exec
+ddev ssh              # Interactive shell in web container
+ddev exec ls -la      # Run any command in web container
+
+# Logs
+ddev logs             # Web server logs
+ddev logs -s db       # Database server logs
+
+# Launch
+ddev launch           # Open site in browser
+ddev launch wp-admin/ # Open WP admin
+```
+
+## IMA Addon Commands
+
+Commands provided by the `ima-ddev-wordpress` addon:
+
+```bash
+# First-time bootstrap (idempotent — safe to re-run)
+ddev setup
+
+# Import wp-content assets from WPE site archive
+ddev import-assets ~/path/to/extracted-archive
+
+# Import database dump
+ddev import-db --file=~/path/to/dump.sql
+
+# Update the addon
+ddev add-on update ima-ddev-wordpress
+```
+
+## Supply Chain Security
+
+Always use `ddev npm`, `ddev composer` instead of bare host commands. Container isolation prevents compromised dependencies from accessing host SSH keys, env vars, and other projects.
+
+| Instead of | Use | Why |
+|---|---|---|
+| `npm install` | `ddev npm install` | Container-isolated |
+| `composer install` | `ddev composer install` | Container-isolated |
+| `npm run composer:dev` | `ddev npm run composer:dev` | Container-isolated |
+
+**Exception:** `npm run deploy` stays on host — needs SSH access for WP Engine push.
+
+## Global Flags
+
+These flags work with most WP-CLI commands:
+
+| Flag | Description |
+|---|---|
+| `--format=<format>` | Output: `table`, `csv`, `json`, `yaml`, `count`, `ids` |
+| `--fields=<fields>` | Comma-separated columns to display |
+| `--quiet` | Suppress informational messages |
+| `--skip-themes` | Skip loading themes (faster execution) |
+| `--skip-plugins` | Skip loading all plugins (debug conflicts) |
+| `--skip-plugins=<plugin>` | Skip loading specific plugin |
+| `--debug` | Show debug output |
+| `--user=<id\|login>` | Run command as specific user |
+
+## Finding More Commands
+
+The 12 categories above cover ~90% of daily dev usage. For everything else:
+
+```bash
+ddev wp help
+ddev wp help plugin
+ddev wp help post list
+```
+
+See [`references/wp-cli-reference.md`](references/wp-cli-reference.md) for a comprehensive reference and [`references/ddev-commands.md`](references/ddev-commands.md) for DDEV-specific commands.
+
+## Daily Workflow
+
+```bash
+# Start your day
+ddev start
+
+# Develop — code changes auto-reflected via bind mounts
+# Test
+ddev wp plugin activate my-plugin
+ddev wp cache flush
+ddev launch
+
+# Stop when done
+ddev stop
+```
+
+## Integration
+
+**With php-fp-wordpress**: Test plugins during development, verify security functions, check database operations.
+
+**With js-fp-wordpress**: Test script enqueuing, verify AJAX endpoints, check jQuery availability.
+
+```bash
+# Develop plugin with php-fp-wordpress patterns, test with DDEV
+ddev wp plugin activate my-new-plugin
+ddev wp eval "var_dump(current_user_can('edit_posts'));"
+```
+
+## Quality Gates
+
+Before running destructive commands:
+- ✅ Correct project: `ddev describe` to verify you're in the right DDEV project
+- ✅ Backup if needed: `ddev export-db --file=backup.sql.gz` for database modifications
+- ✅ Containers running: `ddev start` (DDEV will tell you if already running)

package/plugins/ima-claude/skills/wp-ddev/references/ddev-commands.md

@@ -0,0 +1,232 @@
+# DDEV Commands Reference
+
+DDEV-specific commands for WordPress local development. For WP-CLI commands, see [wp-cli-reference.md](wp-cli-reference.md).
+
+## Table of Contents
+
+- [Project Lifecycle](#project-lifecycle)
+- [Information](#information)
+- [Database](#database)
+- [Shell & Execution](#shell--execution)
+- [Package Managers](#package-managers)
+- [IMA Addon Commands](#ima-addon-commands)
+- [Configuration Files](#configuration-files)
+- [Logs & Debugging](#logs--debugging)
+- [URLs & Networking](#urls--networking)
+- [Snapshots](#snapshots)
+- [Add-ons](#add-ons)
+- [Troubleshooting](#troubleshooting)
+
+---
+
+## Project Lifecycle
+
+```bash
+ddev start               # Start containers (creates if first time)
+ddev stop                # Stop containers (preserves data)
+ddev restart             # Restart after config changes
+ddev delete              # Remove containers and database (destructive!)
+ddev delete --omit-snapshot  # Delete without creating snapshot first
+```
+
+**Gotcha**: `ddev stop` preserves the database. `ddev delete` destroys it. When in doubt, snapshot first.
+
+---
+
+## Information
+
+```bash
+ddev describe            # URLs, ports, DB credentials, PHP version, container status
+ddev list                # All DDEV projects on this machine
+ddev version             # DDEV version
+```
+
+`ddev describe` is your first stop — it shows everything: the HTTPS URL, database port, PHP version, and whether containers are healthy.
+
+---
+
+## Database
+
+```bash
+ddev import-db --file=dump.sql         # Import SQL dump
+ddev import-db --file=dump.sql.gz      # Import compressed dump
+ddev export-db --file=backup.sql.gz    # Export database (compressed)
+ddev export-db                         # Export to stdout
+ddev mysql                             # Interactive MySQL client (inside container)
+ddev mysql -e "SHOW TABLES"            # Run single query
+```
+
+**Credentials**: database=`db`, user=`db`, password=`db`, host=`db` (inside container) or `127.0.0.1:<port>` from host — port shown by `ddev describe`.
+
+---
+
+## Shell & Execution
+
+```bash
+ddev ssh                               # Interactive bash in web container
+ddev ssh -s db                         # Shell into database container
+ddev exec ls -la wp-content/plugins/   # Run command in web container
+ddev exec cat wp-content/debug.log     # Read a file inside the container
+```
+
+`ddev exec` runs one-off commands. `ddev ssh` for interactive sessions.
+
+---
+
+## Package Managers
+
+All package operations run inside the container:
+
+```bash
+ddev npm install                       # npm in container
+ddev npm run build                     # npm scripts in container
+ddev npm run composer:dev              # Composer via npm script
+ddev composer install                  # Composer in container
+ddev composer require vendor/package   # Add dependency
+ddev yarn install                      # Yarn alternative
+```
+
+**Why**: Running on host exposes SSH keys, env vars, and other projects to postinstall scripts. Container isolation prevents supply chain attacks.
+
+**Exception**: `npm run deploy` runs on host — it needs SSH access for WP Engine push.
+
+---
+
+## IMA Addon Commands
+
+Provided by `ima-ddev-wordpress`:
+
+```bash
+# First-time setup (idempotent — safe to re-run)
+ddev setup
+# - Downloads WordPress core
+# - Creates wp-config.php with DDEV credentials
+# - Rewrites URLs to match DDEV hostname
+# - Installs free plugins from .ddev/ima-wordpress.yaml
+# - Fixes known vendor issues (e.g., Mockery dev deps)
+
+# Import wp-content from a WPE site archive
+ddev import-assets ~/path/to/extracted-archive
+# - Copies: PRO plugins, parent theme, compiled CSS, uploads, vendor deps
+# - Never overwrites git-tracked files (rsync --ignore-existing)
+
+# Install or update the addon itself
+ddev add-on get https://gitea.theflccc.org/IMA/ima-ddev-wordpress
+ddev add-on update ima-ddev-wordpress
+```
+
+**Key flag**: `--ignore-existing` means `ddev import-assets` is safe to re-run — it won't clobber your local changes.
+
+---
+
+## Configuration Files
+
+```
+.ddev/
+├── config.yaml              # Project config (type, PHP version, DB)
+├── ima-wordpress.yaml       # Free plugin list (site-specific)
+├── php/                     # PHP overrides (upload_max_filesize, etc.)
+├── .env                     # Environment variables for containers
+├── commands/web/setup       # Custom 'ddev setup' command
+└── commands/host/import-assets  # Custom 'ddev import-assets' command
+```
+
+**Key `config.yaml` settings**: `type: wordpress`, `php_version`, `database`, `webserver_type`, `router_http_port`, `router_https_port`.
+
+After editing `config.yaml`, run `ddev restart` to apply changes.
+
+---
+
+## Logs & Debugging
+
+```bash
+ddev logs                    # Web server (nginx/Apache) logs
+ddev logs -s db              # MySQL server logs
+ddev logs -f                 # Follow logs (tail -f style)
+ddev exec cat wp-content/debug.log | tail -50   # WordPress debug log
+ddev xdebug on               # Enable Xdebug (for PHPStorm/VS Code)
+ddev xdebug off              # Disable Xdebug (faster execution)
+```
+
+**Gotcha**: Xdebug significantly slows PHP execution. Toggle it off when not actively stepping through code.
+
+---
+
+## URLs & Networking
+
+```bash
+ddev launch                  # Open site in default browser
+ddev launch wp-admin/        # Open WP admin
+ddev share                   # Create ngrok tunnel for external access
+```
+
+**Port conflicts**: If 80/443 are in use (e.g., another web server), DDEV auto-assigns alternate ports. Check with `ddev describe`. The `ddev setup` command configures WordPress URLs accordingly — no manual search-replace needed.
+
+---
+
+## Snapshots
+
+```bash
+ddev snapshot                               # Create database snapshot
+ddev snapshot --name=before-migration       # Named snapshot
+ddev snapshot restore                       # Restore latest snapshot
+ddev snapshot restore --latest              # Same as above
+ddev snapshot restore --name=before-migration  # Restore specific
+ddev snapshot list                          # List all snapshots
+```
+
+Snapshots are fast database checkpoints. Take one before any risky operation (migrations, plugin updates, data imports).
+
+---
+
+## Add-ons
+
+```bash
+ddev add-on list                            # List installed add-ons
+ddev add-on get ddev/ddev-redis             # Install from DDEV registry
+ddev add-on get https://gitea.theflccc.org/IMA/ima-ddev-wordpress  # Install from URL
+ddev add-on update ima-ddev-wordpress       # Update specific add-on
+ddev add-on remove redis                    # Remove add-on
+```
+
+---
+
+## Troubleshooting
+
+**"Critical error" on page load:**
+Missing plugin or broken dependency. Check the debug log first:
+```bash
+ddev exec cat wp-content/debug.log | tail -20
+ddev wp plugin activate --all
+```
+
+**ima-payments fatal error (Mockery not found):**
+WPE archives include dev dependencies. Re-run setup (it auto-fixes this) or fix manually:
+```bash
+ddev exec bash -c "cd wp-content/plugins/ima-payments && composer install --no-dev"
+```
+
+**No CSS / unstyled site:**
+Compiled CSS is a build artifact not tracked in git. Re-import from the WPE archive:
+```bash
+ddev import-assets ~/path/to/extracted-archive
+```
+
+**Can't connect to database:**
+```bash
+ddev describe    # Check container status
+ddev restart     # Restart containers
+```
+
+**Port conflict:**
+```bash
+ddev describe    # Shows actual assigned ports
+# DDEV auto-handles conflicts; ddev setup rewrites WordPress URLs to match
+```
+
+**Docker not running:**
+```bash
+docker info      # Check Docker daemon status
+# Start Docker Desktop, or: sudo systemctl start docker
+ddev start
+```