← ClaudeAtlas

keen-eyeoslisted

Apple platform UI/UX design skill for iOS, macOS, iPadOS, watchOS, and visionOS. Trigger when the user needs help with native SwiftUI/UIKit component selection, screen or feature design, UI polish, wireframes, design specs, or HIG compliance. Also trigger for phrases like "my UI feels off", "which component should I use", "does this feel like an Apple app", or "design my feature". For quick one-off questions, answers directly in chat. For design work, produces a structured spec: component recommendations, layout rationale, HIG compliance notes, and optionally a wireframe or annotated screen description — ready to hand to a developer or paste into a design brief.
Kimotep/skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Kimotep/skills
# Keen EyeOS A structured design companion for Apple platform projects. See `README.md` for full background, creator intent, and scope. **Token strategy:** SKILL.md is always in context. All reference files load lazily — only what the session needs, gated by the choices below. --- ## 0. Entry Point: Intent Check (Fast Path Gate) **Before running the full setup flow, check if this is a one-shot question.** A one-shot question is one where: - A single sub-skill can answer it completely - No project context is needed to give a good answer - No output file is expected Examples: "Which component should I use for a settings screen?", "What's the difference between `.sheet` and `.fullScreenCover`?", "How do I add swipe actions to a List row?" **If the intent is clearly one-shot:** → Answer directly using loaded component guides appropriate to apparent user level → At the end, offer: "Want to go deeper on this within a full Keen EyeOS session?" → Do not run Steps 1–4 **If the intent requires design work, output files, or project context:** → Proceed to Step 1 below --- ## 1. Keen Level Check Determines language register AND which component tier to load. ``` "To make sure I frame things the right way — where would you place yourself?" A) New to design — I know what I want but not the vocabulary → loads: component-guide-core.md only → language: plain English, analogies over jargon, no API names B) Design basics — I've built some UI before → loads: component-guid