- Home
- Skills
- Frontend & Web Apps
- Premium Web
Works with the AI Agents you already use
Premium Web
Implement an approved visual direction with intentional mobile composition, keyboard and focus checks, reduced-motion behavior, and explicit UNVERIFIED reporting when browser evidence is absent.
$19
Premium Web
Example session with this skill installed
Using the approved visual direction for a pricing page and its existing tokens and components, refine the plan-card layout for mobile and desktop. Keep changes within the approved surface and existing dependencies. Return the complete Premium Web report. Do not infer browser, accessibility, or performance results; mark them UNVERIFIED unless observed.
- Read your context and instructions
- Compiled the premium web
Illustrative output adapted from the package's synthetic worked example. No project files were inspected or changed for this listing. Names and details below are sample content, not measured results or evidence of execution.
SURFACE: /pricing, a sample page with three plan cards and a toggle.
VISUAL DIRECTION PRESERVED: the sample assumes an approved type scale and spacing unit. These are hypothetical inputs, not detected project tokens.
CHANGED COMPONENTS: PricingCard, BillingToggle, PricingGrid (sample names only).
RESPONSIVE STATES: The sample would inspect a 320px mobile view and wider layouts. Actual overflow and layout-shift results are UNVERIFIED.
A11Y / MOTION / PERFORMANCE CHECKS: Check contrast, keyboard and focus, target size, reduced motion, media sizing, and layout shifts. No checks were run for this listing; findings are UNVERIFIED.
RENDERED EVIDENCE: None for this listing.
UNVERIFIED: Actual implementation, browser rendering, console/network behavior, accessibility outcomes, and performance measurements.
Connects securely to your tools. The creator never sees your data.
About this skill
Premium Web refines an approved visual direction into a web interface through five ordered phases: composition, interaction and motion, accessibility and states, conditional rendered QA, and performance polish. It checks intentional mobile behavior, keyboard and focus states, reduced motion, loading, empty, error, and success states, and existing project design tokens without assuming tools or adding dependencies.
When to use it
Use it after a coherent visual direction and target surface are approved, when an interface needs responsive implementation or refinement. Provide the relevant design authority, existing tokens and components, target surface, and allowed changes. If the visual direction is materially unresolved, establish it first. This is not a strategy-invention, throwaway-prototype, isolated component-source selection, or final release-gating workflow.
The five phases
- Compose hierarchy, typography, spacing, and section relationships before decoration; design mobile behavior intentionally.
- Add interaction feedback and motion only where it clarifies state or hierarchy, respect reduced motion, and prefer capabilities already installed in the project.
- Check semantics, keyboard operation, visible focus, contrast, touch targets, and loading, empty, error, and success states.
- When browser evidence is available, inspect target responsive states, critical interactions, overflow, console and network health, and reduced motion. Otherwise mark rendered behavior UNVERIFIED.
- Remove unnecessary JavaScript or hydration, expensive layout animation, oversized media, and avoidable layout shifts when relevant.
What it returns
A fixed report with SURFACE, VISUAL DIRECTION PRESERVED, CHANGED COMPONENTS, RESPONSIVE STATES, A11Y / MOTION / PERFORMANCE CHECKS, RENDERED EVIDENCE, and UNVERIFIED.
Boundaries
Project authority, accepted specifications, tests, code, and current evidence outrank this workflow. It changes only the approved surface. If the task requires a new dependency, broad redesign, destructive content migration, commit, push, or deploy beyond the approved request, it stops for authority. The package's documented thresholds and checks are criteria to assess, not claims that a project passes; report only results actually observed.
Premium Web refines a supplied visual direction; if the hierarchy or overall strategy is materially unresolved, it stops for direction-setting rather than inventing one. Its outputs do not guarantee visual quality, WCAG conformance, or Core Web Vitals results. Browser and rendered checks depend on the active host and available preview; without evidence, they remain UNVERIFIED. The skill is not a throwaway-prototype workflow or final release gate, and it does not add dependencies, commit, push, deploy, run destructive migrations, or mutate production without explicit authority.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
Permissions
Read Files and Write Files are required to inspect project authority and implement only the approved surface. Browser-rendered QA and console/network observations are optional enhancements; without available browser evidence, report rendered behavior as UNVERIFIED. Terminal/Shell, MCP, external accounts, external services, environment variables, and package installation are not required by the package. No new dependency, broad redesign, destructive migration, commit, push, merge, deploy, or production mutation is implied.