We show 5 on Instagram. Here's everything.

The full lists

Content prompts, entrepreneur mistakes, checklists, and prompts for developers. Copy them and use them right now.

25 Prompts for Content and Social Media

Claude as your content director.

These prompts work right in claude.ai: no terminal, no installs. Just copy, fill in your details, and hit send.

Copy and hooks

• 01 Here's a post that got 100K views. Break it down: how it opens, how it's built, how it ends. Why did it work?
• 02 Write 5 versions of the opening line for a post about [X]. Different angles: a question, a fact, a provocation, a personal story, a list.
• 03 This text sounds like a robot wrote it. Rewrite it in plain human language, no corporate speak, no fancy words.
• 04 Turn this long text into 3 separate posts. Each one should stand on its own and make sense by itself.
• 05 Write a first-person post about [situation]. Not as a teacher, but as someone who's actually been through it.
• 06 Adapt this post for LinkedIn. Keep the substance, but make the tone slightly more professional.
• 07 Write a series of 7 short posts on one topic. Each works on its own and as part of the series.
• 08 Cut this text in half without losing the main idea.

Carousels and structure

• 09 Come up with a 7-slide carousel structure on [X]. First slide is the hook, the next five deliver the value, the last one tells people what to do.
• 10 Here's a post topic. Which opening slide is stronger: [option A] or [option B]? Explain why.
• 11 Find the main idea in this text and turn it into the first slide of a carousel. 7 words max.
• 12 Write an Instagram caption for the carousel. Under 150 words, ending with a call to comment a specific word.
• 13 Here are 5 posts that performed well in our niche. Find what they have in common. What ties them together?

Content planning

• 14 Put together a one-week content plan for an account in the [X] niche. 5 posts, different formats, one post with a call to action.
• 15 Here's our audience: [description]. Which 3 topics do they need most right now? Explain why.
• 16 Find a contradiction in our niche: a topic where most people believe one thing but reality says another. That's viral post material.
• 17 Write down the 10 questions our audience asks most often. Each one is a ready-made post topic.
• 18 This post flopped. Here are the metrics. Break down why. What should change next time?

Engagement and comment replies

• 19 Write 5 call-to-action options for this post. No pressure and no generic 'follow me'.
• 20 Come up with an end-of-post question people genuinely want to answer, not a token one.
• 21 Here's a comment on our post. Write a reply: human, not bot-like, and don't dodge the question.
• 22 Write a post that sparks discussion in the [X] niche. Not a scandal, an interesting point of view.
• 23 Turn this expert post into a beginner-friendly version. No jargon, with clear examples.
• 24 Write a caption for this image. The first 2 lines are the hook before the cutoff. The rest is the value.
• 25 Here's how we usually write: [example]. Check this new text: does it sound like the same style? What's off?

10 Entrepreneur Mistakes

Every one of these cost us time.

1. Using browser chat instead of Projects

Regular Claude chat is like talking to a stranger. The next day, it has no idea who you are again. Projects is your personal employee with memory. Set it up once, and Claude remembers everything, always.

2. Not writing about-me.md

Without a file with your context, Claude writes in a generic voice. Write down once who you are, who you write for, and how you talk, and every answer comes out in your style.

3. Treating the first answer as final

You can always ask Claude to redo it. 'Good, but make it livelier', 'drop the corporate tone', 'add a specific number': every revision makes the result better. Don't stay silent.

4. Giving vague instructions

'Write a post about our product' is not a task. 'Write an Instagram post, 200 words, for small businesses in Moscow, about our new plan, friendly tone, include a specific number' is a task.

5. Not showing examples of your style

Claude doesn't know how you write until you show it. Paste 2-3 of your posts that did well and say 'this is my style, write like this'. The difference is instant.

6. Believing Claude is always right

Claude can write convincingly but inaccurately. Facts, numbers, legal wording: always double-check. Use Claude for form and structure, but verify the data yourself.

7. Handing all your social media to Claude with none of your own voice

Audiences can tell when content isn't 'alive'. Claude is a tool, not a replacement for your personality. The best combo: Claude writes the draft, you add a personal detail from your own life.

8. Starting every session from scratch

If you find yourself explaining to Claude who you are and what you do every single time, set up Projects with context files. One-time setup = 10 minutes saved per session. Over a month, that's several hours.

9. Asking for 'better' without criteria

'Improve this': Claude doesn't know which direction to go. 'Cut it in half and put a specific number in the first sentence': Claude knows exactly what you need.

10. Not publishing because it's 'not perfect'

Claude helps you make things good fast, not perfect slowly. A good post that's published beats a perfect one you keep editing forever. Publish, watch the reaction, improve.

50 Prompts for Claude Code

One list, five categories.

Claude Code is a terminal tool for developers. If you work with claude.ai in the browser, the content prompts above work without installing anything.

Development: 15 prompts

• 01 Find every place [function] is called. Show me the files and line numbers.
• 02 Write tests for this function, including edge cases, null values, and errors.
• 03 Explain this code as if I'm a senior developer who just joined the project.
• 04 What changes if I delete this function? Show me the blast radius across the whole codebase.
• 05 Find potential N+1 queries in this code.
• 06 Rename [X] everywhere in the codebase, including tests, comments, and imports.
• 07 Check this async code for race conditions.
• 08 Which dependencies can be removed because nothing uses them anymore?
• 09 Do the minimal refactoring needed to make this function testable.
• 10 What's the riskiest line in this file, and why?
• 11 Generate a SQL migration for this schema change.
• 12 Find all the TODOs and FIXMEs in the project and list them with a rough priority.
• 13 Add logging only at the critical points, not everywhere.
• 14 Check that all public functions are documented. What's missing?
• 15 What can be safely cached in this component without changing its behavior?

Architecture: 10 prompts

• 16 Map the dependency graph between modules: who depends on whom.
• 17 What are the trade-offs between approach A and approach B for this task?
• 18 How will this system behave at 100x the current load?
• 19 What are the failure points in this architecture? What breaks first?
• 20 What's the minimal set of changes needed for an MVP of this feature?
• 21 What would need to change for this part to work offline?
• 22 Describe this architecture in 5 sentences for a non-technical founder.
• 23 Where should the boundary between these two services be?
• 24 Which piece of technical debt here is the most expensive long-term?
• 25 Is there a single responsibility violation? Show me exactly where.

Debugging: 10 prompts

• 26 Here's the error log. Find the root cause, not the symptom.
• 27 This test is flaky. Why? How do I make it deterministic?
• 28 Production is slower than staging. What should I check first?
• 29 Here are two pieces of code: one works, one doesn't. Find the difference.
• 30 Add temporary logging to capture the state at the moment the bug happens.
• 31 Write a minimal repro case for this bug with no dependencies.
• 32 Which assumptions about the input data are being violated in this code?
• 33 Here's the stack trace. Explain what happened, line by line.
• 34 Why is this SQL query slow? Which indexes would help?
• 35 I'm seeing a memory leak in the profiler. Where is the object not being released?

Content / social media: 8 prompts (in a Claude Code context)

• 36 Rewrite this text without the corporate cliches and filler.
• 37 Turn this article into 5 short Instagram posts.
• 38 Write 3 headline options: different tone, same topic.
• 39 Find the key insight in this text and turn it into a carousel hook.
• 40 Adapt this post for LinkedIn: a more professional tone.
• 41 What questions will readers have after reading this? Answer them in the text ahead of time.
• 42 Cut this text in half without losing the point.
• 43 Translate this technical text into entrepreneur language without losing accuracy.

Workflow: 7 prompts

• 44 Break this task into atomic steps with the dependencies between them.
• 45 What's the riskiest part of this plan? What could go wrong?
• 46 Do this with the smallest possible number of changed files.
• 47 Is there an existing library for this? Don't write it from scratch if you don't have to.
• 48 Which of these tasks can run in parallel via subagents?
• 49 Write a CLAUDE.md for this project based on what you know about the code.
• 50 What should I check before showing this to a client?

Setup Checklist

Getting started with Claude: what to check.

• □ Signed up at claude.ai (you can try it for free)
• □ Created a Project named after my project or business
• □ Added about-me.md: who I am, who I write for, my style
• □ Added anti-ai-style.md: phrases Claude must never use
• □ Wrote a master prompt and saved it as a Text Shortcut on Mac
• □ Tested it: asked for one post in my style
• □ Downloaded the Claude Desktop App for more powerful file work

CTA block (ArticleCTA)