Skip to content
Skills Library
Programming · Building & coding

miro-local-dev-loop

/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\".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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\".

Triggers from the description

start Miro dev loop\

Arguments

/miro-local-dev-loop [feature] [test-board-id]
Original author description

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\".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 67 lines, 511 words
SKILL.md preview
---
name: miro-local-dev-loop
description: "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\"."
argument-hint: "[feature] [test-board-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.9.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- saas
- miro
- development
- testing
model: inherit
effort: medium
compatibility: Designed for Claude Code; live work requires an authorized Miro app and redacted evidence
---
# 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. Compare the observed response and rate headers with the recorded contract.
6. Delete only run-marked fixtures after verifying board ID, item IDs, and ownership; retain a redacted receipt.

## Approval Boundaries

Do not expose a local callback publicly, install an app to another team, or delete unmarked board content without explicit approval. Pause when the responsible owner or exact target is uncertain.

## Output

Return environment guards, fixture IDs as hashes, test results, observed contract drift, cleanup count, and leftovers. State what was not inspected or changed so the receipt cannot overclaim coverage.

## Error Handling

| Condition | Response |
|---|---|
| Production identifier detected | Abort before making any request. |
| Fixture create partially fails | Stop, inventory confirmed creations, and clean only those IDs. |
| Asynchronous state is not visible | Retry a bounded read with jitter; do not duplicate the write. |
| Cleanup ownership is uncertain | Leave the item and flag it for a board owner. |

## Examples

The example is a redacted operator receipt; identifiers are hashes or bounded labels, not board content or credentials.

```text
app=dev; board=test-only; fixtures-created=3; contract-tests=8/8; fixtures-removed=3; production-ids=0
```

## Resources

- [Skill-specific official documentation](references/official-docs.md)
- [REST OAuth from Web SDK](https://developers.miro.com/docs/enable-api-authentication-from-sdk-authorization)
- [Web SDK board reference](https://developers.miro.com/docs/websdk-reference-board)
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 1 KB

Versions

The database has no other skills named miro-local-dev-loop.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version ec020f4a30db (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100miro-sdk-patterns
    Choose and implement Miro Node client or raw REST adapter patterns with typed boundaries, pagination, tenant isolation, and explicit operator commands. Use when designing a Miro API adapter. Trigger with \"review Miro SDK pattern\".
  • 100miro-debug-bundle
    Design and implement a repository-side Miro diagnostic-bundle workflow with bounded metadata and automatic redaction. Use when escalating a Miro failure. Trigger with \"build Miro debug bundle\".
  • 95miro-mcp
    This skill teaches how to use Miro MCP tools effectively for creating diagrams, documents, tables, and extracting context from Miro boards. Use when the user asks about Miro capabilities, wants to create content on Miro boards, or needs to work with Miro board data.
  • 100miro-code-spec
    Use when the user wants to extract a Miro board's specs (documents, diagrams, prototypes, tables, frames, images) to local `.miro/specs/` files for AI-assisted planning and implementation — accepts a board URL or single-item URL.
  • 95miro-spec-guide
    Learn how to extract Miro specifications to local files and use them for AI-assisted planning and implementation. Use when working with Miro specs or when user wants to download board content for reference.
  • 100miro-code-review
    Use when the user wants to create a visual code review on a Miro board from a pull/merge request (GitHub, GitLab, or any forge), local uncommitted changes, or a branch comparison — produces a file-changes table, summary/architecture/security docs, and architecture diagrams, then…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.