Home

Praxis

Praxis is a deterministic project generator. A user describes a desired project through the praxiflow CLI or a versioned JSON configuration; Praxis validates that intent, resolves a set of composable template modules, and atomically writes a complete source tree.

This directory is the documentation source of truth. The Praxis GitHub Wiki is rendered from these files so documentation changes travel through the same review history as code.

Choose a reading path

I am evaluating Praxis

1. Overview — what Praxis is and is not.
2. Architecture — the major systems and data flow.
3. Standard-Projects or Praxis-Pro — what gets generated.

I am changing Praxis

1. Repository-Map — workspace and directory ownership.
2. Code-Architecture — TypeScript modules and abstractions.
3. Generation-Pipeline — the complete execution sequence.
4. Manifest-System — how template modules compose.
5. Testing — the evidence required for a safe change.

I am an agent joining the repository

Start with the Agent-Guide. It maps common tasks to authoritative files, invariants, and verification commands. Do not infer generator behavior from template filenames alone: module selection and manifest selectors determine what reaches an output.

Core documentation

Page	Answers
[[Terminology	Terminology]]
[[Code-Architecture	Code architecture]]
[[Generation-Pipeline	Generation pipeline]]
[[Manifest-System	Manifest system]]
[[Generated-Backends	Generated backends]]
[[UI-Templates	UI templates]]
[[Wiki-Publishing	Wiki publishing]]

Accuracy contract

• Pages describe the current main/cli implementation unless marked Future direction.
• Repository-relative source links identify the implementation that supports a claim.
• A template existing on disk does not mean it is selected for every project.
• Frontend-only projects do not generate a backend. Backend and fullstack projects generate Express; pro-backend generates Django/DRF or Go/Gin.
• Generated projects are outputs, not runtime dependencies of the Praxis CLI.