Skip to main content

​
Usage Tips

​
Use Custom Knowledge to document project info

Use Custom Knowledge to document product vision, user journeys, core features, and more. What to document:
  • Product vision: Core value and goals
  • User journeys: Complete user workflows
  • Core features: Main feature modules and capabilities
  • Design rules: Design standards and constraints
Benefits:
  • AI continuously references this knowledge
  • Maintains project consistency
  • Improves generation accuracy

​
Define roles and boundaries

Define roles and boundaries (Admin/User/Investor, etc.) so AI generates code with the right permissions. What to define:
  • Role types: Admin, regular users, visitors, etc.
  • Permission boundaries: Features each role can access
  • Data isolation: Data scope each role can see
Example: 
Role definitions:
- Admin: Can access all features including user management and system settings
- Regular user: Can access profile, order management
- Visitor: Can only browse public content

​
Generate project knowledge base

Generate a knowledge base for your project based on implemented features. Ask AI example: 
Generate a knowledge base for my project based on implemented features.
Include product positioning, core features, user roles, and design standards.
Generated content:
  • Project overview
  • Feature list
  • User role definitions
  • Design standards
  • Technical architecture

​
Save what works and reuse it next time

Every time you find:
  • A prompt that works really well
  • A structure AI understands well
  • A step that rarely breaks
How to save:
  • Save it for next time
  • Record in project knowledge base
  • Organize into prompt templates
  • Store in Custom Knowledge
Benefits:
  • Improved efficiency
  • Maintained consistency
  • Fewer errors
  • Quick reuse of successful patterns
💡 Tip: Regularly organize and update these patterns to build your own best practices library.