Results for “clearout”

6 skills
adobe
rollout
Deploy an entire redesigned site to AEM Edge Delivery Services by inventorying migrated pages, deduplicating blocks, and driving per-page deployment with tracking and verification.
142 · bundle
adobe
page-prep
Detects and removes disruptive overlays (cookie banners, modals, paywalls, login walls) from webpages before screenshots, scraping, or browser automation.
142 · bundle
brycewang-stanford
quarto-clean
Cleans a Quarto (.qmd) file by replacing LaTeX holdovers with proper Quarto/Pandoc syntax so the document renders correctly to HTML, PDF (Typst/LaTeX), and Word. Fixes citations (\citep → [@key]), cross-references (\ref → @label), figures (\includegraphics → markdown), tables, text formatting (\textbf → **bold**), inline math (\( \) → $ $), hyperlinks (\href → [text](url)), footnotes (\footnote → ^[]), list environments, section headings, and R Markdown chunk options (dot-style → #| YAML). Use when asked to clean, fix, modernize, or port a Quarto or R Markdown document; when LaTeX commands appear in a .qmd file; when a document fails to render to Word or Typst; or when citations/cross-references do not appear in non-LaTeX output.
1k
kursku
clarify
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
55 · bundle
diegojcn
clarify
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
1 · bundle
theycallmeholla
ux-audit
Reconstruct a product flow, then audit how usable it is — whether it makes sense, where users get confused or stuck, whether the copy and instructions are clear, and where friction causes drop-off. Produces a prioritized, severity-weighted findings report. Works from three inputs: frontend code in a repo, a live running app driven via a browser, or a written flow / spec / screenshots. Use this skill whenever the user asks for a UX review, usability audit, "is this flow confusing", "does this signup/onboarding/checkout make sense", "why are people dropping off", "audit this form", "where's the friction", or hands over a flow and asks whether it's user-friendly. Trigger even on casual phrasings ("is my checkout any good?") — it imposes the structure ad-hoc UX opinions miss. Audits flow usability and friction; for visual polish and interface quality the impeccable audit/critique skills apply instead.
0 · bundle