Slide 9
Slide 9 text
10 Best Practices for Successful Development
Prompting Tips
1 Clear and Detailed Prompts
Describe specific page names (e.g., /dashboard) and expected
behaviors in detail rather than vague instructions
2 Use Natural Language
Describe requirements in everyday language, such as "Investor
role users can access this component"
3 Leverage Screenshots
Provide visual information when explaining bugs or UX issues
for more effective communication
4 Set Guardrails
Explicitly indicate files that should not be edited, such as
"/shared/Layout.tsx (do not edit)"
5 Incremental Implementation
Break work into small, testable chunks rather than implementing
five features at once
Workflow Tips
6 Utilize Knowledge Files
Document product vision, user journeys, and design systems,
sharing them across all prompts
7 Active Use of Chat Mode
For 2-3 minor bug fixes, switch to Chat Mode to investigate root
causes before implementation
8 Version Management
Pin (version lock) working features before implementing new
ones to maintain stable versions
9 Small Modifications with Visual Edit
Use the free Visual Edit feature for text, color, and font changes
to preserve credits
10 Remix for Fresh Starts
When stuck in a bug loop, Remix (create clean copy) the project
and rebuild for faster resolution