#Claude Code
Explore public prompts for Claude Code. Narrow the topic by medium or change the order.
Showing 25–38 of 38 · Page 2 / 2
Claude Code Slash Command Designer: One-Click Custom /commands
Turns the checklist or multi-step process you re-paste every time into a custom slash command (.claude/commands/<name>.md, or the newer .claude/skills), with correct frontmatter, $ARGUMENTS parameters, live context pre-injected via `!cmd` (git diff, PR content), and permissions scoped down with allowed-tools.
Claude Code Hooks Builder: Auto Format/Lint/Tests After Every Edit
Uses hooks in .claude/settings.json to automatically run formatting, linting, type-checking, or tests at specific Claude Code lifecycle events (PostToolUse after an edit, PreToolUse before running a command, Stop when wrapping up)—producing correct JSON config plus an executable hook script, with exit code 2 hard-blocking dangerous actions.
Claude Code Skill Factory: Turn Repetitive Workflows Into SKILL.md
Has Claude Code interview you about a repetitive manual process, then produce a fully-structured Agent Skill (SKILL.md) covering name/description/trigger conditions/step-by-step instructions/acceptance criteria/supporting references, and verify it can be triggered automatically as well as invoked via a /slash command.
Claude Code + MCP: Connect External Tools to Your Dev Agent Safely
Has Claude Code help you connect an MCP server (a database, Notion, GitHub, your own API...), choosing the right transport and scope, using .mcp.json or claude mcp add, handling secrets and OAuth securely, and finally demonstrating how mcp__server__tool tools and @resource pull external data into your workflow.
Claude Code Subagent Fan-Out: Splitting Big Tasks Into Parallel Subagents
Has Claude Code break a large task into several independent, parallel subagents (each with its own context, restricted tools, and an assignable model), planning how to fan the work out, defining each subagent's responsibility boundaries and reporting format, and producing reusable .claude/agents subagent definition files when needed.
Claude Code Plan-First: Force a Reviewable Plan Before Touching Any Code
Applies the spirit of Plan Mode so Claude Code hands over a structured plan (files affected, steps, risks, acceptance criteria) before touching any file—you review, correct, and approve it before execution begins. Prevents the AI from charging ahead and writing a pile of things you didn't want.
Claude Code TDD Loop: Red, Green, Refactor Done Right
Forces Claude Code through a strict red→green→refactor cycle: for every behavior, first write a test that fails (red) and actually run it to prove the failure, then write the minimal implementation that just makes it pass (green), and finally refactor under the safety of the passing tests. Cures the AI's old habit of jumping straight to the happy path, skipping edge cases, and faking test coverage.
Claude Code Bug-Fix Loop: Reproduce, Isolate, Fix, Verify
Corrects Claude Code's tendency to 'see an error and start randomly editing' into a disciplined 4-step debugging process: reliably reproduce the bug first, isolate the true root cause (not just the symptom) through minimization, write a regression test that fails, apply the smallest possible fix, then run the full test suite to prove it's fixed without breaking anything else.
Codex Rigorous Diff Reviewer: Correctness, Simplification, and Security in Three Tracks
Has Codex do a disciplined code review of your git diff across three tracks (correctness bugs / simplification-and-reuse / security), listing each finding with a confidence level and a pastable fix, and explicitly instructed to say so when nothing's wrong instead of manufacturing complaints.
Codex Bug-Fix Closed Loop: Reproduce First, Fix Second, With Rerunnable Verification
Forces Codex through a closed loop — write a failing test that reproduces the bug, find the root cause, make the minimal fix, watch that same test go from red to green, then run the full test suite to confirm no regressions — eliminating both 'fixed it without verifying' and 'changed a bunch of unrelated stuff along the way.'
Codex Characterization Tests for Legacy Code: Lock In Current Behavior, Target Edge Cases, Zero Behavior Changes
Has Codex write characterization tests for untested legacy code: it first reads and documents what the code 'actually does right now' (bugs included), systematically covers the happy path plus edge cases and error paths, and is strictly forbidden from modifying the code under test.
Migrating from Cursor to Claude Code / Codex: An Inventory-and-Kickoff Prompt
Has the agent automatically inventory your Cursor project (.cursorrules, .cursor/rules, .cursor/mcp.json), produce a step-by-step migration plan, and generate the corresponding CLAUDE.md or AGENTS.md, slash commands, and MCP config — so you're not stuck 'dumber than Cursor' on day one.
AI Agent Definition-of-Done Self-Check Spec
A Definition of Done template you can paste into any coding agent, turning 'what counts as done' into a checklist the agent must self-verify item by item: behavior meets acceptance criteria, tests/lint/typecheck/build all pass (or it states why they didn't run), risky changes come with a rollback plan, and a final 'verification story' is delivered. Puts an end to agents claiming 'done' while everything is actually broken.
Safe Multi-File Refactoring: Map Blast Radius, Then Batch and Verify
A large-refactor playbook for agents: first do a read-only survey of the 'blast radius' — which files, call sites, and tests are affected — then split the change into small batches, each preserving behavior, each run through its own tests, each its own atomic commit. Puts an end to 'change 40 files at once, then the build breaks and no one knows where to start fixing it.'