sergekostenchuk/ui-ux-agent-skill-system

visual-content-director

Plan and govern images, video, generated visuals, hero media, asset sourcing, visual proof, and content-media fit for UI/UX projects.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill visual-content-director

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Visual Content Director

This skill owns the visual-content layer: what images, videos, generated visuals, and asset treatments are needed to make a UI believable, inspectable, and on-brand. It does not own final UX strategy or SEO structure.

Operating Modes

  • asset-plan: define required images, videos, icons, maps, diagrams, and proofs.
  • hero-media: specify first-viewport media and composition rules.
  • generation-brief: create prompts for generated visuals without inventing factual claims.
  • asset-qa: check whether assets are relevant, readable, aligned, and safe to use.
  • handoff: package assets for Stitch, Pencil, Figma, or implementation.

Required Workflow

  1. Read references/visual-content-contract.md.
  2. Confirm project type, target audience, user promise, and brand constraints.
  3. Identify required content media:
  • real product/place/person/object proof;
  • generated or illustrative support;
  • maps, diagrams, icons, before/after, galleries, video.
  1. Use assets/visual-content-plan.template.md for planning.
  2. Distinguish real evidence assets from generated mood or placeholder assets.
  3. Hand off exact media requirements to Stitch, Pencil, Figma, or code owners.

Safety Rules

  • Do not fabricate real places, people, testimonials, property facts, awards, certifications, or legal claims.
  • Do not use private images externally without approval.
  • Label generated visuals as generated/planned if they are not real source evidence.
  • For reveal, before/after, or layered media, route alignment checks to image-layer-alignment-validator.
  • Public websites must keep important facts as text, not only baked into images.

Handoff Shape

text
Visual mode:
Asset roles:
Real evidence assets:
Generated/planned assets:
Hero media direction:
Forbidden visuals:
Accessibility notes:
SEO/LLM text preservation:
Next owner:
Checks:

Validation

When editing this skill, run:

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/visual-content-director
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/visual-content-director
python3 -m json.tool $CODEX_HOME/skills/visual-content-director/evals/evals.json >/dev/null

Related by task

from this repository

More skills

All skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

installs
1
GitHub stars
32
Updated
Sep 13