All authors
Claude Skills by stuartshields
github.com/stuartshields16 skills0 installs16 views
- Audit Vs Fix DisciplineUse when the user asks to audit, review, investigate, check, scan, "look at", or "find issues in" code — anything that sounds like a diagnostic request without an explicit fix authorization. Enforces findings-only output with severity tiering, forbids in-place fixes during audit, and blocks the dismissal-as-"pre-existing" rationalisation.Votes: 0GitHub stars: 2
- Block JourneyDiscover all files for a block or component, trace the editorial and front-end user journeys, and write a journey document to docs/journeys/.Votes: 0GitHub stars: 2
- Clean WorktreesRemove stale agent worktree directories and their orphaned branches. Run after parallel agent work or when .claude/worktrees/ accumulates cruft.Votes: 0GitHub stars: 2
- Debug RulesDiagnose which rules loaded, which didn't, and why. Reads the InstructionsLoaded audit log and compares against expected rules.Votes: 0GitHub stars: 2
- Debug WpStarts a structured interview to diagnose WordPress issues, then proposes a ranked list of solutions.Votes: 0GitHub stars: 2
- DebuggingStructured debugging protocol. Use when investigating a bug, failing test, regression, unexpected behavior, or any scenario where code is not doing what it should. Trigger phrases include "broken", "not working", "bug", "error", "it worked before", "still broken", "why is this failing", "trace", or "/trace".Votes: 0GitHub stars: 2
- FigmaFigma-to-code workflow using MCP tools. Fetches design context, screenshots, variables, and Code Connect mappings before implementation.Votes: 0GitHub stars: 2
- HandoffWrite or update a handoff document so the next agent with fresh context can continue this work.Votes: 0GitHub stars: 2
- PlaywrightPlaywright MCP browser automation workflow. Snapshot-first approach for page interaction, visual verification, form filling, and debugging.Votes: 0GitHub stars: 2
- Qa CheckAuto-detects the project's tech stack, then audits for Accessibility, Performance, and Code Quality. Works across WordPress/PHP, Python, Node/JS, and static web projects.Votes: 0GitHub stars: 2
- Review MemoryReview auto-memory for the current project. Shows accumulated learnings, identifies noise, and helps promote permanent patterns to CLAUDE.md, rules, or skills.Votes: 0GitHub stars: 2
- Swift Concurrency ReviewUse when reviewing Swift 5.5+ code containing `await`, `actor`, `Task { }`, `@MainActor`, `@unchecked Sendable`, cancellable timer/deadline handles, or long-lived `for await` AsyncStream consumers — especially diffs extending existing actors with new methods. Catches post-`await` state-overwrite races, TOCTOU around Task spawn, cancellation-not-honoured, terminal-state clobber, and consumer-Task-ownership bugs that hang Swift Testing at exit.Votes: 0GitHub stars: 2
- Test PlanGenerate a user-facing test checklist from git diff, or execute an existing test plan via Playwright. Two modes: generate (default) creates the plan, execute runs it in the browser.Votes: 0GitHub stars: 2
- Tool UsageRecovery protocol for tool failures and search budgets. Use when Edit fails repeatedly on the same target, when hooks may have modified file contents between operations, or when WebSearch/WebFetch is not converging on an answer.Votes: 0GitHub stars: 2
- Vibe UserOpen an app in Playwright and explore it as a real user with no prior knowledge. Report UX findings per page, test core flows, and suggest improvements.Votes: 0GitHub stars: 2
- Module Depth ReviewUse when reviewing whether module boundaries earn their keep — finding shallow modules that should be consolidated into deep ones. Triggers on phrases like "is this over-modularised?", "should these be one module?", "too many small files doing related work", "interface feels as complex as implementation", "review the architecture of X", or when a folder has many tiny files that mostly call each other. Read-only audit; pairs with audit-vs-fix-discipline. Not a substitute for `simplify` (which ...Votes: 0GitHub stars: 2