Design mobile app screens with Sleek skills

Who it's for

This fits people who want AI for mobile-app design and already have a Sleek account ready. The official repository is https://github.com/sleekdotdesign/agent-skills It says these are Agent skills for Sleek, and Sleek is the AI-powered mobile app design tool at https://sleek.design/ The included skill design-mobile-apps: Design mobile apps, create screens, and manage Sleek projects with AI It is not a general UI design library, and it does not mean this machine can already export a project.

Do not start creating screens without SLEEK_API_KEY. Keys are handled once at https://sleek.design/agents/setup for sign-in, upgrade, and creation, or managed at https://sleek.design/dashboard/api-keys The material writes no free quota and no required agent product.

First try in 3 minutes

The main path uses the official install command:

npx skills add sleekdotdesign/agent-skills

This is an interactive install. If you only want this one skill directly, the material also writes:

npx skills add sleekdotdesign/agent-skills -s sleek-design-mobile-apps

On the first try run only one of them, not both. Prerequisites: npx can run, and the environment already has SLEEK_API_KEY (a real key, not a placeholder). Confirm the current directory may receive skill configuration, then run it. The side effect is installing the Sleek skill. After install, first confirm the skill can be invoked, then touch a project.

Low-risk task: in an agent that can already use this skill, ask only to manage Sleek projects — see whether existing projects can be read — and say clearly not to create screens. Success signal: the agent can recognize a Sleek project or clearly report a missing key or permission, not that a pile of screens was already created. Creating screens changes the remote project and needs a separate confirmation. If the interface asks you to fill a placeholder key that never appears in the material, stop at once.

The material does not write which local directory the skill lands in; do not invent a copy path.

Use cases

Case 1: Manage an existing Sleek project. This matches manage Sleek projects inside design-mobile-apps. It fits people who already have a key and only want to confirm a project is visible. The material writes no field list and no project-ID rules; what you can confirm is that management happens on the Sleek side. Do not write case 1 as if a design draft were already changed.

Case 2: Create a design screen. This matches Design mobile apps, create screens. It fits people whose project is already selected and who have explicitly allowed a new screen. The material writes no screen template, resolution, or export format; what you can confirm is that the create action is done by this skill. Confirm the target project before you run it, and afterward open the matching screen in Sleek to check. The skill notes page is https://github.com/sleekdotdesign/agent-skills/blob/main/skills/design-mobile-apps That is in-repo documentation, not a second install command.

Limits

Without SLEEK_API_KEY you are outside the usable coverage of the material. Key creation and management point only to https://sleek.design/agents/setup and https://sleek.design/dashboard/api-keys Do not switch to a console that was never written. Interactive install and -s sleek-design-mobile-apps are two install methods from the same source; do not merge them into one compound command. The material names only design-mobile-apps; there is no other skill catalog. Do not infer that one client owns it exclusively.