Skip to main content

Knowledge Base

The Knowledge Base is the authoritative context store for a project.

Why It Is Authoritative​

Anything saved in the Knowledge Base becomes long-term context for AI workflows across design, coding, and generation stages.

Entry Types​

Use the right entry type for the right job:

  • Documents: specs, GDDs, design notes
  • Links: external references (docs, Figma, research)
  • Contacts: ownership and escalation points
  • Key-value entries: stable structured facts

Knowledge Base entries

Knowledge Base Q&A​

Use KB Q&A to ask project-grounded questions such as:

  • Target platform
  • Planned level count
  • Feature constraints

If required data is missing, the system should state that clearly instead of guessing.

Knowledge Base Q&A

Operating Tips​

  • Save finalized design outputs, not rough fragments
  • Keep contact entries current
  • Prefer concise, explicit documents over long unstructured notes

Next: Design Assistant and Evaluation