Frontend Design
Build a frontend direction from the audience, real content, and existing brand constraints; resolve hierarchy before decorative styling.
Generate mobile screen concepts as consistent visual explorations, not working applications.
---
name: knoveya-imagegen-frontend-mobile
description: "Generate mobile screen concepts as consistent visual explorations, not working applications. Use for matching ux design work."
---
# Imagegen Frontend Mobile
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Generate mobile screen concepts as consistent visual explorations, not working applications.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Text, platform conventions, and multi-screen continuity remain plausible.
## Example task
Create a three-screen onboarding concept with matching navigation.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-imagegen-frontend-mobile as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-imagegen-frontend-mobile/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Create a three-screen onboarding concept with matching navigation.
Text, platform conventions, and multi-screen continuity remain plausible.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.