lightspeedwp

Reliable, workflow-driven PDF processing: render → verify → operate → re-render/verify, covering reading, inspection, extraction, editing, forms, OCR, redaction, conversion, and diffing. Prefer authoring in DOCX or PPTX (then converting to PDF) for text-heavy docs or slide-like layouts; use ReportLab here for programmatic PDF generation.

Build, edit and export PowerPoint-style presentations with pptxgenjs or artifact tool library. Use when creating or modifying presentations or other visual aids like charts, posters etc.,

plan bounded website chatbots for lightspeed client projects, including chatbot purpose, audience, approved sources, exclusion lists, behaviour rules, fallback wording, escalation, privacy notes, launch gates, test scripts and first draft system prompts. use when a user asks whether a chatbot is appropriate, how to scope a chatbot, how to prepare ai engine or wordpress chatbot requirements, or how to define safe chatbot behaviour.

create ai governance discovery summaries, lightweight ai policies, operational governance guides, governance matrices, role maps and approved prompt templates for lightspeed website, content and chatbot projects. use when a user provides discovery answers, risk context, business notes or asks to document ai use cases, approval workflows, chatbot behaviour, source controls or human review rules.

assess website ai readiness for lightspeed client projects using checklist answers, website urls, audit exports, discovery notes or uploaded evidence. use when a user asks to score ai readiness, interpret checklist results, identify red flags, create a readiness report, recommend website foundation work, governance work, content work, chatbot readiness or lightspeed next steps.

create tailored content collection checklists, content gap reports, client request emails and downloadable folder structures for lightspeed website, governance and chatbot projects. use when a user needs generic website content requests, sector add-ons for ecommerce, tourism, publishing, education, memberships or subscriptions, or source-of-truth planning for ai-assisted content and chatbot grounding.

route lightspeed ai readiness client projects into the correct workflow, ask clarifying questions, enforce the sequence readiness, governance discovery, content collection and chatbot planning, and produce combined markdown project packs. use when the user is starting a new client-specific ai readiness project, wants a guided wizard, or asks which skill or document to create next.

validate proof, statistics, outcomes and marketing claims before publication for lightspeed wordpress, woocommerce, ai-readiness, publishing, tourism and professional-services website projects. use when the user asks to audit claims, classify stats, create a claim register, approve wording, reject risky wording, identify evidence needed, map claims to page locations, assign review owners, set review dates, or decide whether claims are chatbot-safe.

Extract a color palette from a Figma variables table node and replace the settings.color.palette array in a theme.json file. Use when updating or syncing a WordPress theme.json palette from Figma color variables.

Extract border radius presets from a Figma Variables documentation node and update WordPress theme.json settings.border.radiusSizes (6.9 schema). Use when syncing radius presets from Figma and preserving labels/slugs.

Extract shadow tokens from a Figma Variables documentation node and update WordPress theme.json shadow presets (6.9 schema). Use when the user provides a Figma node with shadow variables and wants theme.json presets updated.

Extract spacing tokens from a Figma variables table node and replace the settings.spacing.spacingSizes array in a theme.json file. Use when syncing WordPress theme spacing scales from Figma.

Extract multiple style variations (color palettes + typography font families) from a Figma variables table node into individual WordPress theme.json style variation files. Use when syncing styles from Figma into /styles variation JSON files, including font downloads and fontFace entries.

Extract typography tokens (font sizes, font families, line heights) from a Figma variables table node and replace settings.typography + custom line-height properties in a WordPress theme.json (6.9 schema). Use when syncing a theme’s typography presets from Figma.

Convert Figma designs into ls-theme WordPress block patterns with strict semantic token mapping, dark-token parity, reuse-or-create style workflow, Phosphor icon mapping into Icon Block markup, CSS-versus-GSAP motion routing, mandatory use of the theme-color-token-enforcer skill for created patterns or styles, and mandatory use of the wordpress-gsap skill whenever GSAP is required.

Audit or fix semantic colour token usage in a WordPress block theme. Use when checking a file, folder, or glob for raw colours, direct preset-colour references, missing settings.custom.color tokens, missing styles/dark.json token parity, or WCAG AA contrast issues. Reuse an existing semantic custom colour token where possible; otherwise create matching theme.json and styles/dark.json token paths and replace authored usage with semantic custom colour tokens, while preserving existing shared non-colour token families such as custom typography font-weight variables.

Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.

Generate technically correct, design-distinctive WordPress block patterns. Use when creating block patterns, starter page patterns, template patterns, template part patterns, or improving pattern design quality. Covers pattern registration (PHP headers, auto/manual), block markup syntax, theme.json design tokens, categories, template types, accessibility, and i18n/escaping.

Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).

Audit a WordPress block theme and fill out theme.json as completely as possible without overwriting existing config. Use when scanning a theme, theme.json, style variations, styles/presets files, templates, patterns, and block.json supports to identify missing block configuration, infer sensible additions, present an approval-first plan, and then apply additive minimal edits.

Import Figma design nodes into ma-theme as WordPress block patterns (PHP), style JSON variations, HTML template parts/templates, or a combination. Handles token mapping from Figma variables to theme.json presets, semantic WordPress block selection, pattern composition via wp:pattern references, and reuse of existing styles/patterns. Use when the user provides a Figma node URL or ID and wants to create theme artifacts from it. Supports simple components (buttons, separators) to complex layouts (cards, heroes, page templates). Approval-gated: always proposes before implementing.

Convert Figma designs into ma-theme WordPress block patterns with strict theme.json token mapping, reuse-or-create style workflow, icon discovery/staging, and an approval-first execution gate.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends the model's capabilities with specialized knowledge, workflows, or tool integrations.

Extract ATI Holidays legacy page sections into WordPress block patterns, template parts, and templates for ati-theme-2026. Use when migrating a live ATI page URL or matching source files in ati-holidays-lsx-child, especially Tour Operator templates that need correct pattern naming, section styling, and template assembly using goafrica-ollie-child and Medical Academic as references.