What problem does it solve? Designing a website or app often defaults to generic card-grid templates that ignore the project's unique domain. This Skill turns a project's context — its domain, brand, sitemap, and real content — into a ranked list of custom interactive mechanics, one per section, so every page feels purpose-built rather than templated. ## Core Features & Use Cases - Domain-to-mechanic generation: Mines a project's symbols, rituals, metaphors, and data shapes to propose one distinct interactive mechanic per page or section. - Interaction-primitive menu: Chooses from proven patterns such as domain-object-as-navigation, pinned scroll-driven SVG scenes, cursor-reveal heroes, numbered pinned steps, and 3D-tilt glyphs. - Ranked deliverable table: Outputs Component, Page/section, Domain metaphor, Interaction primitive, Build approach, Effort (S/M/L), and the real content or CTA each mechanic carries, led by a signature centerpiece. - Use Case: During a church website kickoff, use this Skill to produce ideas like a Bible-as-navigation centerpiece, a baptism dove scroll scene, and a praying-hands 3D tilt beside the giving section. ## Quick Start Ask the agent to generate custom component ideas for your project by providing its domain, brand, sitemap, and real content.
