| name | decent-app |
| description | Use when touching the Flutter app, its REST/WebSocket API, profiles, shots, simulated devices, or real BLE/USB hardware via an Android tablet or desktop, or whenever exercising a code change against a running Decent instance. Covers the dev loop (sb-dev start/reload/stop in simulate or real-hardware mode), REST calls via curl, WebSocket streams via websocat, and smoke-test verification. |
Decent — agent skill
This skill covers driving a running Decent Flutter app from the shell — simulate mode by default, real hardware via --real (+ --adb-forward for Android). It exposes REST via curl, WebSocket via websocat, and lifecycle (start, stop, reload, logs) via scripts/sb-dev.sh. Written for any agent that can read markdown and execute shell commands — Claude Code, Cursor, Codex, Windsurf, humans — and deliberately avoids agent-specific mechanisms like MCP tools or slash commands.
The skill lives under .agents/skills/decent-app/ following the agentskills.io cross-client convention. Any compliant client will auto-discover it. Claude Code also loads it via a forwarder at .claude/skills/decent-app/SKILL.md.
Routing
| Task | File |
|---|
| Start/stop/reload the app | lifecycle.md |
| Call REST endpoints, add endpoints | rest.md |
| Read/write WebSocket streams | websocket.md |
| Work with MockDe1 / MockScale | simulated-devices.md |
| Smoke-test a code change | verification.md |
| End-to-end regression recipes | scenarios/ |
All files above are siblings of this SKILL.md under .agents/skills/decent-app/. Relative paths in the sub-files resolve against that directory.
Authoritative sources
Always read the spec before making API calls. Never guess paths or shapes — the specs are the ground truth and stay in sync with the code.
assets/api/rest_v1.yml — OpenAPI 3.0 spec. Canonical REST endpoint reference.assets/api/websocket_v1.yml — AsyncAPI 3.0 spec. Canonical WebSocket channels and message shapes.scripts/sb-dev.sh — lifecycle helper. The entry point for driving a running dev instance.CLAUDE.md and AGENTS.md at the repo root — project-wide conventions, architecture, and workflow rules.
Prerequisites
Hard dependencies on PATH:
bashcurljqwebsocat (or wscat fallback — see websocket.md)fluttermkfifo (POSIX — macOS and Linux only; Windows contributors run flutter run directly, see lifecycle.md)
Quick start
Simulate mode (default — no hardware needed):
scripts/sb-dev.sh start --connect-machine MockDe1
curl -sf http://localhost:8080/api/v1/devices | jq .
scripts/sb-dev.sh stop
Real hardware on an Android tablet (adb serial from flutter devices):
scripts/sb-dev.sh start \
--platform 8734SCCFAC00000747 --real --adb-forward \
--connect-machine DE1
curl -sf http://localhost:8080/api/v1/devices | jq .
scripts/sb-dev.sh stop
From here, pick the file in the routing table that matches your task.
Rule of thumb
If you're about to guess an endpoint path, payload shape, or WebSocket channel — stop and read the relevant spec first. If you're about to run flutter run by hand, use scripts/sb-dev.sh start instead.
