要点
AI-powered mobile app design tool with REST API for creating projects, describing designs in plain language, and rendering screens.
- Supports high-level requests ("design a fitness app") and specific edits ("add a pricing section to this screen"); send natural language descriptions via chat messages and let the AI decide what to create or modify
- Requires Pro+ plan and API key with scoped permissions (
projects:read/write,chats:read/write,screenshots,components:read) - Async and sync modes available; async returns immediately with a run ID for polling, sync blocks up to 300 seconds
- Always screenshot newly created or updated screens after each chat run and deliver them to the user; combine all project screens into one screenshot when screens are created for the first time
- One active run per project at a time; retry failed requests safely using idempotency keys
SKILL.md
Designing with Sleek
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 with Sleek
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.