Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

mobile-responsive-qa

Estrelas54

Forks24

Atualizado21 de junho de 2026 às 20:33

Run mobile responsive QA for websites and apps. Use after layout, media, navigation, form, pricing, dashboard, gallery, checkout, or motion changes to inspect phone and tablet viewports, prevent horizontal overflow, fix crop issues, verify touch targets, and make mobile feel intentionally composed.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

TheGoat395

TheGoat395/Codex-Skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	mobile-responsive-qa
description	Run mobile responsive QA for websites and apps. Use after layout, media, navigation, form, pricing, dashboard, gallery, checkout, or motion changes to inspect phone and tablet viewports, prevent horizontal overflow, fix crop issues, verify touch targets, and make mobile feel intentionally composed.

Mobile Responsive QA

Use this skill to catch mobile problems that make otherwise premium sites feel rushed.

Workflow

Inspect the project, scripts, routes, local/deployed URL, production surfaces, and available QA/deployment tooling.
Read Mobile Responsive QA Guide before claiming the site is ready.
Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Always Protect

Inspect before changing or shipping: framework, package scripts, build output, routes, forms, media, animation stack, deployment target, environment variables, analytics, SEO metadata, accessibility risks, and available browser QA tooling.
Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
Verify desktop and mobile rendered output, not only source code. For visual or motion work, inspect screenshots, browser behavior, console errors, network failures, and responsive layout.
Treat forms, checkout, booking, CMS content, analytics, environment variables, and deployments as production surfaces with error, loading, empty, success, and rollback states.
Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.

Mais deste repositório

mesmo repositório

design-motion-principles

TheGoat395/Codex-Skills

Motion and interaction design skill using interpretive lenses informed by publicly available work from Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Two modes: build interactive components with purposeful motion, or audit existing animations to catch AI-generated motion anti-patterns. Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or motion design work in React, Framer Motion, CSS, or HTML. This skill is not authored, reviewed, or endorsed by the referenced designers.

2026-07-0254

frontend-quality-auditor

TheGoat395/Codex-Skills

Audit frontend websites and apps before launch. Use for production-readiness reviews, visual polish checks, responsive QA, accessibility risks, performance and SEO basics, interaction states, forms, media, copy clarity, trust signals, and ship/no-ship recommendations for React, Next.js, static sites, dashboards, landing pages, portfolios, and product UI.

2026-07-0154

gsap-performance

TheGoat395/Codex-Skills

GSAP performance guidance — prefer transforms, avoid layout thrashing, use will-change selectively, and batch animation work. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.

2026-06-2554

accessibility-audit-websites

TheGoat395/Codex-Skills

Audit website accessibility. Use for semantic structure, headings, alt text, forms, focus states, keyboard navigation, color contrast, labels, ARIA misuse, reduced motion, captions, skip links, modals, menus, carousels, and final frontend QA aligned with WCAG-style accessibility expectations.

2026-06-2154

accessibility-performance-polish

TheGoat395/Codex-Skills

Improve website accessibility and performance polish. Use for semantic HTML, keyboard navigation, focus states, contrast, alt text, reduced motion, image/video loading, canvas fallbacks, bundle caution, animation performance, and final production readiness for polished websites.

2026-06-2154

animation-easing-language

TheGoat395/Codex-Skills

Define animation easing language for premium websites and apps. Use for motion timing systems, easing curves, spring feel, duration scales, stagger rhythm, delay strategy, entrance/exit timing, tactile controls, cinematic sections, and translating luxury, modern, fast, calm, or playful motion words into concrete values.

2026-06-2154

name	mobile-responsive-qa
description	Run mobile responsive QA for websites and apps. Use after layout, media, navigation, form, pricing, dashboard, gallery, checkout, or motion changes to inspect phone and tablet viewports, prevent horizontal overflow, fix crop issues, verify touch targets, and make mobile feel intentionally composed.

Mobile Responsive QA

Use this skill to catch mobile problems that make otherwise premium sites feel rushed.

Workflow

Inspect the project, scripts, routes, local/deployed URL, production surfaces, and available QA/deployment tooling.
Read Mobile Responsive QA Guide before claiming the site is ready.
Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Always Protect

Inspect before changing or shipping: framework, package scripts, build output, routes, forms, media, animation stack, deployment target, environment variables, analytics, SEO metadata, accessibility risks, and available browser QA tooling.
Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
Verify desktop and mobile rendered output, not only source code. For visual or motion work, inspect screenshots, browser behavior, console errors, network failures, and responsive layout.
Treat forms, checkout, booking, CMS content, analytics, environment variables, and deployments as production surfaces with error, loading, empty, success, and rollback states.
Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.