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/anvil-toolset 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
Quality gates for multi-reviewer code review pipelines: adversarial verification panel, completeness critic, reviewer pipeline conventions, and the context sharing pattern for parallel reviewers. TRIGGER WHEN: running /senior-review:team-review quality gates; running /senior-review:code-review Steps 4b/4c (adversarial verification and completeness check); consolidating or deduplicating findings from multiple parallel reviewers. DO NOT TRIGGER WHEN: single-reviewer style review without a consolidation phase, or generic team coordination (the upstream agent-teams skills cover that).
development
Knowledge base for pure-architecture decisions on when to unify duplicated logic into a shared abstraction versus leave it duplicated. Covers the canonical theory (Rule of Three, DRY/WET/AHA, Wrong Abstraction, Locality of Behaviour, Bounded Contexts, Tidy First options framing, CUPID vs SOLID), 12 essential-duplication patterns that justify unification, 12 wrong-abstraction patterns that justify inlining or decomposition, an operational decision frame, and a verified reading list. TRIGGER WHEN: the user is making an architectural decision about whether to centralize, extract, or remove a layer; reviewing an abstraction for premature generality; auditing scattered cross-cutting concerns; spawned by the abstraction-architect agent during /abstraction-architect:audit or as the Abstraction dimension of /senior-review:team-review or /senior-review:code-review; the user asks "should I extract this into a service" / "is this DRY enough" / "is this wrong abstraction". DO NOT TRIGGER WHEN: the task is code formatting and readability cleanup (use clean-code:clean-code), Python-specific refactoring with metrics (use python-development:python-refactor), generic dead-code removal (use senior-review:cleanup-dead-code), security review (use senior-review:security-auditor), or pure pattern-consistency review without an architecture lens (use senior-review:code-auditor).
development
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
Stripe payments knowledge base - API patterns, checkout optimization, subscription lifecycle, pricing strategies, webhook reliability, Firebase integration, cost analysis, and revenue modeling. Loaded by stripe-integrator and revenue-optimizer agents; also consumable directly when the user asks for Stripe-specific patterns without needing an agent. TRIGGER WHEN: working with Stripe API (Payment Intents, Customers, Subscriptions, Checkout Sessions, Connect, webhooks, tax, usage-based billing), pricing strategy, or revenue modeling. DO NOT TRIGGER WHEN: payment work is non-Stripe (PayPal, Square, crypto) or the task is generic e-commerce unrelated to payments.