vendix-development-rules

To enforce consistent TypeScript standards across multi-tenant projects, apply codified development rules covering TypeScript, Prisma-generated clients, and RxJS patterns for all codebase interactions. This ensures safe, scalable coding practices across frontend and backend.

The best way to plan multi-file refactors in a Vendix codebase is using decision frameworks and agent selection guidance encoded in development standards. This approach reduces errors and ensures strict adherence to documented verification workflows using container logs.

Yes, you need Prisma-generated clients for Vendix architecture planning. Mandatory development rules require strict adherence to Prisma-generated clients, TypeScript, RxJS patterns, and multi-tenant context during code research and feature designs.

The verification workflow using container logs works by requiring strict adherence to documented verification steps during code reviews and debugging tasks. This reduces waste and errors by validating code changes against container log outputs before finalizing.

Yes, you can use these development standards for onboarding new developers to a multi-tenant project. The rules codify consistent practices, provide decision frameworks, and outline verification workflows ideal for understanding frontend and backend architecture safely.

You should not bypass RxJS patterns for code changes in a multi-tenant application. The encoded Vendix development rules mandate strict adherence to RxJS patterns, TypeScript, and Prisma-generated clients across all interactions to maintain consistency and safety.