Menu
Skills in this repository
SkillsMP has collected 61 skills from peterbamuhigire/website-skills. Open a skill to review its source and details.
peterbamuhigire/website-skillsShowing 21 of 61 collected skills.
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.
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.
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.
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,…
Use when a website needs evidence-grounded blog topics, editorial series, or a topic backlog; use `blog-writer` for drafting articles and `content-writing` for page-copy standards.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Use when performing a read-only audit of an existing website's crawl, indexation, metadata, content, internal links, schema, local search, or measurement defects; use seo for authorised implementation.
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.
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.