Prompts tagged "Claude Code" in the PromptCraft library.
Teaches Claude Code to take over your recurring monthly Excel copy-paste routine: it interviews you to clarify the process first, runs a small-scale pilot, only automates the full workflow after confirmation, and finally delivers a one-click operating manual that non-engineers can follow.
Installs a focused 'security auditor' subagent into Claude Code that reviews code and architecture file-by-file through an OWASP Top 10 lens as you develop features, classifying vulnerabilities by severity with directly-applicable remediation suggestions.
Installs a senior 'backend architect' subagent into Claude Code that uses contract-first design and domain-driven design to draw service boundaries, design REST/GraphQL/gRPC APIs, and build resilience and observability into the architecture from day one.
Installs a dedicated 'performance engineer' subagent into Claude Code that profiles code you've just written, finds bottlenecks like N+1 queries, memory leaks, and slow APIs, classifies them by impact, and provides before/after optimization recommendations with benchmark estimates.
A PostToolUse hook that makes Claude Code automatically run a formatter (Prettier/Black/gofmt) plus a linter every time it edits or writes a file—permanently removing 'inconsistent formatting' as a code review chore.
A PreToolUse Bash hook that intercepts destructive commands like rm -rf, fork bombs, and curl|sh before the AI executes them—a last line of defense that holds even against --dangerously-skip-permissions.
A Stop hook that fires a desktop notification and plays a sound the moment Claude Code finishes running. You can freely switch to other windows—the AI will call you back when it's done, no need to keep staring at the terminal.
A single npx command generates an information-rich terminal statusline for Claude Code, showing the current directory, Git branch, model, a context-usage progress bar, real-time spend burn rate, and a countdown to usage reset—hooked into live ccusage stats.
After Claude Code removed its built-in output style feature, this uses a SessionStart hook to automatically inject a custom response style (tone / format / rules) into every session, with a local marketplace for managing, activating, and applying multiple styles.
Rewrites awesome-cursorrules' Next.js App Router standard into an AGENTS.md/CLAUDE.md you can drop straight into your project root, so Claude Code, Codex, and Cursor automatically follow Server-Components-first, file-based routing, TypeScript, and performance conventions when writing Next.js.
Rewrites awesome-cursorrules' FastAPI production architecture standard into an AGENTS.md/CLAUDE.md that enforces Router→Service→Repository layering, thin handlers, an anti-corruption layer, and idempotency — so AI automatically rejects anti-patterns when writing Python backends.
Rewrites awesome-cursorrules' Go backend scalability standard into an AGENTS.md/CLAUDE.md covering idiomatic error handling, context propagation, interface abstraction, concurrency, and observability — so AI follows standard conventions and trade-off analysis when writing Go services.
Anthropic's official skill-creator: a meta-skill that "asks you clarifying questions, produces a SKILL.md, runs evals, refines the trigger description, and packages everything into a .skill file." It teaches you to build reusable Claude skills using a standardized directory structure and progressive disclosure.
Anthropic's official mcp-builder: a four-phase workflow (research & planning → implementation → review & testing → writing evals) for wrapping your API or service into a high-quality MCP server. Covers both Python (FastMCP) and TypeScript (MCP SDK), with emphasis on tool naming, input/output schemas, error messages that point toward a fix, and evaluating with real-world tasks.
Anthropic's official algorithmic-art skill: write an 'algorithmic philosophy' first, then turn it into an interactive HTML piece with p5.js. The core is Art Blocks-style seeded randomness (same seed = same image), paired with tunable parameters and seed navigation, letting you systematically explore generative art techniques like flow fields and particle systems instead of randomly flailing.
The AGENTS.md file from the official agents.md standard project itself, demonstrating what a 'minimal but complete' agent rules file looks like — telling AI to use the dev server instead of building during development, restart after dependency changes, and which commands run lint/test/build — with a directly reusable template.
GitHub's official open-source tool for Spec-Driven Development. Using /speckit.specify → /plan → /tasks → /implement, it turns a vague requirement into an executable specification end to end, then has the AI generate code from that spec — fixing the unpredictability of 'vibe coding.'
Uses two Markdown templates (create-prd.md and generate-tasks.md) to turn 'dumping a pile of requirements on AI' into a controlled process: first generate a PRD, break it into a checkable task list, then complete one subtask at a time — pausing after each for your go-ahead before continuing.
Installs the flagship code-reviewer subagent from wshobson/agents (36k stars, MIT license) into Claude Code, giving you an Opus-powered senior reviewer specialized in security, performance, and maintainability that automatically takes over review after every commit.
Uses VoltAgent/awesome-claude-code-subagents (154+ subagents, 10 categories, MIT license) as a curated directory for picking the right subagent and installing it into Claude Code's .claude/agents/ using the standard YAML format.
Distills the open-source SuperClaude framework's /sc: command system and cognitive-persona mechanism into a ready-to-use workflow prompt, upgrading Claude Code from "one question, one answer" into a structured development process covering everything from brainstorming to implementation, testing, documentation, and version control.
A curated, ready-to-use version of OneRedOak's design-review workflow: using Playwright MCP in a real browser environment, it automatically audits frontend changes across 7 stages (interaction, responsiveness, visuals, accessibility, robustness, code health) and reports findings graded Blocker/High/Medium/Nitpick.
Curates three core project-rules from steipete/agent-rules into a single rule pack usable directly as a slash command: semantic commits (12 types plus emoji, with automatic splitting into atomic commits), a 6-persona professional PR review, and 5 Whys root-cause analysis.
Has Claude Code scan your repo and produce a tight, verifiable CLAUDE.md project memory file under 200 lines—covering build/test/lint commands, directory structure, conventions, and prohibitions—while routing anything that doesn't belong there into skills or path-scoped rules instead.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.'
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.
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.
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.
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.'