prototype-ui-with-imagegen
Skill1 starsChanged 4 months agoNo licenceView on GitHub
Explore distinct visual directions for one native Apple or Android UI surface with built-in or delegated Codex image generation, compare them against real product and platform constraints, and optionally rebuild a selected direction in SwiftUI or Jetpack Compose. Runs in Codex or in any host that can call `codex exec`. Use for UI concepts, image-generated redesign variants, native component or screen prototypes, riffs on a concept, or implementation of a selected direction. Support system-native, hybrid-native, and custom-native strategies while preserving behavior, accessibility, the app shell, project components, symbols, and design tokens unless explicitly in scope. Report a screenshot-backed current-state audit, independent subagent review, labeled contact sheet, tradeoffs, detailed next steps, and downstream skill recommendations. Keep exploration read-only until the user explicitly selects a variant. Do not use for web, HTML, CSS, or generated production UI assets.
In this repository15 other files it gives its agents.
- android-designSkill
- apple-designSkill
- audit-and-clean-skillsSkill
- audit-ios-app-redesignSkill
- cross-store-ratings-reportSkill
- feature-extension-swarmSkill
- feature-planning-swarmSkill
- find-android-animation-opportunitiesSkill
- find-apple-animation-opportunitiesSkill
- google-io26-app-opportunity-auditSkill
- implementation-orchestratorSkill
- ios-app-preview-videosSkill
- review-android-animationsSkill
- review-apple-animationsSkill
- wwdc26-app-opportunity-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. About 0 are common, 33 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈33
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

