wordpress-agent-kit

Bootstrap a new or existing WordPress project with the full wp-agent-kit system: monorepo detection, Composer/WPackagist/SatisPress setup, Playground local dev, WP Engine dev/staging/production, CI gate, git hooks, and plugin packaging. Use when setting up a new WordPress project from scratch, onboarding an existing codebase, or wiring up a monorepo with multiple plugins/themes.

Use when integrating Gravity Forms with OpenAI via Gravity Connect: configuring OpenAI Fields (real-time pre-submission AI) or OpenAI Feeds (async post-submission processing), setting token ceilings, routing through OpenRouter, using GPT Image generation, voice-to-text transcription, or building AI-powered form workflows.

Use when working with Gravity Forms: installing or updating core and add-ons via wp gf CLI, managing forms and entries programmatically, exporting/importing form JSON for version control, testing notifications, configuring Cloudflare Turnstile anti-spam, or turning forms into MCP-compatible schemas for AI consumption. Also use for the GFAPI PHP class and hook/filter development.

Use when working with Gravity SMTP: installing, configuring, or troubleshooting WordPress transactional email delivery via SendGrid, Mailgun, Postmark, Brevo, SES, or custom SMTP. Critical: always verify version ≥ 2.1.5 to protect against CVE-2026-4020 which leaks API keys via unauthenticated REST endpoint.

Use for Gravity stack setup and orchestration: SatisPress/Composer configuration for the full plugin suite (Gravity Forms, SMTP, Connect, GravityView, Spellbook, Pods), reading the .cursorrules and llms.txt templates, or understanding how all products fit together. For product-specific work, load the individual skill instead.

Use when working with Gravity Wiz products: installing or managing Spellbook (the Gravity Wiz platform), Gravity Perks (48+ form enhancement plugins like GP Populate Anything, Nested Forms, Limit Submissions), or any individual perk. Also use for Gravity Shop (WooCommerce integration).

Use when working with GravityView or GravityKit products: creating Views to display Gravity Forms entries on the front-end, configuring search/sort/filter, entry approval workflows, edit-entry forms, role-based access, merge tags, shortcodes, or the GravityActions/GravityBoard extensions.

Use when working with the Pods Framework: creating or managing custom post types (CPTs), custom taxonomies, custom database tables (ACTs — Advanced Content Types), or custom fields via Pods. Critical for AI agents: always declare whether a Pod uses wp_postmeta or ACT storage before writing any DB queries, WP_Query, or pods_field() calls.

Optional: Use for WP Engine hosting workflows — SSH-based git push, remote WP-CLI via SSH gateway, GitHub Actions CI/CD with safety-gated deploys to dev/staging/production, managing installs/domains/cache/backups via the wpe-labs Claude Code skills, and WP Engine API access. Requires SSH key setup and WPE_USERNAME/WPE_PASSWORD env vars for API operations.