-
Notifications
You must be signed in to change notification settings - Fork 0
Extending Generated Projects
Generated repositories are owned by their users. Extend them using their framework's native patterns while preserving the lifecycle and infrastructure contracts recorded in praxis.config.json.
- Read
praxis.config.json. - Resolve its Template-Agent-Guide.
- Identify runtime entry points and selected integrations.
- Read health/readiness/shutdown behavior.
- Inspect Compose/Kubernetes/Terraform only if present.
- Run the generated repository's tests before changing behavior.
Keep routes thin, add services for reusable policy, isolate external integrations behind small modules, and register initialization/cleanup with the existing lifecycle. Do not connect clients during module import if failure cannot be rolled back.
Create bounded applications or focused core modules. Keep settings environment-specific, views transport-oriented, permission/domain policy explicit, and schema changes in migrations. Add Celery tasks only when the worker/broker topology exists.
Keep handlers transport-oriented, services policy-oriented, and persistence behind narrow typed interfaces. Wire implementations explicitly in command entry points, close every constructed dependency, and update sqlc queries/migrations together.
- Compose is local topology; do not treat it as cloud provisioning.
- Kubernetes owns workloads and rollout behavior; keep probes aligned with application semantics.
- Terraform owns cloud resources/state; do not place application migration or secret values in Terraform source.
- Changes crossing application and infrastructure layers require tests/evidence in every affected layer.
If the improvement belongs in future generated projects, change the relevant manifest/overlays and contract tests in Praxis. Preserve selectors and patch anchors, regenerate representative outputs, and verify unselected configurations remain clean. Start with the Template-Agent-Guide.
This Wiki is generated from the repository's versioned docs/ source. Update and review the source files; do not rely on hand edits to generated Wiki pages.
- Core-Internals
- Architecture
- Repository-Map
- Code-Architecture
- Generation-Pipeline
- Manifest-System
- UI-Templates
- Testing
- Agent-Guide
- Wiki-Publishing
- Template-Architecture
- Standard-Projects
- Standard-Frontend-Architecture
- Express-Architecture
- Fullstack-Architecture
- Praxis-Pro
- Django-Architecture
- Gin-Architecture
- Capability-Architecture
- Compose-Architecture
- Kubernetes-Architecture
- Terraform-Architecture
- Extending-Generated-Projects
- Generated-Backends