.github

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.

curate page-level faqs into a company faq page, schema-ready faq sets and chatbot-safe source registers for lightspeed wordpress website projects. use when the user asks to consolidate faqs, deduplicate faq content, map faqs to pages, create chatbot-safe faq registers, identify unsupported questions, define escalation questions, prepare faqpage schema notes or turn approved website content into safe chatbot grounding material.

audit parity between figma design-system intent and wordpress block-theme implementation for lightspeed projects. use when the user asks to compare figma variables with theme.json, review colour, typography or spacing tokens, map figma components to wordpress blocks, map patterns to figma sections, check light and dark mode parity, mobile states, focus states, accessibility states, or produce a figma-to-wordpress launch qa report.

define measurement before launch for lightspeed wordpress, woocommerce, publishing, tourism, ai-readiness and lead-generation websites. use when the user asks for ga4 event plans, gtm trigger notes, form submission tracking, lead magnet download tracking, consultation cta tracking, chatbot handoff events, looker studio dashboard briefs, launch baseline reports or conversion measurement governance.

plan final launch qa for lightspeed wordpress projects where a figma design system is implemented as a wordpress block theme, block plugin or pattern library. use when the user needs a launch qa plan, figma-to-wordpress qa scope, block theme checklist, block plugin checklist, page/template qa matrix, accessibility and responsive qa plan, conversion tracking qa, launch gates, specialist skill routing or a go/no-go planning framework before running final audits.

final pre-launch qa for lightspeed wordpress, woocommerce, publishing, tourism, ai-readiness and lead-generation websites. use when the user asks for a launch checklist, page-by-page qa table, broken link checklist, form testing checklist, accessibility testing checklist, lighthouse or pagespeed notes, mobile or responsive qa, analytics or tagging checks, redirect verification, seo launch checks or go/no-go launch summary.

draft practical policy and trust-page content for lightspeed wordpress, woocommerce, publishing, tourism, ai-readiness and chatbot projects from governance inputs. use when the user asks for a privacy policy brief, cookie policy brief, accessibility statement, ai governance page, chatbot disclosure wording, data or log retention decision notes, trust page drafts, policy review notes, or public/internal policy wording that must be separated from legal/privacy review.

collect only blocking missing project defaults and route messy lightspeed project requests to the right specialist skill. use when a lightspeed teammate starts or resumes website, figma-to-wordpress, ai-readiness, chatbot, content, seo, analytics, qa, launch, support, linear, github, asana, or delivery work with incomplete context, scattered sources, unclear next steps, or missing reusable defaults. skip when the current message, memory, or connected sources already provide enough context to proceed.

plan redirects and seo migration controls when a wordpress website structure changes. use when the user needs a current url inventory, new url map, redirect status table, priority page list, 404 risk list, seo migration notes, launch-day redirect checklist, redirect qa plan, or go/no-go notes for a redesign, rebuild, migration, domain change, content consolidation or information architecture change.

plan schema markup, faq schema, internal linking, ai-search discoverability and answer-engine optimisation for lightspeed wordpress website launches using approved website content, page briefs, claim registers, faq maps and source-of-truth notes. use when the user asks for page-level schema recommendations, organization/service/faqpage/article/breadcrumblist notes, ai visibility baseline checklists, answer-engine optimisation checklists, internal linking plans or claim-safe ai/search wording.

generate website-ready content drafts for lightspeed wordpress, woocommerce, publishing, tourism, ai-readiness and governance projects using approved page briefs, content collection outputs, claim registers, source-of-truth registers and chatbot-safe content rules. use when the user asks to create page copy, service pages, solution pages, faqs, ctas, meta descriptions, case-study drafts, policy drafts, launch-ready content packs or chatbot-safe answer snippets from planning artefacts.

The Markdown Content Validator helps ensure your markdown files and their YAML frontmatter meet necessary standards before publication or handoff, providing a detailed report on any issues found. Use this skill when you need to validate documentation, templates, or prompts for errors, missing fields, and adherence to versioning rules without altering the original content.

review post-launch website performance and optimisation opportunities for lightspeed projects using analytics summaries, ga4 notes, search console observations, seo findings, chatbot transcripts or summaries, content performance notes, conversion observations, heatmap findings, backlog items, and stakeholder priorities. use when the user asks for post-launch optimisation, ongoing improvement planning, CRO observations, content iteration priorities, chatbot tuning recommendations, retention or conversion improvements, analytics-led backlog creation, or a prioritised optimisation roadmap after launch.

audit technical SEO readiness for lightspeed website projects using website urls, crawl exports, sitemap lists, redirect maps, metadata samples, launch checklists, staging or live observations, and developer notes. use when the user asks for a technical SEO audit, crawlability or indexation review, canonicals review, metadata QA, migration SEO risk review, internal linking risk review, sitemap and robots checks, structured-data validation notes, or a prioritised technical SEO fix list before or after launch.

Create, edit, redline, and comment on `.docx`, Word, and Google Docs-targeted document artifacts inside the container, with a strict render-and-verify workflow. Use `render_docx.py` to generate page PNGs (and optional PDF) for visual QA, then iterate until layout is flawless before delivering the final document.

Read, create, inspect, render, and verify PDF files where visual layout matters. Use Poppler rendering plus Python tools such as reportlab, pdfplumber, and pypdf for generation and extraction.

Create or edit PowerPoint or Google Slides decks

Use this skill when a user requests to create, modify, analyze, visualize, or work with spreadsheet files (`.xlsx`, `.xls`, `.csv`, `.tsv`) or Google Sheets-targeted spreadsheet artifacts with formulas, formatting, charts, tables, and recalculation.

Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.

Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.

Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.

**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

Run website accessibility discovery assessments for LightSpeed website projects. Use when the user wants to assess accessibility findings, likely compliance or usability risks, evidence gaps, recurring accessibility problem patterns, or what should be validated before remediation planning.

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.

Run website content audits, content inventories, content gap reviews, and content strategy discovery for LightSpeed website projects. Use when the user wants to assess existing website content quality, identify duplication or decay, map content gaps, organize findings into a structured audit, or connect current-state content evidence to recommended content strategy directions.

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.

The Design MD Generator creates and updates `DESIGN.md` files for LightSpeed projects, transforming design evidence from Figma and GitHub into a portable design contract for WordPress themes. Use this skill when starting a new project or auditing an existing one, ensuring that your design files are validated and aligned with implementation realities.

collect and persist reusable lightspeed website discovery defaults in memory before discovery workflows. use when a lightspeed teammate starts a client website discovery task, asks to create a discovery pack or summary, or a related discovery skill is blocked by missing client, website, goal, output, approval, or standing project defaults. route away from this skill for run-specific source gathering, draft review, specialist audits, launch planning, or one-off rewrites when enough context already exists.

Review a website discovery pack, section draft, or client-ready summary for missing template sections, classification mistakes, internal-versus-client boundary issues, and unresolved template-field coverage before finalizing or sharing it.