Promptles
Anti-Patterns

Simplify Before You Prompt

When a task feels overwhelming, don't dump the full complexity on Claude. Break it down, pick the most impactful piece, and write a focused prompt for that. You can always follow up with the next piece.

Where you'll practice this

2 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.

  • Simplify the Mess

    You inherited a utility function `processUserData` that does way too much: it validates input, normalizes names, formats phone numbers, checks for duplicates, and sends a welcome email. It's 80 lines long and untestable. You want to refactor it, but the situation is complex. The…

  • When No Skill Fits

    You want to rename a single React component file from `UserCard.tsx` to `MemberCard.tsx`, update the two import sites, and run typecheck. That's it — three files touched, two minutes of work. Your installed skills are `/diagnose` (for bugs), `/review-pr` (for PRs),…

Other principles in Anti-Patterns