Platform · Component ① · Skeleton (chassis)

The shared skeleton
every project rides on

standarda-template is the shared Django skeleton laid down every time a new AX project starts. The bones every service needs — sign-up, login, permissions, error handling — are already wired in. The FDE just adds the customer's business logic on top.

🧱 Cookiecutter skeleton 🔐 Auth & permissions built in 🤖 Claude skills, agents & hooks bundled 🧪 E2E tests · docs system
5 Django appsAuth · profiles · email · SMS · projects
Full authSign-up · login · Google OAuth
Dev automation built inClaude skills · agents · hooks
Quality by default~28 utilities · E2E · docs system
Analogy · Car skeleton (chassis)

You don't carve the frame from scratch every time

Just as a carmaker doesn't design a new chassis for every model, Dawell Service doesn't build login, permissions, and error handling from zero on every project. We lay down the proven skeleton as-is and add only the parts that fit the customer's work on top. Because the skeleton is sturdy and standardized, every project you open has the same structure.

  • Every project shares the same bones → anyone grasps the structure instantly
  • Sensitive areas like security and auth reuse proven code
  • New projects automatically inherit the improvements and lessons banked in the skeleton
Car chassis (skeleton) illustration — standarda-template
standarda-template = the standard chassis every model shares
What's Inside

What's already in the skeleton

The moment you generate a new project, everything below — from the web bones to the AI dev tooling — is ready to go.

Web skeleton — Django apps & shared utilities

The bones every service needs. Auth, permissions, and utilities are already wired in.

🔐

accounts

User authentication. A Custom User model and Google OAuth login are built in.

👤

profiles

User profile management — profile data kept separate from the account, in a standard structure.

✉️

emails

Email verification — sign-up, password reset, and other email-based flows ready to use.

📱

sms

SMS verification — plug straight into any service that needs phone-based identity checks.

🗂️

projects

Project management — the baseline data structure for agents that handle many targets and tasks.

🧰

utils (shared utilities)

About 28 functions — validation, permissions, error codes, serializers, response standardization, and more. Not an app, but shared by all code. (+ agent_utils for agents.)

AI-native dev automation — .claude

The skeleton ships with more than Django code — it carries the way you develop on top of it (skills, agents, hooks) too. So whichever project you open, you develop with the same tools and the same workflow.

Dev skills · 11

From /dev, /develop, and /release to documentation, client guides, and template sync — the create, develop, and deploy flow lives in commands.

🧑‍🔧

Specialized subagents · 11

Spec validation, PDF/Excel parsing, API/UI testing, server-log debugging, backlog management — role-specific expert agents share the development load.

🛡️

Quality guards (Hooks)

Pre-commit checks on issue docs, logging rules, and skill descriptions run automatically — even when people forget team rules, the tooling enforces them.

📚

docs · convention system

Rules for issue, feature, and structure docs plus CLAUDE.md conventions come bundled, so the AI generates consistent code.

🤝

Client guides

User guides and test guides for customers are generated semi-automatically — so customers can start using what you built right away.

🔄

Template sync

Pull improvements banked in the skeleton into a project (sync-from), and push a project's good patterns back up to the skeleton (sync-to).

* How this dev automation actually connects into a single flow is covered in detail on the Dev Automation Tools page.

“Not rebuilding auth and permissions — and inheriting the way you develop too — that's what saves the entire first few days.”

The more security is involved, and the more it's about dev rules, the faster and safer it is to reuse a proven skeleton.

How It Starts

The flow of opening a new project

Cookiecutter stamps out the skeleton, and the setup script prepares the dev environment too.

STEP 1

Generate skeleton

Enter the project name and settings in Cookiecutter and the full standard structure is generated.

STEP 2

Environment setup

The setup script prepares the virtualenv, dependencies, and .env.

STEP 3

DB · admin

Database creation, migrations, and an admin account are all set up automatically.

STEP 4

Start developing

With auth and permissions already running, you add customer business logic right away.

Cookiecutter Django 4.2 Django REST Framework PostgreSQL Custom User · Google OAuth Email · SMS verification pytest E2E tests standarda-core integration 11 Claude Code skills 11 subagents Quality hooks docs · CLAUDE.md conventions
Explore More

Explore the platform