Menu
SkillsMP has collected 61 skills from peterbamuhigire/website-skills. Open a skill to review its source and details.
Showing 40 of 61 collected skills.
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.
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.
Use when auditing or improving the website engine or any website, landing page, ecommerce experience, dashboard, portal, or visual web product it produces.
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.
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.
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.
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.
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.
Use when converting an approved brand and style brief into website tokens, component rules, responsive behaviour, states, and motion; do not use to analyse reference sites or assemble production pages.
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.
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.
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.
Use when a completed website must be built, release-gated, deployed, verified, communicated, and made rollback-ready; use `observability` for telemetry design and quality-gate skills for specialist audits.
Use when creating or upgrading portable website-engine skills, triggers, contracts, references, validators, or routing fixtures; use skill-safety-audit for independent safety review and update-claude-documentation for router-only changes.
Use when a premium website build needs build-coupled UX and visual-quality orchestration before design-system and page-builder; use the external design-system-skills engine for general visual doctrine.
Use when implementing website metadata, structured data, sitemaps, robots directives, canonical and hreflang signals, internal links, and search-facing content structure; use seo-audit for read-only diagnosis.
Use when a concrete website-delivery task needs this procedure; use the named neighbouring skill for its distinct trigger.
Use when analysing client-supplied reference or competitor websites into an implementation-facing design direction; do not use for defining tokens or building pages, which belong to design-system and page-builder.
Use when implementing approved website content, design rules, assets, routes, conversion goals, schema, and analytics as reusable production pages; do not use to invent the design system or write missing native-language copy.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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…
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.
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.
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.
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.
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…
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.
Use when designing or implementing multilingual website routes, locale content, hreflang, canonical URLs, switching, and sitemaps; do not use for writing native French or Kiswahili copy or for general SEO alone.
Use when generating measured web-image derivatives from approved source assets; do not use for cataloguing, selecting, or licensing photographs, which belongs to photo-manager.
Use when cataloguing, renaming, dimensioning, selecting, approving, and placing the correct logo and website photographs; do not use for derivative encoding alone, which belongs to image-compression.
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.