AI-powered mobile app design tool with REST API for creating projects, describing designs in plain language, and rendering screens.
Works with
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 a
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsleek-design-mobile-appsExecute the skills CLI command in your project's root directory to begin installation:
Fetches sleek-design-mobile-apps from sleekdotdesign/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sleek-design-mobile-apps. Access via /sleek-design-mobile-apps in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
297
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
297
stars
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.design
Auth: Authorization: Bearer $SLEEK_API_KEY on every /api/v1/* request
Content-Type: application/json (requests and responses)
CORS: Enabled on all /api/v1/* endpoints
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)
| 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.
https://sleek.design. No data is sent to third parties.Authorization header to Sleek endpoints.imageUrls in chat messages, those URLs are fetched by Sleek's servers. Avoid passing URLs that contain sensitive content.| 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.
GET /api/v1/projects?limit=50&offset=0
Authorization: Bearer $SLEEK_API_KEY
Response 200:
{
"data": [
{
"id": "proj_abc",
"name": "My App",
"slug": "my-app",
"createdAt": "2026-01-01T00:00:00Z",
"updatedAt": "..."
}
],
"pagination": { "total": 12, "limit": 50, "offset": 0 }
}
POST /api/v1/projects
Authorization: Bearer $SLEEK_API_KEY
Content-Type: application/json
{ "name": "My New App" }
Response 201 — same shape as a single project.
GET /api/v1/projects/:projectId
DELETE /api/v1/projects/:projectId → 204 No Content
GET /api/v1/projects/:projectId/components?limit=50&offset=0
Authorization: Bearer $SLEEK_API_KEY
Response 200:
{
"data": [
{
"id": "cmp_xyz",
"name": "Hero Section",
"activeVersion": 3,
"versions": [{ "id": "ver_001", "version": 1, "code": "<!DOCTYPE html>...</html>", "createdAt": "..." }],
"createdAt": "...",
"updatedAt": "..."
}
],
"pagination": { "total": 5, "limit": 50, "offset": 0 }
}
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:
{
"data": {
"id": "cmp_xyz",
"name": "Hero Section",
"activeVersion": 3,
"versions": [{ "id": "ver_001", "version": 1, "code": "<!DOCTYPE html>...</html>", "createdAt": "..." }],
"createdAt": "...",
"updatedAt": "..."
}
}
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_KEY
Content-Type: application/json
idempotency-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 |
wait=false)Status 202 Accepted. result and error are absent until the run reaches a terminal state.
{
"data": {
"runId": "run_111",
"status": "queued",
"statusUrl": "/api/v1/projects/proj_abc/chat/runs/run_111"
}
}
wait=true)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" }
]
}
}
}
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
Related Skills
mobile-app-ui-design
54ceorkm/mobile-app-ui-design
Frontend2 shared tagsfrontend-design
655anthropics/claude-code
Frontendtag: designantigravity-design-expert
205sickn33/antigravity-awesome-skills
Frontendtag: designhigh-end-visual-design
190leonxlnx/taste-skill
Frontendtag: designinterior-design-expert
143erichowens/some_claude_skills
Frontendtag: designtui-design
104hyperb1iss/hyperskills
Frontendtag: designReviews
4.5★★★★★59 reviews- OOmar Brown★★★★★Dec 24, 2024
Useful defaults in sleek-design-mobile-apps — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- MMin Diallo★★★★★Dec 16, 2024
We added sleek-design-mobile-apps from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- JJin Lopez★★★★★Dec 12, 2024
sleek-design-mobile-apps reduced setup friction for our internal harness; good balance of opinion and flexibility.
- SShikha Mishra★★★★★Dec 4, 2024
Solid pick for teams standardizing on skills: sleek-design-mobile-apps is focused, and the summary matches what you get after install.
- YYash Thakker★★★★★Nov 23, 2024
We added sleek-design-mobile-apps from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- KKaira Sethi★★★★★Nov 15, 2024
Registry listing for sleek-design-mobile-apps matched our evaluation — installs cleanly and behaves as described in the markdown.
- JJames Menon★★★★★Nov 11, 2024
Keeps context tight: sleek-design-mobile-apps is the kind of skill you can hand to a new teammate without a long onboarding doc.
- HHana Torres★★★★★Nov 7, 2024
Solid pick for teams standardizing on skills: sleek-design-mobile-apps is focused, and the summary matches what you get after install.
- KKaira Reddy★★★★★Nov 3, 2024
I recommend sleek-design-mobile-apps for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- SSoo Ghosh★★★★★Oct 26, 2024
sleek-design-mobile-apps has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 59
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.