Why it matters: The Knowledge file is your project’s brain. It gets sent with every prompt and helps the AI understand the full context.What to include:
Clear, verbose prompts = better output. Think of the AI like your engineering partner—it only knows what you tell it.Prompting tips:
Be specific: Mention the exact page (e.g. /dashboard) and expected behavior.
Use natural language
Copy
Ask AI
I want users with the role Investor to access this component, but not Admins.
Add screenshots: Especially useful for describing bugs or UX issues.
Add guardrails: Tell the AI what not to touch. E.g.
Copy
Ask AI
Do not edit /shared/Layout.tsx.
Repeat important instructions across prompts. The AI’s memory can be limiting.
Avoid trying to implement 5 things at once. Break work into smaller, testable chunks. Use Chat Mode between each block to validate before moving on.
Copy
Ask AI
**Feature Breakdown Template:**Create the new pageAdd UI layoutConnect the dataAdd logic + edge casesTest per role
If your app has multiple roles (e.g. Admin, Investor, Startup), always define which role the prompt applies to. This helps avoid bugs caused by shared logic/components.
Copy
Ask AI
As an Investor, I want to view the company dashboard, but I shouldn’t be able to edit it. Please isolate this feature to the Investor role only.
Chat mode = your AI co-pilot. It helps you debug, brainstorm, and plan implementations—without editing your code until you’re ready.When to switch to Chat Mode:
After 2–3 failed “Try to Fix” attempts
When debugging complex logic or database issues
When planning new features
Copy
Ask AI
Suggest 3 ways to implement X
Workflow tip:Some users like to use Chat Mode for 60–70% of your time. Only click “Implement the plan” when you’re fully satisfied.
If you forget using the Chat mode, this format improves output consistency and prevents collateral edits.
Copy
Ask AI
On page /settings, implement [feature]. The expected behavior is [XYZ]. Please don’t touch component A, layout B, or shared logic unless necessary. Follow best practices from Tailwind / Supabase / X.
To avoid unwanted code execution:
Copy
Ask AI
Investigate but don’t write code yet.
Copy
Ask AI
Suggest 3 ways to solve this without changing anything.
This keeps control in your hands.
When AI enters a “loop,” use this sequence to avoid endless cycles of patching broken code:
Switch to Chat mode
Paste the error screenshot
Say:
Copy
Ask AI
Please investigate this without breaking other features. If needed, revert to the last working version and fix from there.
You’re not alone. AI can be magical one moment and frustrating the next. The final 5% of any build is often the slowest—but the most important.
Golden rule:Take your time with prompts. Re-check everything. Break work into small, testable blocks. The more precise your inputs, the better your outputs.
Add a voice note prompt using dictation (e.g. On Mac, use the mic to dictate long prompts) for long prompts. You’ll craft better input faster—especially useful when frustrated or tired.
Use the “I am frustrated…” prompt pattern to nudge better AI focus
After a major edit, always recheck multiple roles and their behavior (especially with conditional logic)
Store stable versions as fallbacks for quick debugging
If you’re seeing unexpected side effects, this helps avoid bugs caused by overly generic logic.
Copy
Ask AI
Create a component specifically for [role X] and do not reuse shared components unless clearly scoped.