From coordinator
This skill should be used when detecting repetitive actions, oscillating between approaches, or stalling without progress — the three stuck patterns. Referenced by agent prompts for self-monitoring.
npx claudepluginhub oduffy-delphi/coordinator-claudeThis skill uses the workspace's default tool permissions.
You MUST maintain a mental tally of your recent actions. After each tool call, check against these patterns:
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You MUST maintain a mental tally of your recent actions. After each tool call, check against these patterns:
If you have called the same tool with the same arguments 3+ times and received the same result (or the same error), you are stuck. (Two retries are allowed — the third repetition triggers detection.)
Recovery: Stop retrying. Read the error output carefully. Describe what you expected vs what happened. Try a fundamentally different approach — not a variant of the same approach.
If your last 4+ actions alternate between two patterns (e.g., edit-undo-edit-undo, or read-file-A, read-file-B, read-file-A, read-file-B), you are oscillating.
Recovery: Pick one approach and commit. If you're uncertain which is correct, escalate with BLOCKED rather than oscillating.
If you've written 3+ paragraphs of analysis without making a single tool call, you're stalling.
Recovery: State your plan in one sentence. Execute the first concrete step immediately. Analysis without action is not progress.
After context compaction, check your tasks (TaskList/TaskGet) for "tried and abandoned" notes before attempting any approach. Check both metadata.tried_and_abandoned and task descriptions (legacy format). If a task records that an approach was tried and failed, do not retry it.
Recovery: Read all task metadata and descriptions via TaskGet for notes about failed approaches. Choose a different strategy.
Before beginning work, review any ANTI-REPETITION section in your dispatch prompt. Plan your approach to be fundamentally different from all listed failed approaches. If during execution you realize you are converging on a listed failed approach, STOP.
Recovery: Choose a fundamentally different approach. If no alternative exists, report BLOCKED with Type: Structural — "All known approaches exhausted."