Iaac Maai Structure Compliance Check Cloudflare

Cloudflare Fullstack Deployment

Deploy fullstack web applications on Cloudflare's edge network. Everything runs at the edge (300+ data centers), scales to zero, and has a generous free tier requiring no credit card (except R2, which is free but requires a credit card on file).

Quick Start

# 1. Sign up at https://dash.cloudflare.com (free, no credit card)
# 2. Install CLI
npm install -g wrangler
# 3. Authenticate (opens browser)
wrangler login
# 4. Scaffold a project
npm create cloudflare@latest my-app
# 5. Run locally
cd my-app && wrangler dev
# 6. Deploy globally
wrangler deploy

Architecture Overview

┌──────────────────────────────────────────────────┐
│              Cloudflare Edge (300+ DCs)           │
│                                                    │
│  ┌────────────┐  ┌────────────┐  ┌─────────────┐  │
│  │  Workers    │  │  Static    │  │  Workers AI  │  │
│  │  (API/SSR)  │  │  Assets    │  │  (inference) │  │
│  └─────┬──────┘  └────────────┘  └─────────────┘  │
│        │                                           │
│  ┌─────┴──────┐  ┌────────────┐  ┌─────────────┐  │
│  │  D1 (SQL)  │  │  R2 (S3)   │  │  KV (cache)  │  │
│  └────────────┘  └────────────┘  └─────────────┘  │
└──────────────────────────────────────────────────┘

Service Decision Matrix

Dashboard vs CLI

Almost everything is CLI-only via wrangler. The dashboard is only needed for:

• Account signup (one-time) at dash.cloudflare.com
• API tokens for CI/CD at Profile > API Tokens
• Custom domain setup at Workers > Settings > Domains
• Monitoring / analytics for logs and metrics

All resource creation (D1, R2, KV), deployments, migrations, and secrets are handled by wrangler.

Recommended Stacks

JavaScript/TypeScript (Production-ready)

Python (Open Beta)

Key Architecture Rules

1. Max 300-400 lines per file. Split aggressively.
2. Domain-driven folders. Each feature is a self-contained directory.
3. No hardcoding. Config in env vars or constants files.
4. Rich comments. Explain the why, not just the what - target beginners.
5. Log everything. Use structured logging so debugging is possible.
6. Zustand early. Introduce state management before complexity hits.
7. Validate all inputs. Never trust client-sent data.
8. ARCHITECTURE.md at root — MANDATORY. Once the user decides on an architecture, immediately create ARCHITECTURE.md with: overview, mermaid diagram, services table, folder structure, data flow, and domain map. Keep it up to date — if the architecture changes, update this file FIRST. See references/architecture-bestpractices.md for template.

Reference Docs

Work in Progress — Self-Correcting Skill

This skill is actively evolving. If during execution any reference file contains outdated APIs, incorrect imports, broken commands, or patterns that don't work:

1. Fix it immediately in the reference file, or
2. Ask the user if they'd like the skill files updated with the correction.

Don't silently work around inaccuracies — surface them and fix the source so future sessions benefit. Treat every execution as a chance to improve the skill.

Agent Execution Flow

This skill is designed for AI coding agents to execute, not just reference. Every reference file contains copy-pasteable code and runnable commands.

Step-by-step for the AI agent:

1. Understand the user's goal. If they have no idea, read beginner-onboarding.md — help them pick a project from the ideas list. Ask what interests them, what they want to learn.

2. Discuss architecture. Once a project is chosen, discuss which services are needed (use the Service Decision Matrix above). Let the user make the call on stack/features.

3. Document architecture IMMEDIATELY. Create ARCHITECTURE.md at project root with:

   • Overview paragraph
   • Mermaid diagram (references/architecture-bestpractices.md has template)
   • Services table (service, purpose, binding name)
   • Folder structure
   • Data flow description This is the source of truth. Update it every time the architecture changes.

4. Build the app. Follow tutorial-todo-app.md as the base pattern, adapting for the user's chosen project. Pull specific patterns from:

   • js-patterns.md / python-patterns.md — code patterns
   • database-storage.md — D1, R2, KV, Queues setup
   • auth-security.md — Better Auth, JWT, Turnstile
   • architecture-bestpractices.md — structure, security, state management

5. Deploy. Follow deployment-cicd.md for CLI deploy + GitHub Actions setup.

6. Keep ARCHITECTURE.md current. After adding any new service, domain, or changing data flow — update ARCHITECTURE.md and its mermaid diagram before moving on.

Source: iaac-maai/structure_compliance_check — distributed by TomeVault.