Coding standards, frameworks, refactoring, and code review (16.5K skills)
Choose a suitable model and role for work in Claude Code or Codex, from a second opinion to focused debugging or delegation. Prepare a scoped handoff and, when requested, execute it once and verify the result.
Have Codex implement a defined work order, then have Claude independently inspect the changes and run verification checks. The workflow records evidence and limitations, bounds correction rounds, and requires updated reviews when later edits change the result.
Find development task files in a repository and review their status and dates. Filter pending, active, or completed work, view counts by status, or export task details as JSON for reporting and other tools.
Develop features by writing failing tests before implementation, starting from a specification, task file, or plain description. Follow existing project conventions, make tests pass with minimal code, then improve the code while preserving passing tests.
Create and review Ralph workflows built from hats, the roles assigned to different stages of work. Explain how events connect those roles, validate routing and completion settings, and refine configuration files for clearer responsibilities.
Turn a rough development idea into a detailed design and step-by-step implementation plan. Guided questions, research notes, and diagrams clarify requirements, while user approval at each stage keeps the planning process aligned with their decisions.
Control interactive terminal apps through tmux, a tool for persistent terminal sessions. Send keystrokes, capture screen output, and manage long-running servers or commands to support application testing and collect evidence for QA reports.
Review a pull request by number or GitHub URL using Ralph's reviewer loop. It checks out changes in a separate working directory, runs tests, examines the diff, and presents a structured report or available intermediate findings.
Reproduce and investigate rendering problems in ralph's terminal interface using a tmux split pane. Capture live output and inspect diagnostic logs while keeping the main pane available for investigation commands.
Investigate Ralph Orchestrator behavior through its official documentation map. Use relevant pages to explain internal mechanisms, assess bug reports, and scope code improvements with source links and checks against the local code.
Implement coding tasks through exploration, planning, testing, and commits. Follow test-driven development, writing failing tests before implementation, while matching existing project conventions and recording requirements, decisions, progress, and build results in separate planning documents.
Turn rough development requests or PDD implementation plans into structured task files. Each task includes technical requirements, dependencies, and acceptance criteria describing the starting conditions, action, and expected result, including unit test requirements.
Operate Ralph runs from startup through recovery and merging. Inspect status, logs, history, and code changes, resume suspended runs, and use diagnostic files to investigate unexpected behavior or problems in the merge queue.
Implement a defined feature in a new project, starting from the requested outcome and acceptance criteria. Run relevant checks, exercise the user journey when runtime access allows, fix issues caused by the change, and report remaining gaps.
Prepare a concise project handoff for another session or coding tool. It records current changes, decisions, blockers, verified check results, and the next task while excluding secrets, unnecessary personal information, and full conversation transcripts.
Create project instructions for AI agents and tool configuration from agreed requirements and technical decisions. Update relevant rules, preserve existing files, and keep task procedures and progress records separate from instructions that are always loaded.
Diagnose reproducible crashes, broken behavior, or failing checks in an existing project. Test specific explanations, make focused fixes, and rerun the original failure and relevant checks while recording evidence, remaining gaps, and recovery information.
Add one clearly scoped feature to an existing app while preserving current behavior and ongoing work. The skill inspects affected code, implements focused changes, runs relevant checks, and reports results, unchecked areas, and recovery information.
Turn agreed requirements into a technical design for an MVP, a minimum viable product. Review the existing project, define component boundaries and deployment needs, and document tradeoffs, constraints, and checks for implementation.
Review code changes against requirements and check results to identify bugs, broken existing behavior, and relevant security risks. Receive actionable findings with file locations, triggers, impacts, and suggested fixes, with verification gaps clearly separated.
Choose a suitable workflow for planning an app, changing an existing product, or fixing a bug. The skill uses project context to identify the next action, limit unnecessary questions, and guide relevant implementation and checks.
Build, debug, and review Workers invoked by Cloudflare Gateway Forward policies. The skill guides request transformations, generated responses, and use of Gateway identity information, with checks for the required entrypoint and how requests continue to their destination.
Build and maintain apps that run isolated Linux environments from Cloudflare Workers using the stable Sandbox SDK. Guide command execution, files, sessions, and deprecated API cleanup while keeping package and container versions aligned.
Build or move Next.js applications to Cloudflare Workers using vinext, which implements Next.js APIs on Vite. This skill guides project setup, compatibility checks, migration, and deployment through the relevant upstream skills and documentation.