Frontend Design
Build a frontend direction from the audience, real content, and existing brand constraints; resolve hierarchy before decorative styling.
Design SwiftUI screens with semantic components, clear state, and platform-appropriate navigation.
---
name: knoveya-ios-design
description: "Design SwiftUI screens with semantic components, clear state, and platform-appropriate navigation. Use for matching ux design work."
---
# iOS Design
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Design SwiftUI screens with semantic components, clear state, and platform-appropriate navigation.
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
Dynamic type, voice access, and asynchronous failures remain usable.
## Example task
Provide an understandable retry state in a native list.
## 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-ios-design as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-ios-design/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.
Provide an understandable retry state in a native list.
Dynamic type, voice access, and asynchronous failures remain usable.
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.