Best Prompts Directory

hub

Best Prompts Directory

Curated prompts for every Claude Code job: code review, refactor, audit, plan, ship. Copy, paste, adapt.

The Directory

40 prompts that actually work.

Searchable. Copy-paste ready. Every prompt tested in real production sessions with Claude Code. 8 categories, from engineering to business. Filter by difficulty, search by keyword, copy in one click.

Engineering

Interview-driven spec generation

When to use: Starting any non-trivial feature. Forces you to think through requirements before writing code.

Multi-layer code review

When to use: Before merging any PR. Catches the three most common production issues in one pass.

Ruthless senior engineer review

When to use: When you want unfiltered, prioritized feedback on a critical file.

Parallel hypothesis debugging with agents

When to use: When you have a tricky bug and want to test multiple theories simultaneously.

Incremental API migration

When to use: Migrating deprecated APIs safely. The one-by-one approach catches regressions early.

N+1 query detector

When to use: Performance audit. N+1 queries are the most common hidden performance killer.

Feature spec with rollback plan

When to use: Before building any feature that touches the database or has external dependencies.

Auth flow walkthrough with ASCII diagram

When to use: Onboarding to a new codebase or documenting an existing flow for the team.

Security

Hardcoded secrets scanner

When to use: Before any public release, after onboarding new developers, or during periodic audits.

Auth vulnerability deep scan

When to use: When auth is business-critical. These three are the most exploited auth vulnerabilities.

Simulated penetration test

When to use: Before launching a public API. Gets you attacker-mindset analysis without hiring a pen tester.

SQL injection audit

When to use: Any project with raw SQL. Parameterized queries are the only reliable defense against SQLi.

Gitignore completeness check

When to use: Project setup, before first commit, or after adding new tools that create config files.

PR security checklist generator

When to use: Every PR that touches backend logic. Paste the checklist into the PR description.

Context Management

Structured context gathering

When to use: Start of any complex session. Prevents Claude from guessing and making wrong assumptions.

Session summary and context reset

When to use: When your session is getting long and Claude starts losing track of earlier decisions.

Focused context compaction

When to use: When context is bloated and you need Claude to focus on one specific area.

Spec-first session split

When to use: Large features. Splitting spec and implementation into separate sessions keeps context clean.

CLAUDE.md knowledge extraction

When to use: End of productive sessions. Captures institutional knowledge so future sessions start smarter.

Swarms & Agents

Parallel client status dashboard

When to use: Weekly client review. Gets status on all clients simultaneously instead of reading files one by one.

Parallel security scan across routes

When to use: Full codebase security audit. Parallelizes what would otherwise be a serial, hours-long review.

Writer-critic loop for quality

When to use: High-stakes features where quality matters more than speed. Simulates a real code review cycle.

End-to-end feature build with parallel agents

When to use: Building a complete feature fast. Each layer gets focused attention from a dedicated agent.

Debugging

Slow-down diagnostic interview

When to use: When you are stuck. Prevents Claude from jumping to the first solution and missing the real issue.

Five competing hypotheses

When to use: Intermittent or hard-to-reproduce bugs. Gives you a structured investigation plan.

Non-determinism source finder

When to use: Flaky tests. Common sources: time, random, network, shared state, async race conditions.

Function deep-dive with edge case testing

When to use: Understanding unfamiliar code and immediately hardening it with tests.

Workflow & Automation

Inbox processing automation

When to use: Daily inbox zero routine. Turns a 30-minute manual task into a 2-minute AI task.

Stale PR monitor

When to use: Team management. Catches PRs that are silently stalling before they become blockers.

Pre-commit safety gate

When to use: Any production project. Prevents the two most common commit mistakes: broken tests and leaked secrets.

Deployment watchdog

When to use: Post-deployment monitoring. Catches issues before users report them.

Content & Writing

Voice-matched content generation

When to use: Any content creation. The @ reference loads your actual writing style so output matches your voice.

Raw notes to LinkedIn post

When to use: When you have ideas but not time to craft them. Converts rough thoughts into publish-ready posts.

Multi-angle content from one win

When to use: Maximizing content from a single win. One result can fuel a week of different posts.

30-day content calendar

When to use: Monthly content planning. Gets you from zero to a full month of planned content in one session.

Business & Sales

Client status deep-read

When to use: Before any client interaction. Surfaces forgotten tasks and keeps nothing from slipping through.

Client call preparation kit

When to use: 15 minutes before any client call. Shows up prepared without spending an hour re-reading files.

Discovery-to-proposal generator

When to use: After a discovery call. Turns raw notes into a professional proposal in minutes.

Prospect ICP scoring and outreach

When to use: Before cold outreach. Personalized pain points convert 3-5x better than generic messages.

Win-to-case-study extractor

When to use: After every successful project. Case studies are the highest-converting sales asset.

Pro Tips

How to write your own power prompts

Be specific about role

Give Claude a persona with clear expertise and temperament. A paranoid security auditor reviews differently than a friendly code mentor.

State the output format

Tell Claude exactly what structure you want back. JSON, bullet list, markdown file, ASCII diagram. Never leave it ambiguous.

Add constraints

Constraints prevent Claude from going off track. "Ask one question at a time" and "Don't jump to solutions" are two of the most powerful.

Use the Interview Pattern

For complex tasks, don't dump requirements. Tell Claude to interview you. This surfaces edge cases you forgot and produces better specs.

Tell Claude what NOT to do

Negative constraints are as important as positive ones. Prevents over-engineering, fake enthusiasm, and vague suggestions.

Want this running in your stack?

ManasFlow builds AI automation systems for production teams.

Second Brain Structure: PARA Done Right

Resources Hub: Everything in One Place