What problem does it solve? Adding a new issue-thread interaction kind to the Todero codebase touches four separate layers (shared contract, server service, UI card, and external helpers), and missing any one of them causes broken agent flows, drifted staleness logic, or 400 errors in production. This Skill gives contributors a proven, ordered playbook so nothing is skipped. ## Core Features & Use Cases - Layered implementation plan: Walks through the shared Zod contract, server service and routes, React card components, and CLI/MCP/plugin SDK helpers in the correct order. - Canonical prior art: Points to the checkbox confirmation rollout (commit 4d5322c82, PR #7649) as the reference diff and maps new kinds to the closest existing interaction pattern. - Invariants and anti-patterns: Codifies board-only resolution, company scoping, stale-target expiration, idempotency keys, and review-observed mistakes to avoid. - Use Case: A maintainer needs to add an in-thread approval card with target binding; they follow the checklist to land the shared types first, then wire the service, card, fixtures, Storybook, and agent guidance, and run the focused vitest set before review. ## Quick Start Ask the agent to add a new issue-thread interaction kind to the Todero repo following this skill, starting with the shared contract in packages/shared.
