How Teams Use This

Read the standard. Run the checklist. Ship with evidence.

Everything here is designed to reduce guesswork, make delivery consistent, and keep quality visible at handoff.

Build Standards for implementation, validation, permissions, and UX behavior.
Review Checklists and templates that make work reviewable and traceable.
Improve Tasks and ownership rules that turn process into repeatable team habits.
Non-Negotiables

Rules for Every Task

These rules apply regardless of role, platform, task size, or deadline.

No Silent Failures

Every error must be visible to the user. Console-only errors are not acceptable.

No Untested Handoff

Test your own work before marking it complete. Evidence must be added to the ticket.

Backend Is Source of Truth

Frontend improves UX, but business rules, permissions, and validation must be enforced on backend.

No Missing Loading State

Every async action must show loading, success, and failure states.

No Unsafe Delete

Destructive actions must have confirmation, clear messaging, and permission checks.

No Mobile Skipped

Every UI must be checked on mobile before delivery.

Team Ownership

Team Ownership & Process Standards

Own the work end-to-end. Understand the requirement, ask questions early, build with standards, test your own work, update clearly, raise issues in the ticket, and stay accountable for changes.

Core Rule

Every team member must own their work end-to-end: understand the requirement, ask questions early, build with standards, test their own work, update clearly, raise issues in the ticket, and stay accountable for changes. Before marking things Done — meet the standards.

Expected Standards

These are the habits every team member is expected to follow on every task.

Understanding Read the task properly before starting.
Clarification Ask questions before building unclear requirements.
Accountability Own your changes, bugs, and fixes.
Communication Give concise updates with time and status.
Escalation Ask for help when blocked after proper effort.
Work Type Standard Checklist
Supabase API, table, RPC, RLS, or Edge Function Supabase Standards Supabase Checklist
Django view, model, form, serializer, or service Django Standards Django Checklist
React page, component, form, table, modal, or UI state Frontend Standards Frontend Checklist
Xano API, reusable function, workflow, or webhook Xano Standards Xano Checklist
Website build, migration, replication, launch, or handoff Website Standards Website Launch Checklist
Third-party integration like Stripe, SendGrid, Gmail, Razorpay Third-Party Standards Third-Party Checklist
Backend API Done
Schema, constraints, indexes, RLS or permissions, validation, error responses, logs, tests, and frontend API documentation are complete.
Frontend Task Done
Main flow works, validation works, loading state works, errors show in UI, mobile is checked, and Add/Edit behavior is consistent.
Django Feature Done
Permission enforced, validation in form or serializer, logic in service, no duplicated business logic, and templates keep CSS/JS separate.
Website Done
Pages built, forms tested, mobile responsive, SEO metadata configured, redirects handled, analytics added, and staging approved.
Start Here

Use Standards Before Building

Before starting any task, read the matching standard, follow the checklist, and submit the final work with evidence.