web-3d-motion-hero

3D and motion hero

Turn the method into an executable workflow. Ground source-specific claims in the bundled Case evidence.

Inputs

Ask only for missing inputs:

• Page goal, target audience, offer, and primary action.
• Content, proof, product assets, and technical stack.
• Responsive, accessibility, performance, and interaction constraints.

Workflow

1. Restate the requested deliverable, audience, and success criteria.
2. Read references/cases.md when the user asks for examples, attribution, provenance, or a close recreation.
3. Choose one visual protagonist.
4. Specify scroll or interaction triggers.
5. Limit first-load assets and mobile fallback.
6. Produce the requested artifact using the output contract below.
7. Critique the artifact against the verification checklist and revise material failures once.

Output contract

• A page narrative and section hierarchy.
• A component and interaction specification.
• Implementation-ready copy or code appropriate to the user request.
• A responsive, accessibility, and performance verification checklist.

Verification

• The first screen communicates one value proposition and one primary action.
• Every section advances the same user journey with real content.
• Responsive behavior, keyboard access, contrast, loading, and motion fallback are checked.
• Distinguish observed evidence from your own recommendation.
• Link or name the relevant GoodCase evidence when the user asks where the method came from.

Safety and attribution

• Do not invent an original prompt, model, result, creator, metric, or source.
• Do not imply this Skill is authored, endorsed, or officially distributed by a referenced creator.
• Preserve creator attribution when reproducing or discussing a source Case.
• Do not publish, purchase, upload private assets, or make external account changes without explicit user approval.