- Home
- Skills
- Frontend & Web Apps
- Conversion Design Architect
Works with the AI Agents you already use
Conversion Design Architect
Design briefs and page audits built on 107 numbered rules that show evidence type, number, year and sample where the source has them. Computed contrast, WCAG 2.2 AA plan, NO/EU legal notes.
$5
Conversion Design Architect
Example session with this skill installed
Quick check: is a countdown timer on our checkout a good idea? We sell shoes online, market Norway.
- Read your context and instructions
- Compiled the conversion design architect
Verdict: No live countdown. Use a static, true delivery cut-off instead.
Evidence
- E7.12 — Tuncer et al. 2023, n = 202 (controlled, fictional clothing shops): countdown timers and stock bars raised frustration and lowered perceived vendor benevolence. Tag: E.
- E7.13 — EU Commission sweep 2026: 18 % of shops used pressure tactics, more than half misleading. Tag: E (prevalence).
- E7.14 — Baymard 2024: 83 % of checkouts lack a real order cut-off for next-day delivery — the one form of urgency users act on. Tag: E.
Do this instead
Replace the timer with a static line inside the framed payment section, directly above the pay button:
Bestill innen kl. 14:00 for levering i morgen.
Text #1A1A1A on #FFFFFF (17.4:1), 16 px, no animation. If you later insist on a live clock, it must be real (tied to the actual cut-off), pausable (WCAG 2.2.2) and never reset.
Caveat (Norway)
A countdown that resets, or "only 2 left" without real stock, may breach markedsføringsloven § 7/8 and the EU unfair-practices blacklist (false limited availability). Recommend counsel review for any urgency claim in client-facing material.
Next step
Tell me the actual cut-off time and carrier, and I'll write the three states of that line (before cut-off, after cut-off, weekend).
Connects securely to your tools. The creator never sees your data.
About this skill
Most "high-converting design" advice is folklore: red buttons, hidden navigation, countdown timers, "the fold is dead". Conversion Design Architect replaces it with what the research actually shows — and tells you how strong that evidence is.
Four modes
Design Brief — give it a business, an audience and one conversion goal. It returns a client pack (plain-language summary, conversion logic, page architecture per page type, copy frame, trust placement, inputs still needed) and a developer pack (design tokens as CSS custom properties with computed contrast ratios and a dark-surface CTA rule, component states, WCAG 2.2 AA conformance plan, performance budget, tracking events, a semantic HTML wireframe).
Conversion Audit — give it a URL, HTML or screenshots (plus PageSpeed data if you have it). It prints a coverage line first ("41/60 checks verifiable"), scores only what it can see, ranks the top-5 fixes by evidence level and ease, and adds WCAG gaps, legal flags and a 30-day plan.
Quick Check — "Is a countdown timer a good idea?" → verdict, evidence (ID, number, year, sample), alternative, caveat, in 200 words or fewer.
Element Request — a wish-list of page elements with no goal → verdict and alternative per element, then the right questions.
What is different
- 107 numbered rules (106 with a named source, 81 with a hard number), 105 of them tagged E (study) / S (survey) / Q (expert review) / C (convention) / N (standard), with sample size, year and context where the source reports them — desktop vs mobile, e-commerce vs services, English vs Norwegian are flagged when generalised.
- 42 anti-patterns in four honest categories: debunked, unsupported, ethically risky, may-breach-law — e.g. "mark only optional fields" (Baymard: 32 % then fail a required field), resetting countdowns (EU blacklist), decoy plans, self-made trust badges.
- WCAG 2.2 AA mapped to hero, CTA, nav, forms, checkout (incl. 3.3.4 review step, 3.3.7, 3.3.8), carousels, cookie dialogs, chat widgets; two-colour focus pattern; QA loop.
- Legal notes: Norway in depth (dated; IKT-forskriften WCAG 2.0 AA floor, EAA not in the EEA as of 2026, markedsføringsloven, prisopplysningsforskriften 30-day rule, payment-button wording, review-transparency duty, ekomloven cookies); EU generic; Germany, UK, US as pointers marked for verification. Design guidance, not legal advice.
- Palette method with the WCAG luminance formula, relative OKLCH steps and a worked example; font pairing defaults; budget conventions.
Use it for
Agency and freelance web design, redesign pitches, campaign landing pages, Shopify/WooCommerce product and checkout reviews, SaaS pricing pages, clinic/trades/consultancy service pages, B2B lead-gen, accessibility-first public-sector work.
Honest limits
No A/B study shows accessibility lifts conversion (the case is reach and law); lead-form field-count data is pre-2020; audit checks that need speed data or a keyboard test are marked N/A unless you supply them; legal notes are design guidance, not advice.
Files: SKILL.md + references/evidence-rules.md, page-blueprints.md, palette-method.md, wcag-checklist.md, anti-patterns.md, audit-rubric.md, legal-notes.md.
Requires specific inputs (screenshots/HTML) for audits. Not a substitute for legal counsel. Does not perform SEO or branding. Pre-2015 evidence is flagged as aged.
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 19 days ago
Permissions
No special permissions declared or detected