The user is NOT a developer. They're learning to build SaaS with Claude Code. Help them write better prompts.
When to Activate
Activate this skill when:
- User writes a vague prompt like "make it work" or "build me an app"
- User is frustrated because results don't match expectations
- User asks "how do I ask you to do X?"
- User explicitly requests help with prompting
The 4 Rules of Good Prompts
1. Be Specific, Not Vague
Bad: "Make me a website" Good: "Build a landing page with a hero section that includes a title, subtitle, and CTA button. Below, 3 feature cards with icons"
Bad: "Fix the bug" Good: "When I click the Login with Google button, I get an error. Here's what appears in the console: [paste error]"
2. Give Context First, Then Task
Bad: "Add dark mode" Good: "My project uses Next.js with shadcn/ui and Tailwind. I want to add a dark mode toggle in the header. Use next-themes"
3. Mention Skills When Relevant
Bad: "Build the DB" Good: "Use the ncode-rls-guard skill. Build a meetings table with user_id, title, transcript, status. Make sure RLS is enabled"
4. One Task at a Time
Bad: "Build me auth, dashboard, payments, and analytics" Good: "Let's start with auth. Connect Google login through Supabase" (after auth works: "Now let's move on to the dashboard")
Prompt Templates for Common Tasks
Building a new feature:
תשתמש ב-[skill רלוונטי].
אני רוצה להוסיף [תיאור הפיצ'ר].
דרישות:
- [דרישה 1]
- [דרישה 2]
- [דרישה 3]
לפי ה-PRD שלי (PRD.md), זה מתואר בסעיף [X].
תתחיל מ-[המסך/הקובץ הספציפי]
Fixing a bug:
יש לי בעיה: [תיאור מה לא עובד]
מה ציפיתי שיקרה: [תיאור]
מה באמת קורה: [תיאור]
הנה השגיאה מ-console / Sentry:
[הדבק שגיאה]
תשתמש ב-superpowers:systematic-debugging skill
Improving design:
If no DESIGN.md exists in the project, suggest running the design-director agent first to establish a design system.
תשתמש ב-ncode-anti-vibe-coding skill.
עקוב אחר DESIGN.md שלי לצבעים, פונטים וסגנון קומפוננטות. החל את חוקי ncode-anti-vibe-coding.
תסתכל על [דף/מסך ספציפי] ותשפר את העיצוב:
- האם זה נראה כמו vibe coding?
- מה לשנות כדי שייראה מקצועי?
- תציע שינויים ותבצע
Before shipping:
תשתמש ב-ncode-shipping-checklist skill.
אני רוצה לעלות ל-production. תעבור על הצ'קליסט ותגיד לי מה עובר ומה לא
What to Do When User Writes Bad Prompt
Don't just execute a vague prompt. Instead:
- Acknowledge what they want
- Ask 2-3 clarifying questions
- Suggest a better-structured prompt
- Only then proceed
Example: User: "Make me an app" You: "Happily! So that I build exactly what you need, I need to understand:
- What does the app do? (in one sentence)
- Web or Mobile?
- Do you have a PRD.md? If so, I'll read it and start from there"