Run any Skill in Manus with one click

api-driven-app

Stars0

Forks0

UpdatedJuly 6, 2026 at 22:20

Architecture and implementation for API-driven desktop and web applications. Use when the app depends heavily on remote APIs, model/API gateways, auth, request orchestration, server state, offline/slow-network handling, streaming, uploads/downloads, rate limits, and API-backed UI workflows.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

PAISHU-AI

PAISHU-AI/guanghechaojizhiti

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	api-driven-app
description	Architecture and implementation for API-driven desktop and web applications. Use when the app depends heavily on remote APIs, model/API gateways, auth, request orchestration, server state, offline/slow-network handling, streaming, uploads/downloads, rate limits, and API-backed UI workflows.

API Driven App

Workflow

Map the app into UI state, server state, local persisted state, auth state, and transient operation state.
Define API client boundaries: base URL, auth, timeout, retry, cancellation, error normalization.
Design server-state strategy: cache keys, invalidation, stale data, optimistic updates, pagination, polling/streaming.
Handle failure modes: offline, timeout, 401, 403, 404, 409, 422, 429, 5xx, partial data, and API schema drift.
Make UI states explicit for loading, refreshing, saving, queued, failed, retrying, empty, and permission-limited views.

Architecture Rules

Do not call raw endpoints from scattered components.
Keep API DTOs at the boundary; map to view models when UI needs differ.
Treat auth expiry and rate limits as first-class UX states.
Use idempotency keys for repeated mutating operations when supported.
Separate local drafts from committed server state.
Preserve user work during network failure when feasible.

Desktop-Specific Checks

Handle proxy, certificate, OS network changes, and app sleep/wake.
Store credentials in secure OS storage when possible.
Avoid blocking the UI thread on long requests or local processing.

Web-Specific Checks

Keep shareable state in the URL when useful.
Avoid leaking secrets into frontend bundles.
Consider CORS, cookies, CSRF, and SameSite behavior.

Output

State data/state model, API boundary, failure states, caching strategy, and verification cases.

Bundled Resources

references/api-client-blueprint.md: desktop/web API-driven architecture, API client contract, app error shape, state ownership.
assets/api-client.ts: minimal typed API client seed with timeout, auth header, JSON errors, and normalized AppError.

More from this repository

same repository

backend-design

PAISHU-AI/guanghechaojizhiti

Design backend architecture, service boundaries, domain models, data flow, async jobs, reliability strategy, error handling, observability, and deployment shape. Use before implementing significant backend systems, APIs, services, queues, integrations, or refactors.

2026-07-060

ui-polish-pro

PAISHU-AI/guanghechaojizhiti

Professional UI beautification and product visual refinement for desktop and web apps. Use when the user asks to make an interface more beautiful, premium, polished, modern, professional, refined, or visually consistent, especially for API-driven tools, dashboards, SaaS, admin panels, and desktop software. Incorporates high-taste anti-generic UI rules.

2026-07-060

tauri-pro

PAISHU-AI/guanghechaojizhiti

Professional Tauri desktop application development with Rust commands, webview frontend, permissions, IPC, filesystem access, secure storage, sidecars, updater, packaging, and cross-platform desktop behavior. Use for Tauri apps, Tauri + React/Vue/Svelte, Rust backend commands, desktop APIs, tauri.conf, capabilities, and build/release issues.

2026-07-060

database-pro

PAISHU-AI/guanghechaojizhiti

Professional database design, migration, transaction, indexing, query optimization, and data integrity skill for SQL databases and ORMs. Use for schema design, migrations, indexes, constraints, query performance, data modeling, consistency, backfills, and database review across PostgreSQL, MySQL, SQLite, Prisma, Drizzle, TypeORM, SQLAlchemy, and similar tools.

2026-07-060

frontend-design-pro

PAISHU-AI/guanghechaojizhiti

Professional frontend design and implementation planning for web apps, dashboards, tools, admin panels, API-driven screens, and desktop-like UI. Use when designing or improving frontend screens before or during implementation, especially when component hierarchy, application layout, data states, and usability need to be explicit.

2026-07-060

anthropic-frontend-design

PAISHU-AI/guanghechaojizhiti

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

2026-07-060

name	api-driven-app
description	Architecture and implementation for API-driven desktop and web applications. Use when the app depends heavily on remote APIs, model/API gateways, auth, request orchestration, server state, offline/slow-network handling, streaming, uploads/downloads, rate limits, and API-backed UI workflows.

API Driven App

Workflow

Map the app into UI state, server state, local persisted state, auth state, and transient operation state.
Define API client boundaries: base URL, auth, timeout, retry, cancellation, error normalization.
Design server-state strategy: cache keys, invalidation, stale data, optimistic updates, pagination, polling/streaming.
Handle failure modes: offline, timeout, 401, 403, 404, 409, 422, 429, 5xx, partial data, and API schema drift.
Make UI states explicit for loading, refreshing, saving, queued, failed, retrying, empty, and permission-limited views.

Architecture Rules

Do not call raw endpoints from scattered components.
Keep API DTOs at the boundary; map to view models when UI needs differ.
Treat auth expiry and rate limits as first-class UX states.
Use idempotency keys for repeated mutating operations when supported.
Separate local drafts from committed server state.
Preserve user work during network failure when feasible.

Desktop-Specific Checks

Handle proxy, certificate, OS network changes, and app sleep/wake.
Store credentials in secure OS storage when possible.
Avoid blocking the UI thread on long requests or local processing.

Web-Specific Checks

Keep shareable state in the URL when useful.
Avoid leaking secrets into frontend bundles.
Consider CORS, cookies, CSRF, and SameSite behavior.

Output

State data/state model, API boundary, failure states, caching strategy, and verification cases.

Bundled Resources

references/api-client-blueprint.md: desktop/web API-driven architecture, API client contract, app error shape, state ownership.
assets/api-client.ts: minimal typed API client seed with timeout, auth header, JSON errors, and normalized AppError.