Skip to content
Back to skills

Web 3d Motion Hero By Aqq5ux

ASecurity

Apply an evidence-derived 3D and motion hero workflow observed across published GoodCase examples by Aceternity UI. Use when planning, designing, or implementing a website in this interface pattern, including requests for 网页, 落地页, 作品集, 3D hero, SaaS, ecommerce, or UI structure. This is an unofficial synthesis and must preserve source attribution.

  • 13 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgoperformance

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 18, 2026

npx -y skills add LearnPrompt/goodcase --skill web-3d-motion-hero-by-aqq5ux --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Web 3d Motion Hero By Aqq5ux?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Web 3d Motion Hero By Aqq5ux
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/learnprompt-web-3d-motion-hero-by-aqq5ux/badge)](https://www.skillsdirectory.com/skills/learnprompt-web-3d-motion-hero-by-aqq5ux)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: web-3d-motion-hero-by-aqq5ux
description: "Apply an evidence-derived 3D and motion hero workflow observed across published GoodCase examples by Aceternity UI. Use when planning, designing, or implementing a website in this interface pattern, including requests for 网页, 落地页, 作品集, 3D hero, SaaS, ecommerce, or UI structure. This is an unofficial synthesis and must preserve source attribution."
---

# Aceternity UI · Reusable Interactive Component Source

Turn the method into an executable, Case-grounded workflow. The Skill is incomplete unless the final artifact can be traced to one named anchor Case.

## 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.
- Preferred anchor Case from `references/cases.md`, or permission to select one.

## Required evidence gate

- Read `references/cases.md` before drafting on every invocation.
- Select exactly one anchor Case. Name it in the response; do not average several unrelated visual styles.
- Inspect the anchor's finished media with an available image, video, or browser tool. If the media cannot be inspected, say so and do not claim visual fidelity.
- Write a reference contract before the artifact:
  - **Preserve:** at least three structural traits supported by the Case evidence.
  - **Replace:** subject, copy, brand, or context supplied by the user.
  - **Avoid:** unrelated dominant motifs and superficial copying of creator identity.

## Workflow

1. Restate the requested deliverable, audience, and success criteria.
2. Read `references/cases.md` and select one anchor Case.
3. Inspect its finished media, summary, and prompt excerpt.
4. Produce the Preserve / Replace / Avoid reference contract.
5. Choose one visual protagonist.
6. Specify scroll or interaction triggers.
7. Limit first-load assets and mobile fallback.
8. Produce the requested artifact using the output contract below.
9. Compare it with the anchor Case, then revise material failures once.

## Output contract

- A reference contract naming one anchor Case, with Preserve, Replace, and Avoid decisions.
- 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.
- The response names one anchor Case and confirms that its evidence file was read.
- At least three visible or structural traits in the artifact map back to the Preserve list.
- No unrelated theme becomes dominant unless the user explicitly requested it.
- If finished media was inaccessible, the response labels the result as prompt-grounded rather than visually verified.
- Distinguish observed evidence from your own recommendation.
- Link or name the relevant GoodCase evidence used for the artifact.

## 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.
- Transfer structure and decision logic; do not impersonate a creator or present a close copy as original work.
- Do not publish, purchase, upload private assets, or make external account changes without explicit user approval.

Files in this skill

  • SKILL.md3.6 KB
  • references/cases.md23.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.