cinematic-site-qa
Skill4 starsChanged 3 months agoMITView on GitHub
Run the final mechanical and visual QA for cinematic websites, including assets, catalogs, accessibility, responsive behavior, motion, video seeking, 3D performance, and production fallbacks.
In this repository26 other files it gives its agents.
- aigentSkill
- aigent-3d-scroll-systemSkill
- aigent-asset-gallery-systemSkill
- aigent-business-sitesSkill
- aigent-designSkill
- aigent-landing-page-polishSkill
- asset-provenance-auditSkill
- cinematic-asset-gallerySkill
- cinematic-studioSkill
- cinematic-web-directorSkill
- creative-asset-directorSkill
- design-forensicsSkill
- design-resolverSkill
- gsap-scroll-choreographySkill
- hyperframes-videoSkill
- inspiration-originality-auditSkill
- modular-scroll-pageSkill
- publish-siteSkill
- reference-synthesisSkill
- remotion-web-assetsSkill
- spline-web-sceneSkill
- threejs-web-sceneSkill
- video-asset-pipelineSkill
- video-scrub-deckSkill
- visual-design-criticSkill
- web-3d-asset-pipelineSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
no essential information only in motion
- Distinctive: line 72
no generic card scaffold
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cinematic Site QA
QA the built page, not the intention.
Static checks
npm run check
npm run assets
npm run catalogs
npm run audit -- path/to/page path/to/shared.cssBrowser matrix
Minimum:
- desktop 1440 × 1000
- mobile 390 × 844
- reduced motion
- keyboard only
- slow network
- failed media or WebGL
- page reload at a deep anchor
- forward and reverse scroll
Inspect
Clarity
- first viewport explains the offer, artifact, or task
- primary action is visible
- real proof appears early
Media
- poster loads
- desktop and mobile variants are correct
- later assets are lazy
- scrub media seeks
- range requests work
- 3D pauses offscreen
- fallbacks preserve meaning
Accessibility
- focus visible
- semantic controls
- contrast
- no essential information only in motion
- no autoplay audio
- touch targets usable
- zoom and text expansion do not break layout
Performance
- no horizontal overflow
- bounded pixel ratio
- no excessive
will-change - no layout thrash
- initial asset budget understood
- console and network errors resolved
Taste
- one dominant idea
- no generic card scaffold
- motion has a job
- media belongs to the product world
- the result could not be relabeled for an unrelated product
Record failures with file, state, impact, and the smallest shared fix.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.