immersive-hero-designer-acrazie
Immersive Hero Designer / Acrazie
Build a distinctive, working hero that earns attention without sacrificing the message or the rest of the page. Treat references as evidence of visual intent, not as code or assets to copy. The deliverable is the complete section: visual, semantic heading and supporting copy, relevant action, and integration into the user's site.
Project loading and task authority
Published-library defaults remain model-invocable within the requested task. An explicit project kit or stricter instruction takes precedence: propose this skill from metadata and wait for the user's explicit command before reading its body. Apply the same gate to each dependency and the returning specialist after Interview. Never read or dispatch an unactivated dependency as a bypass. These gates are not filesystem controls or evidence of live host behavior.
Reuse a Task Contract with independent approval evidence when it covers the target, allowed files, delivery format, constraints, asset rights, acceptance criteria and scoped realization authority. A status label or concept selection alone is not execution approval. Reopen only materially invalidated decisions. Reusing a contract does not require Interview installation.