Yesterday a new resource landed on r/PromptEngineering that’s actually worth bookmarking.
Not another “50 ChatGPT prompts to 10x your productivity” listicle. Something more useful.
Most prompt libraries fail because they’re built for screenshots, not actual work. They look impressive in a tweet and fall apart the moment you try to adapt them to your real situation. This one is built differently.
The site at ainews.tech has two sections worth your time.
What’s in it
100 prompts organized by job-to-be-done. Writing, code, sales, research, design, productivity, learning, creative, analysis. Each one has a use case, a template with {{placeholders}}, and one-click buttons to open it directly in ChatGPT, Claude, or Gemini.
The placeholder system matters more than it sounds. Instead of copying a prompt and then trying to reverse-engineer where your actual content goes, the templates make the insertion points explicit. You see exactly what the prompt expects from you before you run it. That’s a small design decision that saves real time when you’re using these on deadline.
The job-to-be-done organization is also the right call. Browsing by “writing” vs “code” sounds obvious, but it matches how people actually think when they sit down to work. You don’t wake up thinking “I need an AI prompt.” You think “I need to write a cold email to a CFO” or “I need to explain this codebase to a new hire.” The library is indexed to that kind of thinking.
Then there are 128 Claude Skills across 12 packs.
The twist
These skills are hand-written. Not generated by AI, not scraped from Reddit threads. Each one includes required inputs, structure, anti-patterns, and the exact instructions Claude follows.
128 skills is a serious body of work. The difference between a hand-crafted skill and a vibe-coded one shows up fast when you’re running it on real tasks.
Here’s what that difference looks like in practice. A vibe-coded skill gives Claude a general direction and hopes for the best. A hand-crafted one specifies the output format, the failure modes to avoid, the inputs it actually needs, and the structure it should follow. When you feed it a messy real-world task instead of a clean demo example, the hand-crafted version holds up. The vibe-coded one hallucinates something plausible and calls it done.
The anti-patterns sections in particular are the part most people skip and then regret. That’s where the creator documented what went wrong during testing. Reading those before you run a skill on something important is the difference between a clean first run and 20 minutes of debugging why the output looks weird.
It’s also MIT-licensed. No signup. No paywall. Fork it, modify it, build on top of it.
How to use it
- 🔍 Go to ainews.tech/prompts. Browse by job-to-be-done, not by category. Find what you’re actually trying to get done this week.
- 📋 Grab the prompt template. Swap the {{placeholders}} for your real context. Don’t sanitize your inputs to make them fit the template, put in the messy real version. The template is there to structure the AI’s response, not to limit what you bring to it. Run it in whatever model you’re already using.
- ⚙️ Head to ainews.tech/skills. Find the pack that matches your recurring workflow. Read the anti-patterns section first. That’s where you learn what trips people up and you’ll skip the most common mistakes before you even start.
- 🔧 Fork what’s useful. MIT license means you own your modifications. The prompts and skills in here are starting points, not scripture. If a placeholder doesn’t match how you work, change it. If an instruction produces outputs you don’t like, rewrite it. The library gives you a running start; you take it from there.
Pro tip
Don’t try to absorb all 228 assets at once. Pick the one task you repeat 10+ times a week. Find the prompt or skill that covers it. Get one real win, then come back for more.
The people who get value from libraries like this are the ones who treat them like a toolbox, not a museum. A museum you visit once, take a photo, and never return to. A toolbox you open every time you need to get something built. The goal is to get one prompt or skill into your actual workflow this week, not to star the repo and forget it exists.
If you want to go deeper, take the skill you’re using most and read the full specification, not just the template. Understanding why the instructions are written the way they are helps you adapt it when your use case drifts from the original one. That’s when the hand-crafted quality really pays off.
Go get it
The creator did the reps. You skip straight to using it.
Someone spent serious time building this so you don’t have to start from scratch. That’s the kind of open-source contribution worth acknowledging with actual use, not just an upvote.
🚀 Bookmark ainews.tech/prompts and ainews.tech/skills. Both are free, both are live right now.
Built a free library: 100 prompts + 128 Claude Skills
by u/Annual-Ad-2495 in PromptEngineering