attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
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 CoWork-OS/CoWork-OS --skill imagegen-frontend-web --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/imagegen-frontend-webContext 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: imagegen-frontend-web 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. version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com> source-author: "Leonxlnx"
**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.
---
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" / "premium" / "luxury" / "bold"**:
If the user says **"SaaS" / "product" / "dashboard" / "fintech" / "infra"**:
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository…
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch,…
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Use when the user asks for a repository-wide or scoped-path security scan.