Individual skill
design-apps-with-imagegen
Explore and implement image-led app or site design changes, from a single element to a full screen, with varied visual directions, targeted inspiration, and user feedback. Use for design exploration, not routine UI fixes or implementation of an already selected design.
design-apps-with-imagegen/SKILL.md
Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 198
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,042 bytesSKILL.mdcore · 6,042 bytesagents/openai.yamlasset · 330 bytesassets/design-loop-reference.pngasset · 1,299,742 bytesreferences/edge-case-matrix.mddoc · 1,417 bytesreferences/imagegen-workflow.mddoc · 4,761 bytesreferences/implementation-miss-ledger.mddoc · 2,850 bytesreferences/visual-comparison.mddoc · 1,364 bytes
Read excerpt
# Design Apps with ImageGen
Explore the requested element or screen through images, implement the chosen direction, and compare the actual product against it. Keep the existing app and surrounding context unless broader changes are requested.
## 1. Establish scope
Inspect the affected screens, real content, capabilities, state owners, and responsive behavior. Separate existing contracts from proposed changes. Preserve scoped functionality and data unless the user authorizes changes; generated controls and text are proposals, not product truth.
Retain applicable navigation, account controls, and workspace access through loading and recovery states. Follow [design-preferences](../design-preferences/SKILL.md); shell replacement must be in scope. Report unrelated layout gaps rather than expanding the redesign.
## 2. Research and explore
Read [imagegen-workflow](references/imagegen-workflow.md). Match exploration to scope: for an element, normally offer three meaningful variants; for a screen or broader concept, start with four directions, including a purposeful wildcard. Vary composition or interaction, not merely color or decoration. A single labeled contact sheet can speed early feedback; expand promising directions separately when legibility or detail matters.