AlphaMoatによると、2026-10時点でDesing mobile appsのダウンロード数は17,723、スター数は5で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中1,598位、デザイン・メディアでは1,116件中216位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 1.8万 | 3 | - |
| SkillHub ↗ | 1.7万 | 5 | — |
プラットフォームごとに集計方法と集計時点が異なります。
範囲を絞った API key で一覧・作成、自然言語の依頼、進行確認、画面撮影を行います。各プロジェクトの実行は同時に一つです。新画面は個別と全体、更新は対象画面を示します。指示と参考 URL は Sleek に渡ります。取り消せる最小権限を使い、私的な参考画像を避け、プロジェクト削除前に確認します。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 1.8万 | — | 5 |
| 2026-09 | 1.8万 | — | 5 |
| 2026-08 | 1.7万 | +4.5% | 5 |
| 2026-07 | 1.7万 | +16.2% | 5 |
| 2026-06 | 1.4万 | +7.4% | 5 |
| 2026-05 | 1.3万 | — | 5 |
| 2026-03 | 6337 | — | 3 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
---
name: sleek-design-mobile-apps
description: Use when the user wants to design a mobile app, create screens, build UI, or interact with their Sleek projects. Covers high-level requests ("design an app that does X") and specific ones ("list my projects", "create a new project", "screenshot that screen").
compatibility: Requires SLEEK_API_KEY environment variable. Network access limited to https://sleek.design only.
metadata:
requires-env: SLEEK_API_KEY
allowed-hosts: https://sleek.design
---
# Designing with Sleek
[](https://sleek.design)
## Overview
[sleek.design](https://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
---
## 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+ (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.
---
## Handling high-level requests
When the user says something like "design a fitness tracking app" or "build me a settings screen":
1. **Create a project** if one doesn't exist yet (ask the user for a name, or derive one from the request)
2. **Send a chat message** describing what to build — you can use the user's words directly as `message.text`; Sleek's AI interprets natural language
3. **Follow the screenshot delivery rule** below to show the result
You do not need to decompose the request into screens first. Send the full intent as a single message and let Sleek decide what screens to create.
---
## Screenshot delivery rule
**After every chat run that produces `screen_created` or `screen_updated` operations, always take screenshots and show them to the user.** Never silently complete a chat run without delivering the visuals.
**When screens are created for the first time on a project** (i.e. the run includes `screen_created` operations), deliver:
1. One screenshot per newly created screen (individual `componentIds: [screenId]`)
2. One combined screenshot of all screens in the project (`componentIds: [all screen ids]`)
**When only existing screens are updated**, deliver one screenshot per affected screen.
Use `background: "transparent"` for all screenshots unless the user explicitly requests otherwise.
---
## 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 |
| `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
```http
GET /api/v1/projects?limit=50&offset=0
Authorization: Bearer $SLEEK_API_KEY
```
Response `200`:
```json
{
"data": [
{
"id": "proj_abc",
"name": "My App",
"slug": "my-app",
"createdAt": "2026-01-01T00:00:00Z",
"updatedAt": "..."
}
],
"pagination": { "total": 12, "limit": 50, "offset": 0 }
}
```
#### Create project
```http
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 / Delete project
```http
GET /api/v1/projects/:projectId
DELETE /api/v1/projects/:projectId → 204 No Content
```
---
### Components
#### List components
```http
GET /api/v1/projects/:projectId/components?limit=50&offset=0
Authorization: Bearer $SLEEK_API_KEY
```
Response `200`:
```json
{
"data": [
{
"id": "cmp_xyz",
"name": "Hero Section",
"activeVersion": 3,
"versions": [{ "id": "ver_001", "version": 1, "createdAt": "..." }],
"createdAt": "...",
"updatedAt": "..."
}
],
"pagination": { "total": 5, "limit": 50, "offset": 0 }
}
```
---
### Chat — Send Message
This is the core action: describe what you want in `message.text` and the AI creates or modifies screens.
```http
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; 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.
```json
{
"data": {
"runId": "run_111",
"status": "queued",
"statusUrl": "/api/v1/projects/proj_abc/chat/runs/run_111"
}
}
```
#### Response — sync (`wait=true`)
Blocks up to **300 seconds**. Returns `200` when completed, `202` if timed out.
```json
{
"data": {
"runId": "run_111",
"status": "completed",
"statusUrl": "...",
"result": {
"assistantText": "I added a pricing section with...",
"operations": [
{ "type": "screen_created", "screenId": "scr_xyz", "screenName": "Pricing" },
{ "type": "screen_updated", "screenId": "scr_abc" },
{ "type": "theme_updated" }
]
}
}
}
```
---
### Chat — Poll Run Status
Use this after async send to check progress.
```http
GET /api/v1/projects/:projectId/chat/runs/:runId
Authorization: Bearer $SLEEK_API_KEY
```
Response — same shape as send message `data` object:
```json
{
"data": {
"runId": "run_111",
"status": "queued",
"statusUrl": "..."
}
}
```
When completed successfully, `result` is present:
```json
{
"data": {
"runId": "run_111",
"status": "completed",
"statusUrl": "...",
"result": {
"assistantText": "...",
"operations": [...]
}
}
}
```
When failed, `error` is present:
```json
{
"data": {
"runId": "run_111",
"status": "failed",
"statusUrl": "...",
"error": { "code": "execution_failed", "message": "..." }
}
}
```
**Run status lifecycle**: `queued` → `running` → `completed | failed`
---
### Screenshots
Takes a snapshot of one or more rendered components.
```http
POST /api/v1/screenshots
Authorization: Bearer $SLEEK_API_KEY
Content-Type: application/json
{
"componentIds": ["cmp_xyz", "cmp_abc"],
"projectId": "proj_abc",
"format": "png",
"scale": 2,
"gap": 40,
"padding": 40,
"background": "transparent"
}
```
| Field | Default | Notes |
| ------------ | ------------- | --------------------------------------------------------------------- |
| `format` | `png` | `png` or `webp` |
| `scale` | `2` | 1–3 (device pixel ratio) |
| `gap` | `40` | Pixels between components |
| `padding` | `40` | Uniform padding on all sides |
| `paddingX` | _(optional)_ | Horizontal padding; overrides `padding` for left/right when provided |
| `paddingY` | _(optional)_ | Vertical padding; overrides `padding` for top/bottom when provided |
| `paddingTop` | _(optional)_ | Top padding; overrides `paddingY` when provided |
| `paddingRight` | _(optional)_ | Right padding; overrides `paddingX` when provided |
| `paddingBottom` | _(optional)_ | Bottom padding; overrides `paddingY` when provided |
| `paddingLeft` | _(optional)_ | Left padding; overrides `paddingX` when provided |
| `background` | `transparent` | Any CSS color (hex, named, `transparent`) |
| `showDots` | `false` | Overlay a subtle dot grid on the background |
Padding resolves with a cascade: per-side → axis → uniform. For example, `paddingTop` falls back to `paddingY`, which falls back to `padding`. So `{ "padding": 20, "paddingX": 10, "paddingLeft": 5 }` gives top/bottom 20px, right 10px, left 5px.
When `showDots` is `true`, a dot pattern is drawn over the background color. The dots automatically adapt to the background: dark backgrounds get light dots, light backgrounds get dark dots. This has no effect when `background` is `"transparent"`.
Always use `"background": "transparent"` unless the user explicitly requests a specific background color.
Response: raw binary `image/png` or `image/webp` with `Content-Disposition: attachment`.
---
## Error Shapes
```json
{ "code": "UNAUTHORIZED", "message": "..." }
```
| HTTP | Code | When |
| ---- | ----------------------- | -------------------------------------- |
| 401 | `UNAUTHORIZED` | Missing/invalid/expired API key |
| 403 | `FORBIDDEN` | Valid key, wrong scope or plan |
| 404 | `NOT_FOUND` | Resource doesn't exist |
| 400 | `BAD_REQUEST` | Validation failure |
| 409 | `CONFLICT` | Another run is active for this project |
| 500 | `INTERNAL_SERVER_ERROR` | Server error |
Chat run-level errors (inside `data.error`):
| Code | Meaning |
| ------------------ | -------------------------------- |
| `out_of_credits` | Organization has no credits left |
| `execution_failed` | AI execution error |
---
## Flows
### Flow 1: Create project and generate a UI (async + polling)
```
1. POST /api/v1/projects → get projectId
2. POST /api/v1/projects/:id/chat/messages → get runId (202)
3. Poll GET /api/v1/projects/:id/chat/runs/:runId
until status == "completed" or "failed"
4. Collect screenIds from result.operations
(screen_created and screen_updated entries)
5. Screenshot each affected screen individually
6. If any screen_created: also screenshot all project screens combined
7. Show all screenshots to the user
```
**Polling recommendation**: start at 2s interval, back off to 5s after 10s, give up after 5 minutes.
### Flow 2: Sync mode (simple, blocking)
Best for short tasks or when latency is acceptable.
```
1. POST /api/v1/projects/:id/chat/messages?wait=true
→ blocks up to 300s
→ 200 if completed, 202 if timed out
2. If 202, fall back to Flow 1 polling with the returned runId
3. On completion, screenshot and show affected screens (see screenshot delivery rule)
```
### Flow 3: Edit a specific screen
```
1. GET /api/v1/projects/:id/components → find screenId
2. POST /api/v1/projects/:id/chat/messages
body: { message: { text: "..." }, target: { screenId: "scr_xyz" } }
3. Poll or wait as above
4. Screenshot the updated screen and show it to the user
```
### Flow 4: Idempotent message (safe retries)
Add `idempotency-key` header on the send request. If the network drops and you retry with the same key, the server returns the existing run rather than creating a duplicate. The key must be ≤255 chars.
```
POST /api/v1/projects/:id/chat/messages
idempotency-key: my-unique-request-id-abc123
```
### Flow 5: One run at a time (conflict handling)
Only one active run is allowed per project. If you send a message while one is running, you get `409 CONFLICT`. Wait for the active run to complete before sending the next message.
```
409 response → poll existing run → completed → send next message
```
---
## Pagination
All list endpoints accept `limit` (1–100, default 50) and `offset` (≥0). The response always includes `pagination.total` so you can page through all results.
```http
GET /api/v1/projects?limit=10&offset=20
```
---
## Common Mistakes
| Mistake | Fix |
| --------------------------------------------------- | ------------------------------------------------------------------------------- |
| Sending to `/api/v1` without `Authorization` header | Add `Authorization: Bearer $SLEEK_API_KEY` to every request |
| Using wrong scope | Check key's scopes match the endpoint (e.g. `chats:write` for sending messages) |
| Sending next message before run completes | Poll until `completed`/`failed` before next send |
| Using `wait=true` on long generations | It blocks 300s max; have a fallback to polling for `202` response |
| HTTP URLs in `imageUrls` | Only HTTPS URLs are accepted |
| Assuming `result` is present on `202` | `result` is absent until status is `completed` |
通过同一个AI创作工具完成AI图片、视频、音乐与语音创作,查找公开社交数据,编辑视觉成果,并集中查看和管理生成资产。Beatra 全能创作支持AI图片生成(文生图)、AI视频生成(图生视频)和AI视频编辑,通过AI音乐生成把想法做成歌曲或纯音乐,也可用AI语音生成(文字转语音)、多语言旁白和AI语音克隆完成跨媒介内容;还能查找抖音数据、小红书数据,以及 YouTube、TikTok、Instagram 与 X 上的公开帖子、笔记、评论、账号和趋势,把社交媒体数据用于竞品调研和创作。它是一款面向AI内容创作与多模态内容创作的AI创作套件,用起来就是一个把图片、视频、音乐与语音收在同一处的AI创作助手,适用于社交内容、产品展示、营销素材、课程、播客、短片和跨媒介项目;还能在不同媒介间复用原始素材、已有成果和查到的公开资料,查看制作进度、返回文件、实际用量和积分记录。
用一张人像和一段短脚本或语音,制作有明确讲述内容的数字人口播视频。可使用现成录音,也可以先选择音色,把脚本生成旁白,让画面中的人物随声音完成稳定、自然的口播。适合 AI 主播、虚拟主播视频、数字人讲解、让照片说话、照片说话视频、产品讲解视频、数字人培训视频、公告和社交口播,并在交付后检查人物一致性、声音清晰度、口型同步和动作稳定性。一节课的讲解也能做成课程口播。
ContextWeaveアーキテクチャ図ワンショット生成
将一段活动描述、一张产品照片或品牌参考图,转化为抓人眼球的活动海报、宣传 banner 或社交媒体配图。这款 AI海报设计与制作工具生成图片丰富的海报,在海报排版上搭配清晰视觉层级、按品类匹配的风格和预留文字区域,覆盖活动、音乐节、电影、产品发布和促销场景。你可以把它当作 AI宣传单制作工具来制作促销宣传单,当作活动海报设计工具,当作电影海报生成器,当作音乐节海报设计工具,当作产品发布会海报的 banner设计 AI,或当作平面设计海报工作室。从活动主题出发,用品牌风格参考图变换产品或场景照片,或在已认可草稿上做定向精修,完成可印刷或可分享的成品。
抖音短视频双路径生产体系(单 Skill 版)。Path A[付费·高质量]:策略大脑→(可选:素材混剪/AI高光提取)→脚本优化→AI生图/素材准备→配音渲染(百炼/GPT-SoVITS/CosyVoice/VoxCPM2+剪映/Remotion/ffmpeg/数字人)。Path B[免费·动画风]:采集热点→脚本→edge-tts免费配音+HyperFrames开源渲染→MP4,零云费开箱快。触发词分层:①"抖音短视频/选题规划/合规闸门/运营策略" ②"口播脚本/AI生图/AI配音/视频渲染/Remotion渲染" ③"蹭热点/快速出片/免费做视频" ④"混剪/高光提取/素材粗剪/autoclip
GPT Image 2.5生图是一款 AI 工具,用 GPT-Image-2.5 和 ChatGPT Images 2.5 出一张图。GPT Image 2.5 Studio 支持 gpt-image-2.5-flare 与 gpt-image-2.5-sunburst,可文生图或参考图生图,做中文海报、商品图、信息图和社媒画面。
用 MiniMax H3 这款 AI视频生成器创作高质感 2K AI 视频。从文字创意出发完成文生视频,让静态图片自然动起来,用首尾画面做首尾帧视频的完整转场,也可以结合图片、视频和音频参考,以多模态视频生成塑造统一场景。适合 AI 广告视频、电商产品视频、品牌宣传视频、动态海报、游戏 UI、电影片头和社交短视频创作,形成电影感画面与同步的原生立体声。使用 Beatra 账号即可开始,创作进度与成片集中管理。
输入品牌名称、行业方向或参考图,生成专业 AI Logo、品牌标识和应用图标。这款 AI logo 设计工具从你的品牌简报出发——公司名、行业气质、配色偏好——先探索多个商标设计方向,再用精确品牌色、简洁几何和可缩放构图精修最强概念。制作企业 logo、创业公司标志、字母标、徽章、组合标识和 VI设计中的主标,从网站 favicon 到门头招牌都清晰可辨。从文字描述出发,将已有草图和品牌素材转化为精致标识,或在已认可草稿上做定向精修。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。