Agent skill · software engineering · jeremylongshore
miro-local-dev-loop
Build repository-side scaffolding for a repeatable Miro development loop with isolated apps, fixture boards, contract tests, cleanup, and explicit operator commands. Use when developing Miro integrations locally. Trigger with \"start Miro dev loop\".
Why this skill is useful
Provides specific configuration patterns and scripts for setting up a local development environment with Miro's REST API v2 that the AI wouldn't reliably generate on its own.
What it needs
Requires ngrok, node installed locally. Requires miro account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Miro Local Development Loop Overview Shorten feedback cycles without turning a real collaboration board into a test fixture. Separate configuration, deterministic fixtures, and destructive cleanup; use the evidence produced here to make the next decision explicit and reviewable. Prerequisites A non-production Miro app and Developer team A dedicated test board with an accountable owner Local configuration names, fixture schema, and cleanup policy Tool Discipline Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution. Current Contract Web SDK code runs only while its Miro app context is loaded on a board. REST OAuth and Web SDK authorization are separate; hybrid apps must configure both flows. Board operations are asynchronous and can take time to synchronize. REST test traffic consumes the same per-user/per-application credit budget as other callers. Authentication For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content. Instructions 1. Map the feature to REST, Web SDK, or a deliberate hybrid before writing code. 2. Load configuration by environment and assert that production app, team, and board IDs are absent. 3. Create deterministic fixture items with a run marker on the dedicated test board. 4. Run unit tests with schema-faithful fixtures, then one bounded live contract test. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/miro-local-dev-loop