Large Markdown projects become hard to navigate when headings change. This skill helps generate, preview, and update tables of contents across files.

Long AI tasks lose context and coordination across sessions. This skill uses GitHub Issues, checkpoints, and worktrees to preserve state and guide phase transitions.

Teams need consistent handoffs between development, testing, review, and merge phases. This skill validates allowed transitions, delegates thread changes, and updates workflow memory.

Teams lose context when AI work moves across GitHub issues and background tasks. This skill helps Claude, Codex, and Claude Code track the active issue, manage transcription state, and create review threads.

Teams need a quick view of GitHub Elements workflow health without changing issue state. This skill produces a read-only status overview for active threads, phases, and warnings.

Feature work can drift when requirements are missing or stale. This skill defines requirement files, versioning, issue links, and backup steps.

GitHub Elements teams need structured visibility into workflow health, metrics, and epic progress. This skill produces detailed reports for metrics, compliance, and epic analysis.

Teams lose time when requirements are vague or forced into one template. This skill guides Claude, Codex, and Claude Code to create clear, testable requirements for each domain.

Starting issue work requires validation, labels, comments, and local setup. This skill coordinates those steps for a specific GitHub issue number.

Long development sessions can lose state across tools, agents, and handoffs. This skill records a structured checkpoint in the active GitHub Issue thread and GHE_REPORTS.

Teams need changelogs that reflect code, requirements, and design changes. This skill guides Claude, Codex, and Claude Code through git-based changelog updates.

Model safety teams need reproducible evidence about when prefills make exploit behavior more likely. This skill guides Claude, Codex, and Claude Code through trajectory and logprob analysis.

Teams often add brittle tests that mirror implementation details instead of user behavior. This skill guides Claude, Codex, and Claude Code to write focused tests for critical workflows.

Input validation often becomes inconsistent across forms, APIs, and business rules. This skill guides Claude, Codex, and Claude Code toward secure validation patterns.

Teams can introduce conflicting frameworks, services, or build tools when stack decisions are scattered. This skill guides Claude, Codex, and Claude Code to follow documented technology standards.

Inconsistent error handling can hide failures and confuse users. This skill guides Claude, Codex, and Claude Code toward clear exceptions, validation, cleanup, and recovery paths.

Inconsistent code slows reviews and makes maintenance harder. This skill gives Claude, Codex, and Claude Code clear rules for readable, consistent code.

Responsive interfaces often fail across phones, tablets, and desktops. This skill gives Claude, Codex, and Claude Code focused guidance for mobile-first layouts, breakpoints, and touch-friendly UI.

Frontend styling often drifts across files, components, and frameworks. This skill guides Claude, Codex, and Claude Code toward consistent CSS methods and design tokens.

Frontend teams need consistent component structure across frameworks. This skill guides Claude, Codex, and Claude Code to design focused, reusable UI components.