Every project has its own goals, constraints, and preferences. Use the Custom Knowledge tab to capture those. Everything you add here is remembered and applied across your project, making edits smarter and more aligned.

You don’t need to be comprehensive. A few lines of clear direction can go a long way.

​
What to include in your Custom Knowledge

Here are a few examples of useful knowledge to add:
  • Project guidelines: What to prioritize, what to avoid or how decisions should be made.
  • User personas: Detailed descriptions of your target users and their needs.
  • Design assets: Color palettes, typography, layout rules and other visual elements.
  • Coding conventions: Naming conventions, formatting rules and file structure.
  • External references: Links to API docs, internal tools, design systems or style guides.
  • Security practices: Guidelines for secure coding, data protection and handling sensitive information.
  • Compliance requirements: Any legal or regulatory requirements your project must adhere to.

​
Tips for using Custom Knowledge

  • Start small. Even a few lines can make a meaningful difference.
  • Think of it as shared memory. Everything you write here is remembered and used in future edits.
  • Keep it current. Update it as your project evolves to stay aligned and relevant.