Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.potpie.ai/llms.txt

Use this file to discover all available pages before exploring further.

As code generation becomes inexpensive, the constraint shifts from writing speed to architectural judgment. Forge is built for that constraint. Engineers define outcomes, boundaries, and invariants upfront, and agents handle implementation with full repository awareness and respect for existing patterns.

​
Specification first

Before generating anything, Forge probes for:
  • The desired outcome and scope
  • Constraints and invariants the implementation must satisfy
  • System boundaries and interface definitions
  • Failure modes and validation strategies
This shifts the work from writing a code to reasoning about the system behaviour. Agents handle the implementation only once the specification is locked.

​
Repository context

Forge reads the knowledge graph for established abstraction layers, dependency direction rules, naming conventions, shared domain models, and prior architectural decisions. When introducing new functionality, Forge:
  • Reuses existing abstractions
  • Avoids duplicating domain logic
  • Respects dependency boundaries
  • Aligns with current error handling and testing patterns
Forge integrates seamlessly as it generates code with full repository context.

​
Get Access

Forge is part of Potpie’s enterprise offering. Reach out to learn more or explore the full set of specialist agents.