plugins/frontend/skills/premium-web-consultant/SKILL.md
Premium web design consultant that conducts structured client discovery, produces professional deliverables (website brief, sitemap, design direction, content strategy), and orchestrates web-designer, ui-layout-designer, seo-specialist, and content-marketer agents automatically. TRIGGER WHEN: planning a new website or redesign before any code is written. DO NOT TRIGGER WHEN: the task is outside the specific scope of this component.
npx skillsauth add acaprino/alfio-claude-plugins premium-web-consultantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Strategic website planning skill. Bridges the gap between "I need a website" and writing code. Produces professional strategy documents through structured discovery, then orchestrates specialist agents at defined handoff points.
Positioning: This skill handles the discovery and strategy phase. Hand off to the frontend-engineer agent when ready to build. Use /frontend:review-design instead if improving an existing frontend codebase.
Four principles woven into every phase and deliverable. Every recommendation must tie back to at least one.
Users form an opinion about a website in ~50 milliseconds. That first impression colors judgment of everything that follows - products, services, company quality. A professional, clean hero section creates a positive halo; clutter or low-quality imagery creates a negative halo that no amount of good content below the fold can overcome.
Application:
Brains conserve energy. High cognitive load feels stressful and unprofessional. Cognitive fluency - things that are easy to process - gets interpreted as better, more trustworthy, higher quality. Premium websites are masterclasses in clarity: generous white space, clear visual hierarchy, simple predictable navigation.
Application:
Premium means flawless execution for everyone. Accessible design is not an afterthought - it reduces cognitive load for all users, not just those with disabilities. High contrast, semantic HTML, keyboard navigability, and screen-reader support signal a mature, top-tier brand.
Application:
People remember experiences by their most intense points (peaks) and how they ended, not as an average of every moment. Micro-interactions create small peaks of positive emotion - a satisfying hover state, a smooth scroll transition, a gentle form confirmation. Premium websites feel alive because of these thoughtful details. They signal that the creator cared.
Application:
Structured interview. Do not proceed until all questions are answered and confirmed.
CLIENT DISCOVERY
-------------------------------------------
Business: [company name, industry, what they sell/do]
Objective: [primary goal - leads, sales, awareness, portfolio, SaaS signups]
Audience: [who, demographics, tech comfort, device preference]
Competitors: [3-5 competitor URLs]
Tone: [3 adjectives describing desired brand feeling]
Brand assets: [existing brand guidelines, logo, specific colors/fonts, or "none - start fresh"]
UVP: [unique value proposition - biggest competitive advantage]
Existing site: [URL if redesign, "none" if new]
Budget range: [ballpark for scope calibration]
Timeline: [launch target]
Success metrics:[how they'll measure if the site worked]
-------------------------------------------
Hard gate: Do not proceed to Phase 1 until the user confirms all discovery answers. If answers are vague, push for specifics - especially Audience, Objective, and Success metrics. These drive every decision downstream.
Compile discovery into a professional brief document. Use the references/website-brief-template.md template.
Sections:
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [competitor URLs, industry, target audience]
Ask: Analyze the SEO landscape for these competitors.
Report: domain authority estimates, top-ranking keywords,
content gaps, backlink strategies, and opportunities
for the client to differentiate in search.
-------------------------------
Invoke seo-specialist agent. Incorporate findings into the competitor analysis section of the brief.
Information architecture phase. Use the references/sitemap-template.md template.
Sections:
Cognitive Load rules:
Step 1: web-designer
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [sitemap, page hierarchy, proposed user flows, conversion funnels]
Ask: Validate this information architecture against the target
audience's mental model. Review user flows for friction
points. Optimize conversion funnels - identify drop-off
risks and suggest improvements. Flag any IA decisions
that increase cognitive load unnecessarily.
Apply the LIFT Model: flag elements that increase user
ANXIETY or DISTRACTION. Enhance CLARITY and RELEVANCE
for the primary CTA on each page.
-------------------------------
Step 2: ui-layout-designer (receives optimized IA from Step 1)
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [sitemap with page purposes, navigation structure, audience device preference]
Ask: Define page layout composition for each major page type.
Propose grid systems, responsive breakpoint strategy,
and above-the-fold content priorities. Ensure layouts
support the primary CTA per page and respect the
cognitive load constraints (clear hierarchy, generous
white space, one primary goal per section).
-------------------------------
Run these agents sequentially - UX validates and optimizes flows first, then layout designs page structure using the optimized IA. Incorporate both outputs before proceeding.
Visual identity phase. Use the references/design-direction-template.md template.
Sections:
Halo Effect + Cognitive Fluency + Accessibility rules:
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [color palette, typography choices, spacing system,
component style direction, responsive breakpoint
strategy from Phase 2]
Ask: Define the CSS architecture to implement this design
direction. Specify: custom property naming convention,
spacing scale (CSS custom properties), typography scale,
container query strategy, responsive approach
(mobile-first vs desktop-first with rationale),
and any modern CSS features (scroll-driven animations,
View Transitions) that would enhance the premium feel.
-------------------------------
Invoke web-designer agent. Record CSS architecture decisions in the design direction document.
Messaging and copy strategy phase. Use the references/content-strategy-template.md template.
Sections:
Peak-End Rule:
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [messaging hierarchy, per-page copy strategy,
audience profile, tone of voice, conversion funnels
from Phase 2]
Ask: Refine the per-page messaging strategy. For each page:
validate headline/body/CTA alignment with the target
audience. Suggest specific CTA copy variations for
A/B testing. Ensure messaging hierarchy builds
persuasion through the conversion funnel. Apply
Peak-End Rule - every page ends strong.
-------------------------------
Invoke content-marketer agent.
HANDOFF
-------------------------------
Brief: [paste the full client discovery, unchanged]
Context: [complete sitemap from Phase 2, per-page copy strategy,
competitor SEO analysis from Phase 1, target audience]
Ask: Create a detailed SEO keyword map for every page in
the sitemap. For each page: primary keyword, secondary
keywords (2-3), search intent, suggested meta title
(under 60 chars), suggested meta description (under
160 chars). Prioritize keywords by search volume and
competition feasibility for this business.
-------------------------------
Invoke seo-specialist agent (second invocation - now has sitemap context from Phase 2).
Merge both outputs into the content strategy document.
Compile all phase outputs into a single umbrella document. Use the references/final-package-template.md template.
Structure:
Write the final package to a file (e.g., website-strategy.md or a directory structure if large).
When moving between phases and invoking specialist agents, always use:
HANDOFF
-------------------------------
Brief: [paste the original client discovery, unchanged]
Context: [summary of the previous phase's key decisions]
Ask: [the specific question or task for the next agent]
-------------------------------
This prevents each specialist from solving the wrong problem.
| Phase | Agent | Plugin | Purpose | |-------|-------|--------|---------| | 1 | seo-specialist | digital-marketing | Competitor SEO analysis | | 2 | web-designer | frontend | IA validation, user flows, conversion funnels | | 2 | ui-layout-designer | frontend | Page layout, grid systems, responsive breakpoints | | 3 | web-designer | frontend | CSS architecture, spacing, typography, responsive | | 4 | content-marketer | digital-marketing | Per-page messaging, CTA strategy | | 4 | seo-specialist | digital-marketing | Keyword mapping, meta suggestions |
Notes:
frontend-engineer agent for implementationdevelopment
Unified web frontend knowledge base covering CSS architecture, UX psychology, UI components, distinctive aesthetics, and interface design generation. TRIGGER WHEN: working on web styling, design systems, component decisions, responsive strategy, distinctive frontend aesthetics, or exploring multiple interface designs. DO NOT TRIGGER WHEN: the task is purely backend or unrelated to web frontend.
development
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
tools
Knowledge base for the codebase-mapper plugin. Provides writing guidelines, tone rules, and diagram conventions for generating human-readable project guides. Referenced by all codebase-mapper agents during document generation. TRIGGER WHEN: referenced by codebase-mapper pipeline agents (codebase-explorer, overview-writer, tech-writer, flow-writer, onboarding-writer, ops-writer, config-writer, guide-reviewer) during document generation. DO NOT TRIGGER WHEN: outside the /map-codebase pipeline (general documentation work should use docs:readme-craft or codebase-mapper:docs-create).
tools
Progressive Web App knowledge base for 2025-2026: Web App Manifest, Service Workers (Workbox 7, Serwist), Web Push (VAPID, RFC 8030/8291/8292, Declarative Push for Safari 18.4+), install flows (beforeinstallprompt, Window Controls Overlay), OPFS storage, Project Fugu, Core Web Vitals (INP < 200ms), security (HTTPS, CSP, COOP/COEP), and distribution (Bubblewrap, PWA Builder MSIX, Capacitor). TRIGGER WHEN: building, auditing, or debugging PWAs, including manifest, service worker, Web Push, install flow, OPFS, Background Sync, Wake Lock, vite-plugin-pwa, Next.js Serwist, @angular/pwa, @vite-pwa/nuxt, Bubblewrap, TWA, PWA Builder, or Capacitor wrapping. DO NOT TRIGGER WHEN: the task is generic frontend styling (use frontend), React performance (use react-development:review-react), cross-platform security unrelated to PWA (use platform-engineering), Tauri or Electron wrappers (use tauri-development), or GA4 / analytics (use digital-marketing).