Skip to content

/stark-assets

Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when the agent supports it.

From plugin
stark
2914 skills14 commands
Install
> /plugin marketplace add f0d010c/stark
> /plugin install stark@stark

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/stark-assets

Context preview

What this command does when you run it.

Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when the agent supports it.

Command definition

stark-assets.md
description: Plan UI assets for a Stark design before implementation, including references, icons, typography, generated product mocks, and optional image generation when the agent supports it.
argument-hint: "<project or screen brief>"

/stark-assets

Legacy Claude Code command. In Codex, ask:

> Use stark assets to plan the visual assets for this app/site before building.

Plan assets for the project described by `$ARGUMENTS`.

Read:

  • `references/ui-patterns/ui-decision-brief.md`
  • `references/ui-patterns/asset-selection.md`
  • `references/ui-patterns/asset-realism-matrix.md`
  • `references/ui-patterns/asset-production-pipeline.md`
  • `references/ui-patterns/advanced-visual-systems.md` when assets become the signature visual system
  • the routed platform or web skill

Then produce an asset plan before implementation:

Asset plan
- Needed assets: product UI mock, icons, texture, typeface, references
- Source: local Stark library, lucide, generated CSS/SVG mock, imagegen, external reference
- Advanced visual system: main mechanic, owner, motif, fallback, rejected spectacle, if relevant
- License risk: none / low / needs attribution / avoid
- Usage: hero product preview, warning states, workflow diagram, empty state
- Reference extraction: structure only, not copied visuals
- Bans: stock hero photos, abstract AI gradients, placeholder images, private screenshots without permission

Rules

  • Do not freely browse and grab assets.
  • Ask whether the project needs icons, real product screenshots, reference UI patterns, typography, brand assets, or generated bitmap visuals.
  • Pull only assets that support the product job and visual direction.
  • If the agent is GPT/Codex and image generation is available, prefer generated bitmap assets for fictional hero imagery, textures, product concept art, or editorial visuals when CSS/SVG would be too weak.
  • Never include private/local screenshots unless the user explicitly allows it.
  • Do not copy copyrighted brand assets into public output.
  • Use real-world references to extract structure and interaction patterns, not visual identity.
Read more
Ships withstark

Design direction for AI coding agents—grounded in product behavior, platform idiom, and rendered evidence. Stark routes UI work across web, Windows, Apple, Android, cross-platform, UX, and design tokens.

Get the whole plugin, auto-invoked

Other commands on stark.