Guide
Prompts and scratch notes are ephemeral. A Product Map is persistent product context: what the product is, how it is structured, and what each feature is for — reusable across sessions and tools.
Persistent context survives a new chat, a new agent, and a new teammate. It is not a longer system prompt. It is a maintained model of domains, jobs, flows, capabilities, and features that agents can read and that humans can correct.
Keep the Product Map as the source of truth in Kriyastream. When you work in Claude Code or Cursor, point agents at the relevant map structure (and linked code evidence) instead of retyping product lore.
Pair this with Code Intelligence so features stay connected to repos and paths — agents implement against named product units, not vague tickets.
Rules files guide agent behavior. A Product Map captures product structure. You want both: rules for how to work, Product Map for what the product is.
Dedicated integration pages explain Kriyastream + Claude Code and Kriyastream + Cursor workflows.
