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 )
Fetches sleek-design-mobile-apps from sleekdotdesign/agent-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/sleek-design-mobile-apps
Restart Cursor to activate sleek-design-mobile-apps. Access via /sleek-design-mobile-apps in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
sleek.design is an AI-powered mobile app design tool. You interact with it via a REST API at /api/v1/* to create projects, describe what you want built in plain language, and get back rendered screens. All communication is standard HTTP with bearer token auth.
Base URL: https://sleek.designAuth: Authorization: Bearer $SLEEK_API_KEY on every /api/v1/* request
Content-Type: application/json (requests and responses)
CORS: Enabled on all /api/v1/* endpoints
Prerequisites: API Key
Create API keys at https://sleek.design/dashboard/api-keys. The full key value is shown only once at creation — store it in the SLEEK_API_KEY environment variable.
Required plan: Pro or higher (API access is gated)
Key scopes
Scope
What it unlocks
projects:read
List / get projects
projects:write
Create / delete projects
components:read
List components in a project
chats:read
Get chat run status
chats:write
Send chat messages
screenshots
Render component screenshots
Create a key with only the scopes needed for the task.
Security & Privacy
Single host: All requests go exclusively to https://sleek.design. No data is sent to third parties.
HTTPS only: All communication uses HTTPS. The API key is transmitted only in the Authorization header to Sleek endpoints.
Minimal scopes: Create API keys with only the scopes required for the task. Prefer short-lived or revocable keys.
Image URLs: When using imageUrls in chat messages, those URLs are fetched by Sleek's servers. Avoid passing URLs that contain sensitive content.
Quick Reference — All Endpoints
Method
Path
Scope
Description
GET
/api/v1/projects
projects:read
List projects
POST
/api/v1/projects
projects:write
Create project
GET
/api/v1/projects/:id
projects:read
Get project
DELETE
/api/v1/projects/:id
projects:write
Delete project
GET
/api/v1/projects/:id/components
components:read
List components
GET
/api/v1/projects/:id/components/:componentId
components:read
Get component
POST
/api/v1/projects/:id/chat/messages
chats:write
Send chat message
GET
/api/v1/projects/:id/chat/runs/:runId
chats:read
Poll run status
POST
/api/v1/screenshots
screenshots
Render screenshot
All IDs are stable string identifiers.
Endpoints
Projects
List projects
GET /api/v1/projects?limit=50&offset=0
Authorization:Bearer $SLEEK_API_KEY
Fetches a single component by ID. Use this when you need the code for a specific screen (e.g., after a chat run returns a componentId in its operations).
GET /api/v1/projects/:projectId/components/:componentId
Authorization:Bearer $SLEEK_API_KEY
Response 200 — same shape as a single item from the list endpoint:
This is the core action: describe what you want in message.text and the AI creates or modifies screens.
POST /api/v1/projects/:projectId/chat/messages?wait=false
Authorization:Bearer $SLEEK_API_KEYContent-Type:application/jsonidempotency-key:<optional, max 255 chars>{"message":{"text":"Add a pricing section with three tiers"},"imageUrls":["https://example.com/ref.png"],"target":{"screenId":"scr_abc"}}
Field
Required
Notes
message.text
Yes
1+ chars, trimmed
imageUrls
No
HTTPS URLs only; included as visual context
target.screenId
No
Edit a specific screen using its screenId (not componentId); omit to let AI decide
?wait=true/false
No
Sync wait mode (default: false)
idempotency-key header
No
Replay-safe re-sends
Response — async (default, wait=false)
Status 202 Accepted. result and error are absent until the run reaches a terminal state.
Blocks up to 300 seconds. Returns 200 when completed, 202 if timed out.
{"data":{"runId":"run_111","status":"completed","statusUrl":"...","result":{"assistantText":"I added a pricing section with...","operations":[{"type":"screen_created","screenId":"scr_xyz","screenName":"Pricing","componentId":"cmp_xyz"},{"type":"screen_updated","screenId":"scr_abc","componentId":"cmp_abc"},{"type":"theme_updated"}]}}}
Chat — Poll Run Status
Use this after async send to check progress.
GET /api/v1/projects/:projectId/chat/runs/:runId
Authorization:Bearer $SLEEK_API_KEY
Response — same shape as send message data object:
{"data":
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
