design-mobile-apps

作者: designed-by-ai

Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.

npx skills add https://github.com/designed-by-ai/skills --skill design-mobile-apps

Designing with Sleek

Design mobile apps in minutes

Overview

sleek.design provides a REST API at /api/v1/* to create projects, design screens from a brief, and fetch their HTML and renders.

Base URL: https://sleek.design Auth: Authorization: Bearer $SLEEK_API_KEY, except the public device start/poll endpoints Content-Type: send application/json for JSON request bodies. CORS: Enabled on all /api/v1/* endpoints Envelope: check HTTP status first. Successful JSON wraps its payload in data; lists also include sibling pagination. Errors use top-level code, status and message, with optional data.url. Successful screenshots and share cards return image bytes; 204 has no body. Ids: opaque 11-character tokens like V1StGXR8Z5j, with no type prefix. Nothing about an id says whether it names a project, screen, component, version or theme, so track each one by the response field it arrived in. Parsing responses: write the body to a file (curl -o run.json) and parse the file. Piping JSON through echo corrupts it: zsh expands the escaped \n inside string values into real newlines, which makes the body invalid JSON. API docs: OpenAPI spec at https://sleek.design/api/v1/spec.json; browsable docs at https://sleek.design/api/v1/docs. Fetch the spec for any contract detail not covered here.


Designing or implementing

A single run can take both directions — "design me a fitness app and build it in Expo" is a design pass followed by an implementation pass. Gate each pointer on the artefact in front of you rather than on a one-time reading of the request:

Designing — you are about to send a chat message to Sleek. Read designing.md first; it carries the create → chat → screenshot loop, how to author a style direction, and when to seed one from a reference instead.

Implementing. Before writing code from a Sleek design, read implementing.md for version selection, native conversion, working features, and acceptance checks.

User shot and review shot

Screenshots come in two framings, and each file below asks for one by name:

  • A user shot is the default render: viewport height, phone-shaped. This is the one you show the user.
  • A review shot adds fullHeight: true, one component per request. This is the one you judge your own work against.

Prerequisites: API Key

If SLEEK_API_KEY is not set, use the device flow so the user never handles the raw key:

  1. POST https://sleek.design/api/v1/device/start (no auth) with body {"source": "your-tool-slug"}. The response contains a verificationUrl, a human-checkable userCode, a secret deviceCode, and a poll interval in seconds.
  2. Show the user the verificationUrl and the userCode, and tell them to confirm the code matches before approving.
  3. Poll POST https://sleek.design/api/v1/device/poll with {"deviceCode": "..."} every interval seconds. On pending, keep waiting. On approved, store data.key privately as SLEEK_API_KEY on that first read: the key is handed over once. On expired or 404 NOT_FOUND, start a new flow. See Device: Poll for the response contract.

Fallback: send the user to https://sleek.design/agents/setup, which handles sign-in, plan upgrade, and key creation in one place, and ask them to paste the key back to you. Keys can also be managed at https://sleek.design/dashboard/api-keys. The full key value is shown only once at creation, and a free account holds one active key at a time.

Plans: free accounts can try the API with their one-time trial credits (about one design run), so a new user can see their first design before any payment decision. Sustained use requires the Pro plan or higher. This file carries no figures on purpose — read the current price, billing periods and credit allowance from https://sleek.design/agents.md, which is generated from Sleek's live pricing, and quote them from there. When cost becomes relevant (the user asks, an upgrade is needed to continue, or you're about to send them to a payment page), state that pricing plainly, including the yearly option, so the user sees a payment step coming before they reach it.


Quick Reference: All Endpoints

Every endpoint the API exposes:

MethodPathScope
GET/api/v1/projectsprojects:read
POST/api/v1/projectsprojects:write
GET/api/v1/projects/:idprojects:read
DELETE/api/v1/projects/:idprojects:write
GET/api/v1/projects/:id/componentscomponents:read
GET/api/v1/projects/:id/components/:componentIdcomponents:read
GET/api/v1/referencesany valid key
POST/api/v1/projects/:id/chat/messageschats:write
GET/api/v1/projects/:id/chat/runs/:runIdchats:read
POST/api/v1/projects/:id/chat/runs/:runId/cancelchats:write
POST/api/v1/screenshotsscreenshots
POST/api/v1/share-cardsscreenshots
POST/api/v1/device/startpublic, no auth
POST/api/v1/device/pollpublic, no auth

Create a key holding only the scopes the task uses.

Every row above is specified in full — request body, response shape, field defaults, status codes — in endpoints.md. This table is enough to pick an endpoint; read the reference when you need a contract detail it doesn't carry.


Error Shapes

{
  "defined": true,
  "code": "FORBIDDEN",
  "status": 403,
  "message": "...",
  "data": { "url": "https://sleek.design/..." }
}
HTTPCodeWhen
401UNAUTHORIZEDMissing/invalid/expired API key
403FORBIDDENValid key, wrong scope or plan
404NOT_FOUNDResource doesn't exist
400BAD_REQUESTValidation failure
409CONFLICTAnother run is active for this project
429TOO_MANY_REQUESTSRender cap: 1000 screenshots + share cards per hour per org, counted on API-key requests only
500INTERNAL_SERVER_ERRORServer error

401, 403 and 429 bodies may include data.url: a page where the user can fix the condition (create a key, upgrade the plan). Share it as-is.

Chat run-level errors (inside data.error):

CodeMeaning
out_of_creditsOrganization has no credits left
execution_failedAI execution error
cancelledRun cancelled via the cancel endpoint
request_message_persist_failedThe run failed before reaching the AI; the message was never stored

For out_of_credits, relay error.url and wait for the user to resolve it. Follow Safe retries for replay versus a new attempt after either recoverable failure.

相关技能

azure-resource-visualizer
microsoft
将Azure资源组转换为详细的架构图,展示资源关系与配置。发现资源组内的所有资源,分析其配置、依赖关系和互连情况。生成按逻辑层(网络、计算、数据、安全、监控)组织的Mermaid图表,包含SKU详情和连接标签。映射包括网络连接、数据流、身份绑定和配置依赖在内的关系。
devopsdesigndevelopment
expo-native-ui
expo
框架(开源)。构建美观、原生体验的Expo屏幕。涵盖Apple HIG样式、语义化颜色、原生控件、SF Symbols、媒体、动画、视觉效果、渐变、存储和响应式布局。如需路由和导航,请使用expo-router技能。
designdevelopment
expo-router
expo
框架(开源)。Expo Router的导航与路由。涵盖基于文件的路由、分组与动态路由、文件夹组织、带预览和上下文菜单的链接、原生堆栈、页面标题、模态框与表单页、原生标签页、页眉与工具栏,以及页眉搜索栏。
apidesigndevelopment
expo-ui
expo
框架(开源)。使用@expo/ui包构建原生UI:在iOS上呈现真实的SwiftUI,在Android上呈现Jetpack Compose,这些UI通过React在Expo或React Native应用中渲染。涵盖通用跨平台组件(从@expo/ui导入的Host、Column、Row、Button、Text、List等),流行React Native社区库的即插即用替代品(BottomSheet、DateTimePicker、Slider、Menu等),以及平台特定的SwiftUI(@expo/ui/swift-ui,仅限iOS)和Jetpack Compose...
designdevelopment
ui-sdk
vercel
Builds interfaces with ui-sdk in React, Vue, Svelte, Solid or web components. Covers choosing and composing its components, building a component or behavior it doesn't ship from @ui-sdk/core (like a stepper, splitter, transfer list or emoji picker), making the interface usable by agents through createAgent, agent tools and WebMCP, and testing keyboard, focus, ARIA, server rendering and right to left, including writing tests for an existing component. Use whenever a project has @ui-sdk/*...
testingdesigndevelopment
Web Interface Guidelines
Vercel
审查UI代码是否符合Web Interface Guidelines。当被要求“审查我的UI”、“检查无障碍性”、“审计设计”、“审查用户体验”或“对照最佳实践检查我的网站”时使用。
designdevelopment
accessibility-engineering
addyosmani
审计现有界面是否符合 WCAG 2.2 AA,并修复发现的违规问题。适用于审计页面或组件的无障碍性、运行 axe-core 或 pa11y、排查 a11y 违规问题,或在发布前检查屏幕阅读器和对比度问题。
developmenttestingdesign
animate-expo
emilkowalski
在 React Native 和 Expo 中构建动画,按照决定动画效果是否自然的顺序做出选择——是否需要动画、在哪个线程运行、使用哪些属性、采用弹簧还是定时动画、手势如何交接,以及如何降级。使用 Reanimated、Gesture Handler、Expo Router 和 expo-haptics 编写实现。适用于在 Expo 应用中为任何内容添加动画、添加手势、底部面板、屏幕过渡、按压反馈或触觉反馈,或修复设备上卡顿的动画。用于……
developmentdesign