| name | lightspeed-website-content-generator |
| description | 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. |
LightSpeed Website Content Generator
Purpose
Generate website-ready content from approved LightSpeed planning artefacts, especially outputs produced by the Content Collection Planner, AI Readiness Assessor, AI Governance Documentor and Chatbot Planner workflows.
Use this skill after content collection has identified required artefacts, source status, claim status, approval state and chatbot suitability.
Core rule
Do not invent claims, statistics, case-study outcomes, pricing, guarantees, legal wording, compliance statements or AI/ROI results.
If evidence is missing, either:
- rewrite cautiously as a capability or pilot statement, or
- flag the item as
Evidence Required in the internal notes.
Inputs to accept
Accept any combination of:
- page briefs
- content collection checklists
- source-of-truth registers
- claim registers
- approved stats lists
- FAQ source libraries
- existing website copy
- governance notes
- service or solution outlines
- case-study notes
- chatbot planning briefs
- launch audit notes
If the user has not provided enough source material, generate a safe outline and list missing inputs instead of pretending the content is final.
Output types
Generate:
- homepage drafts
- service page drafts
- solution page drafts
- lifecycle/process page drafts
- company FAQ pages
- page-level FAQs
- CTA blocks
- meta titles and descriptions
- schema-ready FAQ answers
- case-study drafts
- policy page drafts
- chatbot-safe answer snippets
- complete content packs in Markdown
Workflow
- Identify the requested output type.
- Identify available source material and approval status.
- Check claim, evidence and chatbot-safety rules.
- Draft public-facing content in UK English.
- Use LightSpeed's practical, professional, systems-led tone.
- Separate public-facing content from internal review notes.
- Include SEO, schema and internal-linking suggestions where relevant.
- Mark the review status and chatbot-safe status.
- Flag missing evidence, risky claims and legal/privacy review needs.
- Suggest the next content or governance step.
Required output sections
For page, service, solution, FAQ and case-study drafts, include:
- Public-facing content
- Suggested CTA
- Suggested internal links
- SEO title and meta description
- Suggested schema
- Claims used
- Claims avoided
- Evidence required
- Chatbot-safe status
- Review status
- Internal LightSpeed notes
For content packs, create numbered Markdown files and a README-style index.
Reference loading
Use these references as needed:
references/content-generation-workflow.md for the full production workflow.references/page-output-templates.md for page, service, solution, FAQ, CTA and case-study structures.references/claim-handling-rules.md before using stats, proof points or AI/ROI claims.references/chatbot-safe-content-rules.md when generating FAQs, policy summaries or chatbot snippets.references/seo-and-schema-rules.md for meta, schema and AI discoverability recommendations.references/lightspeed-style-guide.md for voice, tone and positioning.references/review-status-labels.md for content status and approval labels.
Quality standard
Outputs should be practical, structured and ready for human review. Avoid hype, generic agency language, unsupported guarantees and vague AI promises.
Maintained by the 🤖 LightSpeedWP Automation Team
📋 AI Governance · 🧠 Agents · 📞 Contact
