Code Kits

Praetor's generation pipeline is made up of Kits — each one responsible for a single type of implementation node. The Kit Registry maps an implNodeType string to the Kit that handles it.

This page documents every registered Kit, ordered by the topological batch in which it runs.

Topological Batch Order

Kits and deterministic pipeline steps run in dependency order. Later batches can import types and contracts from earlier batches.

Batch 0:  [DETERMINISTIC] ScaffoldStep
Batch 1:  [DETERMINISTIC] SharedTypesStep + DesignSystemStep
Batch 2:  [KIT] EntityKit, SchemaKit, GuardKit
Batch 3:  [KIT] AuthKit
Batch 4:  [DETERMINISTIC] MigrationStep
Batch 5:  [KIT] ServiceKit
Batch 6:  [KIT] OperationKit
Batch 7:  [KIT] EndpointKit
Batch 8:  [KIT] APIClientKit
Batch 9:  [KIT] ComponentKit, UIStateKit
Batch 10: [KIT] PageKit
Batch 11: [KIT] LayoutKit, NavigationKit
Batch 12: [KIT] WorkflowKit, NotificationKit, AutomationKit
Batch 13: [DETERMINISTIC] TestInfraStep
Batch 14: [DETERMINISTIC] CICDStep

Deterministic steps produce output from templates with no LLM. Kit batches may involve an LLM in their APPLY phase.

Core Application Kits

UI Kits

Mobile Kits

Frappe / ERPNext Config Kits

These Kits handle ERPNext DocType configuration nodes. They produce JSON configuration files rather than TypeScript source. See Config Kits for full coverage.

Kit Registry lookup

The pipeline uses a single call to dispatch to the correct Kit:

import { getKit, initializeKits } from './kits/kit-registry.js'

// At startup — loads all Kit modules and triggers self-registration
await initializeKits()

// At generation time — O(1) Map lookup
const kit = getKit(implNode.implNodeType)
if (!kit) {
  log.warn({ implNodeType: implNode.implNodeType }, 'No Kit registered for this node type — skipping')
  continue
}

const output = kit.generate(input)

If no Kit is registered for an impl node type, that node is skipped and a warning is recorded in the generation run summary. It does not block other nodes.

Adding a new Kit

1. Create src/services/codegen/kits/{name}-kit.ts
2. Implement CodegenKit (or MultiNodeCodegenKit if you need all nodes at once)
3. Call registerKit(new MyKit()) at the bottom of the file
4. Add await import('./my-kit.js') inside initializeKits() in kit-registry.ts

The Kit will be available immediately after the next initializeKits() call.