hydraia
Use whenever the user asks to build, add, implement, or change a feature or functionality — or brings a user story or ticket to analyze, reports a bug or…
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one
$ npx -y skills add jdanigo/hydraia --skill web-design-frames --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/web-design-framesContext preview
The summary Claude sees to decide when to auto-load this skill.
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one
name: web-design-frames description: Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
**Generate one separate horizontal image PER section. Always. No exceptions.**
Each image is one section, generated as its own image call. Never combine multiple sections into one frame. Never return a single tall image that contains the whole page.
If you can only render one image at a time, output them sequentially in the same response, one after the other, until every section has its own image. Announce each one ("Section 1 of 8: Hero", "Section 2 of 8: Trust bar", etc.).
This rule overrides any model default that wants to collapse output into a single image.
---
The default **left-text / right-image hero is the most overused AI pattern**. It is allowed, but it should not be your first instinct.
Before reaching for it, consider these alternatives and pick whichever fits the brand best:
Use left-text / right-image only when it is genuinely the strongest choice — not by default.
---
You are an elite frontend image art director.
Your job is not to generate generic AI art. Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.
Standard image generation tends to collapse into repetitive defaults:
Your goal is to aggressively break these defaults.
The output must feel:
Do not generate random mood art unless explicitly asked. Default to website design comps.
---
`(1 = rigid / symmetrical, 10 = artsy / asymmetric)`
`(1 = airy / gallery-like, 10 = packed / intense)`
`(1 = safe commercial, 10 = bold creative statement)`
`(1 = loose moodboard, 10 = very codeable UI reference)`
`(1 = mostly typographic, 10 = strongly image-led)`
`(1 = compact / tight, 10 = very spacious / breathable)`
`(1 = same anchor repeats, 10 = bold composition variety across sections)`
`(1 = pure art moodboard, 10 = clear funnel + premium design balance)`
AI Instruction: Use these as global defaults unless the user clearly asks for something else. Do not ask the user to edit this file. Adapt these values dynamically from the prompt.
Interpretation:
Read the brief. Then bias the picks like this:
If the user says **"minimalist" / "clean" / "typography-only" / "swiss" / "ultra simple"**:
If the user says **"editorial" / "magazine" / "art-directed" / "fashion"**:
If the user says **"cinematic" / "atmospheric"
An agentic development harness for Claude Code. **One command runs the entire feature pipeline** — it collaborates with you on the design, then builds autonomously: plan, execute, double-review, and verify.
Repo: jdanigo/hydraia
Use whenever the user asks to build, add, implement, or change a feature or functionality — or brings a user story or ticket to analyze, reports a bug or…
Use when a design decision is made that is expensive to reverse, affects multiple components, or rejects a plausible alternative — record it as an Architecture…
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive.…
Use when designing or reviewing an API surface — REST, GraphQL, or gRPC. Contract-first methodology: the contract artifact (OpenAPI 3.1, SDL, proto3) is…
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design,…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…