#claude
Explore public prompts for claude. Narrow the topic by medium or change the order.
Showing 1–19 of 19 · Page 1 / 1
Claude Life OS Prime: Turn the Chat Window Into a Productivity Dashboard
Not a chatbot — think Notion AI + Motion + Atomic Habits in one. Tracks habits, goals, energy, and deep work; auto-detects behavioral patterns; flags burnout risk.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.
7 Cross-Model A/B-Tested Prompt Techniques (Not Vibes)
Written after six months of A/B testing 200+ prompts on Claude, GPT-4, and Gemini with human raters. Covers persona + constraint stacking, anti-examples, role-reversal QA, cognitive scaffolds, emotional priming, uncertainty CoT, and steelman-first.
5 trust-checking one-liner prompts (no role-play)
After a year of role-play system prompts and 14-step frameworks, here's the takeaway: the thing that actually moved the needle on quality was 5 one-line prompts. No roles, no markdown, no "you are an expert."
Resume Tailoring for a Specific Job Description
Feed Claude your original resume plus the target job posting, and it rewrites every section of your resume in that company's language — keywords, metrics, and industry terms all aligned — to boost your ATS pass rate.
5 Claude Repeat-Task Templates That Lasted 6+ Months — and the 3 Retention Rules
After 18 months of testing 60 Claude workflows, the retention pattern: annoying but not painful, output has a destination, input under 30 seconds. The 5 templates that survived 6+ months (Friday review / meeting follow-up / client weekly report / Monday briefing / pipeline update).
5 Prompt Engineering Techniques That Actually Move the Needle (XML Beats Markdown by 28%)
Five quantifiable techniques from an AI engineer's hundreds of hours testing across GPT-4, Claude, and Gemini: CoT scaffolding, persona + goal + anti-goal, XML being 28% more accurate than markdown, negative examples outperforming positive ones, and prompt chaining beating the mega-prompt.
Turn Off ChatGPT's Polite Lying — 3 Anti-Sycophancy Instructions
By default, helpful = agreeable = burying the real problem in paragraph four. Three one-line instructions reverse it: problem first, force a recommendation, explicitly forbid softening. The difference between reading and fixing.
A Red Teamer's View: 3 High-Capability Prompt Patterns That Work Across Models
Three patterns shared by the HackAPrompt 2.0 champion: frame the task as an audit, make the abstraction level explicit, and stage the context like production. They work on Claude, GPT, and Gemini alike.
AI Agent Harness Engineering: Separating the LLM from the Deterministic Orchestration Layer
Mitchell Hashimoto's "Agent = Model + Harness" framework. The reason 88% of enterprise AI agents never reach prod isn't the prompt — it's the missing deterministic orchestration layer. Four CS primitives you can't skip: state machine, idempotency, DAG, DLQ.
COMMAND PLANNING MODE: A 9-Section Structured Planning Prompt
No conversation, no suggestions, no attempts — it just turns any situation into a structured execution plan. Fixed 9-block output: Reality / Objective / 4-phase Timeline / Tactics / Threats / Defenses / Contingency / Leverage / Confidence. Same input always yields the same output.
reClaim: Turn a Frontier Model Into a Research Agent With Confidence Scores
Scores every claim on three axes (A: sources / B: counterevidence / C: completeness), plus a 4-tier source hierarchy, adversarial self-poking, and 4 output modes.
A Universal Decision Prompt: Use "What Will You Regret in a Year" to Force a Verdict
Stop picking a role for every decision (financial planner / career coach / relationship coach) — one universal prompt, four steps. The regret line is the core — it forces the model from "it depends" to "actually do this."
CV Writer Ruleset: It Interviews You STAR-Style and Bans "Dynamic Team Player"
The pain of writing a CV isn't the layout — it's listing duties instead of achievements, then having AI pile on and turn you into a "dynamic team player." This ruleset forbids AI from drafting anything until it has your evidence and positioning, and walks you through one question at a time.
Voice Memo → Tomorrow's Priorities (With a Confirmation Round)
Before you log off, ramble into your phone mic for 2 minutes, hand it to Claude, and get back a sorted list: first thing tomorrow morning + ranked to-dos + waiting-on + can-defer. Auto-detects daily vs. weekly mode.
The 60-Second Pre-Send Check: Catch the Message You'll Regret Tomorrow Morning
The author wrote this after 30% of their heated replies made them wince the next day — costing a few deals and a friendship. The trick: don't let AI rewrite it, let it show you what the calm version would look like. Once you see it, you usually can't go back to the original.
Flip Your AI Dev Workflow: Generate the Prompt First, Then the Code (4 Phases)
Instead of telling AI to write code directly, have it translate a vague goal into an executable prompt structure first, then use that structure to drive code generation. Phase 1 Intent → Phase 2 Structuring → Phase 3 Tool-Level → Phase 4 Implementation.
Run an Architecture Review on Your Whole Codebase with Claude
Upload the repo and Claude returns an architectural map, the top 5 fixes to prioritize, and the file paths to back them up.
STAR Interview Answer Bank Generator
Give Claude the target job description plus 5 real work incidents of yours, and it produces 5 STAR-format interview answers you can rehearse the night before the interview.