website

Plugin website from marketplace chwezi in peterbamuhigire/chwezi-engine-agents. Commands read from the repo's manifest — yesterday.

Skills (56)

• agency-client-retention

  Use when designing post-launch retainers, review cadence, expansion offers, churn controls, recurring-revenue capacity, or client reporting. Use `monthly-report` for one evidence-backed report and `customer-service-website-ops` for incident handling.

• agency-positioning

  Use when defining a premium website agency's niche, offer ladder, qualification, fee posture, scope boundaries, proof, and proposal positioning. Use `premium-sales-conversation` for a live opportunity and `brand-strategy` for a client's market identity.

• authority-offers

  Use when packaging expertise into lead magnets, paid audits, workshops, webinars, or mini-products with a measurable conversion path. Use `launch-campaigns` for timing an established offer and `sales-copywriting` for its page copy.

• customer-service-website-ops

  Use when designing post-launch website support triage, escalation, recovery language, and retention operations. Use `service-blueprint-website-delivery` for end-to-end delivery design and `agency-client-retention` for commercial renewal strategy.

• delivery-automation

  Use when auditing and automating repeatable agency delivery work, choosing build versus buy, or creating internal starter kits and SOPs. Use `service-blueprint-website-delivery` for one engagement's operating model and `deploy` for project CI.

• email-sender

  Use when implementing a self-hosted PHP and PHPMailer form-mail flow with spam, CSRF, validation, delivery, and confirmation controls. Use `email-sender` for transactional form delivery, not campaign broadcasts or general form UX.

• launch-campaigns

  Use when sequencing an established offer through prelaunch, launch, close, and follow-up across a website, email, WhatsApp, or blog. Use `authority-offers` when the offer itself is undefined and `sales-copywriting` for deep page persuasion.

• local-in-person-acquisition

  Use when planning ethical face-to-face acquisition for a niche local web studio through territories, short audits, walk-in conversations, follow-up, and pipeline tracking. Use `agency-positioning` to choose the niche and `premium-sales-conversation` after qualification.

• monthly-report

  Use when producing an evidence-backed monthly website or SEO client report from live telemetry and project logs. Use `agency-client-retention` for account strategy, `ecommerce-analytics` for commerce diagnosis, and `seo-audit` for technical SEO review.

• policy-pages

  Use when drafting or implementing website privacy and terms pages from verified processing, ownership, audience, and jurisdiction facts. Use legal counsel for legal conclusions and `form-ux-design` for consent-control interaction design.

• premium-sales-conversation

  Use when qualifying and diagnosing a premium website opportunity before any quote, proposal, or scope is written. Use `agency-positioning` to define the offer and fee posture, and the proposal engine for regulated bids or formal responses.

• referral-program

  Use when designing a consent-based client referral programme with reward, timing, attribution, partner routing, and disclosure rules. Use `agency-client-retention` to earn advocacy and `local-in-person-acquisition` for cold local outreach.

• service-blueprint-website-delivery

  Use when mapping frontstage and backstage website-delivery operations, owners, promises, fail points, SLAs, and recovery across discovery through retainer. Use `website-experience-mapping` for the customer journey and `customer-service-website-ops` for live support.

• social-media

  Use when planning measurable social-media channels, content, offer-led campaigns, list capture, or retainers tied to a website. Use `launch-campaigns` for a timed multi-channel launch and the social-media engine for platform-specialist execution.

• brand-storytelling

  Use when an approved brand strategy must become an evidence-based narrative for About pages, case studies, heroes, or campaigns. Use `brand-strategy` to decide positioning and `premium-commercial-writing` when persuasion, SEO, and offer conversion dominate.

• brand-strategy

  Use when discovery must establish audience, positioning, differentiation, architecture, and a decision-ready brand brief before design or copy. Use `brand-storytelling` after the strategy exists and `agency-positioning` for the agency's own commercial offer.

• ecommerce-analytics

  Use when defining or auditing ecommerce events, KPIs, funnels, cohorts, RFM, attribution, CLV, and dashboards; do not use for general store strategy or checkout-interface design.

• ecommerce-checkout

  Use when specifying or auditing cart, checkout, payment recovery, order confirmation, and post-purchase experience; do not use for overall ecommerce strategy, acquisition lifecycle, or KPI architecture.

• ecommerce-funnel

  Use when designing ecommerce acquisition, retargeting, lifecycle messaging, offers, upsells, retention, and repeat-purchase journeys; do not use for checkout mechanics or measurement architecture alone.

• ecommerce

  Use when defining the overall model, experience, trust, product-decision, and growth strategy for an online store; do not use for deep checkout, lifecycle, analytics, or omnichannel operating-system work.

• retail-commerce-operating-system

  Use when building or specifying a retail website, e-commerce site, omnichannel storefront, product catalogue, customer portal, or commerce frontend that must integrate product data, search/navigation, PDP content, cart/checkout, fulfilment, returns, loyalty/CRM, analytics, POS/inventory, and finance

• blog-idea-generator

  Use when a website needs evidence-grounded blog topic ideas, editorial series, an editorial calendar, or a topic backlog; use `blog-writer` for drafting articles and `content-writing` for page-copy standards.

• blog-writer

  Use when an approved topic must become a researched, source-disciplined article or publishable blog file; use `blog-idea-generator` for topic discovery and `content-writing` for general page copy.

• brand-voice

  Use when copy needs a client's actual voice reproduced consistently across pages, blog posts, and campaigns; use content-writing for page-strategy drafting and premium-commercial-writing's slop gate for the release-time quality floor.

• content-writing

  Use when website pages or interface copy need clear message hierarchy, genuine voice, scannable structure, and evidence-aware editing; use `blog-writer` for articles and `sales-copywriting` for persuasion frameworks.

• east-african-english

  Use when English website copy must sound natural, clear, respectful, and professionally East African; use `language-standards` for multilingual policy and `content-writing` for message structure.

• french-native-copy

  Use when French web, marketing, product, email, or metadata copy must read as native for a named francophone market; use `language-standards` for cross-language policy and `i18n` for routing.

• language-standards

  Use when a multilingual website needs cross-language tone, terminology, locale ownership, and consistency rules; use `french-native-copy`, `swahili-native-copy`, or `east-african-english` for language-specific execution.

• long-form-sales-copy

  Use when a defined offer needs a long-form sales page, VSL, webinar pitch, order-page sequence, or funnel copy; use `sales-copywriting` for shorter conversion elements and `content-writing` for non-sales pages.

• premium-commercial-writing

  Use when website, authority, offer, SEO, or sales-enablement writing must justify premium fees through buyer insight, proof, clear claims, and editorial restraint; use the owning execution skill for publishing or page implementation.

• sales-copywriting

  Use when a website page needs a conversion argument, value proposition, proof sequence, objection handling, risk reduction, or CTA ladder; use `content-writing` for general page clarity and `long-form-sales-copy` for full direct-response assets.

• swahili-native-copy

  Use when Kiswahili web, marketing, product, email, or metadata copy must read naturally for a named East African market; use `language-standards` for cross-language policy and `i18n` for routing.

• deploy

  Use when a completed website must be built, release-gated, deployed, verified and made rollback-ready, or when a Lighthouse or Core Web Vitals audit of a built site must find and fix failures before launch; use `observability` for telemetry design and quality-gate skills for specialist audits.

• experimentation

  Use when a measured website question needs a pre-registered controlled test, power check, guardrails, analysis, and decision; use `cro-audit` to diagnose opportunities and `marketing-measurement-system` to define KPIs.

• marketing-measurement-system

  Use when a premium website needs a KPI tree, event plan, customer-insight loop, loyalty measures, and decision-ready reporting; use `observability` for telemetry implementation and `experimentation` for causal tests.

• observability

  Use when a live website needs real-user performance, error tracking, analytics, source health, alerts, and an operator runbook; use `marketing-measurement-system` for KPI design and `deploy` for release promotion.

• skill-safety-audit

  Use when reviewing a new or changed skill for unsafe instructions, hidden side effects, credential access, installers, or permission inflation; use skill-writing for authoring and update-claude-documentation for router maintenance.

• skill-writing

  Use when creating or upgrading portable website-engine skills, triggers, contracts, references, validators, or routing fixtures under the canonical chwezi-dev-engine skill-writing standard; use skill-safety-audit for independent safety review and update-claude-documentation for router-only changes.

• update-claude-documentation

  Use when repository skill paths, catalogue counts, routing rules, or operating gates change and AGENTS.md, CLAUDE.md, README, or maintainer documentation must be reconciled; use skill-writing for skill bodies.

• africa-excellence

  Use when a website must work credibly in African markets across constrained bandwidth, mobile-first use, mobile money, USSD-aware journeys, local languages, trust, and cultural context; use deploy for release execution.

• hospitality-website-product

  Use when designing or building a world-class website for a hotel, resort, lodge, inn, guest house, restaurant, bar, venue, catering, or food-service brand.

• premium-ui-ux-design

  Use when a premium website build needs build-coupled UX and visual-quality orchestration before design-system and page-builder; use the external chwezi-design-engine engine for general visual doctrine.

• premium-website-product

  Use when defining or qualifying a revenue-critical website as a premium commercial product, including proof, scope, investment logic, no-bid thresholds, and delivery promises; use website-builder after approval.

• website-builder

  Use when orchestrating a complete website from approved documents and assets through strategy, content, design, build, SEO, quality gates, deploy readiness, and handover; use page-builder for implementation-only work.

• website-experience-mapping

  Use when mapping journeys, moments of truth, mental models, service interactions, or ecosystem dependencies before premium page architecture; use page-builder after the behaviour and evidence map is approved.

• accessibility-audit

  Use when auditing rendered website conformance to WCAG 2.2 AA with automated, keyboard, screen-reader, zoom, contrast, and content checks; use visual-qa for screenshot and hierarchy defects.

• cross-page-design-consistency-audit

  Use when auditing a multi-page or multilingual site for competing design systems, ad-hoc interior templates, translation drift, and cross-route content artefacts; use visual-qa for baseline screenshot regression.

• design-quality-score

  Use when scoring a rendered website against the engine's seven-category design-quality and anti-slop rubric; use visual-qa for screenshot regression and cross-page-design-consistency-audit for system drift.

• kaizen-engine-and-product-improvement

  Use when auditing or improving the website engine or any website, landing page, ecommerce experience, dashboard, portal, or visual web product it produces.

• security-gate

  Use when auditing a website release for dependency, secret, header, SRI, security.txt, supply-chain, privacy, and deployment security evidence; use deploy to perform the authorised release.

• visual-qa

  Use when reviewing rendered routes for screenshot drift, hierarchy, overflow, empty sections, responsive states, content artefacts, and visual regressions; use design-quality-score for the broader design rubric.

• google-ai-search

  Use when a website brief promises Google AI Overviews, AI Mode, AEO/GEO, Search Console AI measurement, local or ecommerce AI readiness, or agentic experience preparation; use seo for implementation after guidance.

• seo-audit

  Use when performing a read-only audit of an existing website's crawl, indexation, metadata, content, schema, AI citations, answer fidelity, crawler access, referrals, local search, or measurement defects; use seo for implementation.

• seo

  Use when implementing cross-platform search and AI-answer discoverability, including metadata, entity presence, structured data, sitemaps, crawler controls, canonicals, hreflang, internal links, answer clarity, and referral measurement; use seo-audit for read-only diagnosis.

• cro-audit

  Use when auditing an existing website or completed build for evidence-backed conversion barriers and test priorities; do not use to implement fixes or invent a growth strategy without an inspectable artefact.

• they-ask-you-answer

  Use when building an evidence-led buyer-question content and assignment-selling system for a premium agency; do not use for writing a single article without the broader research, sales-use, and publishing context.

Hooks (3)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/destructive-bash-gate.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/quality-gate.js"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/drift-check-hook.js"

Similar plugins