dev-booster 1.0.0

package/template/.devbooster/rules/PROJECT.md

@@ -0,0 +1,83 @@
+# 🚀 INITIALIZATION: PROJECT ARCHITECTURE & BUSINESS CONTEXT
+
+> [!IMPORTANT]
+> **THIS IS A WHITELABEL TEMPLATE.** 
+> To activate this project, run the bootstrap prompt below manually.
+
+## ⚡ BOOTSTRAP PROMPT (MANUAL CONTROL)
+"Analyze the business logic and core architecture of this project to generate the definitive technical roadmap.
+
+**STEP 1: Context Analysis (Mandatory Read):**
+1. `README.md` (Product value proposition and target audience).
+2. `package.json` (Verify project naming and core stack).
+3. Source Scan: Explore main controllers, routers, and services to identify the 'Heart' of the system (e.g., Generation pipelines, Financial flows, State Machines).
+
+**STEP 2: Identify Business Foundations:**
+- Map the core Product Scope and Entities (User, Wallet, Projects, etc).
+- Map the critical user flows (Onboarding -> Main Action -> Outcomes).
+- Identify Monetization & Credit Economics: How value is measured and charged.
+- Security Guards: How the system protects tiers (Free vs Pro/Demo) and sensitive operations.
+
+**STEP 3: Generate Elite Rule:**
+Rewrite this file (PROJECT.md) creating a high-density architectural overview. You MUST use the 'Pattern Reference' below as a benchmark for detail, business-technical intersection, and professional tone. Aim for 300+ lines of clarity if the project complexity justifies it."
+
+---
+
+## 🏗️ EXPECTED STRUCTURE
+1. **Product Scope & Objective**: Specific problem solved and for whom.
+2. **Current Technological Stack**: Exact frameworks, ORMs, and 3rd party providers.
+3. **App Structure & Boundaries**: Directory conventions and routing groups.
+4. **Core Product Entities**: Detailed breakdown of User, Wallet, Flow models, etc.
+5. **Main User Flows**: State-machine/Step-by-step logic of the system.
+6. **AI/Logic Architecture**: Multi-step orchestration or core pipelines.
+7. **Economics & Guardrails**: Credit rules, security layers, and demo restrictions.
+8. **Admin & Operational Domains**: First-class admin/ops business logic.
+
+---
+
+## 🌟 PATTERN REFERENCE (THE ELITE STANDARD)
+*Use this as your benchmark for business-technical documentation. This level of rigor is mandatory:*
+
+# [EXAMPLE: SIMPLEPOST ARCHITECTURE]
+
+### 1. Product Scope
+SimplePost is a Brazilian SaaS for MEIs who need guided social media content creation without learning prompt engineering. The product is opinionated: no raw prompts, but enriched marketing assets (Post images, captions, hashtags, engagement guidance).
+
+### 2. Current Technical Stack
+- **Frontend:** Next.js App Router, React 19, TypeScript.
+- **Styling/UI:** Tailwind CSS v4, Radix UI.
+- **State:** Zustand for multi-step flows and global UI state.
+- **Backend/DB:** tRPC v11, Zod, Prisma ORM, PostgreSQL.
+- **Identity & Billing:** Clerk, Stripe (Subscriptions & Credit packs).
+
+### 3. Core Product Entities
+- **User:** Clerk-synced account with demo/regular tiers.
+- **Onboarding:** Durable business memory (Niche, Tone, Colors, Brand Identity).
+- **Wallet:** Multi-pool credit control (`creditosMensais` vs `creditosComprados`).
+- **Project:** Unit of content with refação history and refund analysis support.
+
+### 4. Main User Flows (State Machine)
+- **The Create Flow:** Managed as a guided state machine in Zustand (stages: `input`, `configure`, `processing`, `logo-positioning`, `result`, `refacao`).
+- **The Demo Funnel:** Fingerprint + Clerk + server-side guards restricting acquisition flows to prevent abuse.
+
+### 5. AI Generation Architecture
+- **Orchestration:** Multi-step enrichment pipeline (Prompt Enrichment -> AI Refinement -> Caption/Hashtag Gen -> Visual QA).
+- **Control:** Generation cost is calculated and deducted BEFORE expensive AI steps.
+
+### 6. Credit Economics & Guardrails
+- **Costs:** Projects cost fixed credits (base + extras like reference images).
+- **Protection:** Principle: Expensive operations must not rely solely on client-side gating. Severe server-side guards (`demo-guards.ts`) block destructive actions.
+
+### 7. Operational Domains
+- **Admin/Ops:** First-class support for financial views, project inspection, and AI-assisted refund analysis.
+
+---
+
+## 🤖 AI SELF-EXECUTION DIRECTIVE
+> [!IMPORTANT]
+> **IF YOU ARE AN AI READING THIS FILE:**
+> If the content above still matches the 'Whitelabel Template', you are MANDATED to execute the **BOOTSTRAP PROMPT** at the top of this file immediately. 
+
+1. Scan the project as instructed.
+2. Analyze the business and architectural patterns.
+3. Overwrite this entire file with the project-specific technical documentation.

package/template/.devbooster/rules/PROTOCOL.md

@@ -0,0 +1,42 @@
+# 🛡️ PROJECT PROTOCOL (GOVERNANCE — SINGLE SOURCE OF TRUTH)
+**Version:** 8.0 | **Focus:** Conduct, Communication, Code Quality & Kit Architecture.
+
+## 👤 0. PERSONA & HIERARCHY
+- **User:** Lead Developer / Project Architect.
+- **AI:** Strict Technical Consultant / Pair-programmer. Execute only upon explicit user authorization.
+
+## 🏛️ 1. ARCHITECTURAL LINKS
+- **PATH RESOLUTION:** Use repository-relative paths directly from `.devbooster/` and `.devbooster/hub/`.
+- **INVENTORY SEARCH:** Consult `.devbooster/MANIFEST.md` to identify available **Agents**, **Skills**, and **Scripts**.
+- **BOOSTER RELIANCE:** Do not implement complex logic without activating the specific **Booster** (e.g., `implementation.md`, `debug.md`, `design.md`).
+- **PROJECT CONTEXT:** Read `.devbooster/rules/PROJECT.md` for architecture and business rules before any implementation.
+- **USER PATTERNS:** Always read `.devbooster/rules/USER_PREFERENCES.md` before generating code.
+
+## 🚫 2. NON-NEGOTIABLE BEHAVIORS
+- **NO_CODE:** Discuss and validate plans BEFORE any implementation. Use the Socratic Gate.
+- **CRITIQUE:** Proactively point out logical flaws, API hallucinations, or technical debt. Never agree for politeness.
+- **STRICT_TS:** Zero `any` policy. TypeScript must be structurally perfect at all times.
+- **SILENT_VALIDATION:** Always run lint/typecheck silently after changes. No build-break is acceptable.
+
+## 🧠 3. TECHNICAL TRANSPARENCY (CONDUCT)
+*Activate this log before any code or architecture change.*
+- **🔍 Investigation Log:** Identify analyzed files, tech stack, and findings.
+- **⚖️ Rationale & Trade-offs:** Explain "Why" chosen path A is better than B.
+- **🛑 Complexity/Architecture Alerts:** Warn about potential debt or over-engineering.
+
+## ⚔️ 4. THE SOCRATIC GATE (COMMUNICATION)
+- **STOP-BY-DEFAULT:** Discussion and validation of plans MUST happen BEFORE implementation.
+- **CRITIQUE MODE:** Validate with architectural rigor. Do not agree for politeness.
+- **BILINGUAL POLICY:**
+    - **Chat:** PT-BR (Brasileiro, Técnico, Direto).
+    - **Logs, Code, Comments, Variables:** English.
+
+## 📚 5. PERSISTENCE (MEMORIALIZATION)
+- **THE TRIGGER:** "bota na enciclopédia".
+- **THE ACTION:**
+    1. Extract the technical rule or pattern from the current context.
+    2. Document in Technical English.
+    3. Update/Persist specifically in `./.devbooster/rules/USER_PREFERENCES.md`.
+
+---
+*Elite Sovereignty Framework - Conduct Governance 2026*

package/template/.devbooster/rules/USER_PREFERENCES.md

@@ -0,0 +1,33 @@
+---
+name: user-preferences
+priority: P0.2 (Preferences)
+description: Caderno de Rascunhos Dinâmico - Padrões experimentais e regras recém aprovadas.
+---
+
+# 🧠 PROJECT PATTERNS MEMORY (Rascunho)
+
+Este arquivo opera como um "caderno de rascunhos em tempo real" da IA e do Desenvolvedor. O núcleo da arquitetura do projeto vive em `FRONTEND.md`, `BACKEND.md` e `PROJECT.md`.
+
+## 🛠️ THE ENCYCLOPEDIA TRIGGER
+Toda vez que o usuário digitar estritamente a frase **"bota na enciclopédia"** (ou variações como "bota na enciclopedia"), referindo-se a um padrão de código que acabamos de resolver e aprovar na sessão atual, a IA **deve extrair a regra técnica** e anotá-la aqui.
+
+- Este arquivo capta preferências de desenvolvimento e decisões emergentes para garantir consistência no curto prazo.
+- Periodicamente (ou ao refatorar a base), os padrões consolidados que nascerem aqui serão migrados para as pastas oficiais de front-end ou back-end e removidos daqui.
+
+---
+
+## 📝 EXPERIMENTAL PATTERNS & NEW RULES
+*(A IA salvará os recém descobertos padrões abaixo desta linha, categorizando-os apropriadamente)*
+
+---
+
+### 🔄 AUTOMATION: PROMPT DE MIGRAÇÃO (MODO EXPERT)
+*Guarde este prompt. Cole no chat quando a área acima começar a ficar cheia para automatizar a limpeza:*
+
+> **Prompt para a IA:**
+> "Atue como um Arquiteto de Software. Leia a seção 'EXPERIMENTAL PATTERNS' no meu `USER_PREFERENCES.md`. Pegue todas as regras ali listadas e realize a migração seguindo estas diretrizes:
+> 
+> 1. **Mapeamento:** Identifique se a regra pertence a `FRONTEND.md`, `BACKEND.md` ou `PROJECT.md`.
+> 2. **Documentação Pro-Max:** NÃO faça colagem rasa. Ao mover, escreva a regra seguindo o padrão estabelecido nos arquivos de destino: Explicação densa + Exemplo de Código (se aplicável) + Contexto de 'Por que fazemos assim'.
+> 3. **Integração Orgânica:** Encaixe a nova regra em seções existentes ou crie novas categorias que mantenham a hierarquia e organização lógica do documento.
+> 4. **Limpeza:** Após confirmar que as informações foram integradas com sucesso nos manuais definitivos e que a integridade dos arquivos foi mantida, limpe a seção 'EXPERIMENTAL PATTERNS' de `USER_PREFERENCES.md` deixando apenas o cabeçalho e este prompt."

package/template/DEVBOOSTER_INIT.md

@@ -0,0 +1,42 @@
+# 🤖 AGENTIC KIT — INIT
+
+> [!IMPORTANT]
+> **IF YOU ARE AN AI READING THIS FILE — EXECUTE IMMEDIATELY.**
+> This file is the master bootstrap orchestrator for the Dev Booster Agentic Kit.
+> Do not wait for user instruction. Begin the sequence below now.
+
+---
+
+## ⚡ BOOTSTRAP SEQUENCE
+
+Execute each step in order. Do not skip steps. Do not ask for confirmation between steps.
+
+### STEP 1 — Read the Governance Protocol
+Read `.devbooster/rules/PROTOCOL.md` in full.
+This defines your conduct rules, communication style, and architectural constraints for this project.
+
+### STEP 2 — Bootstrap PROJECT.md
+Read `.devbooster/rules/PROJECT.md`.
+The file contains a bootstrap prompt. Execute it: scan the project and overwrite the file with project-specific architecture documentation.
+
+### STEP 3 — Bootstrap FRONTEND.md
+Read `.devbooster/rules/FRONTEND.md`.
+The file contains a bootstrap prompt. Execute it: scan the frontend stack and overwrite the file with stack-specific frontend rules.
+
+### STEP 4 — Bootstrap BACKEND.md
+Read `.devbooster/rules/BACKEND.md`.
+The file contains a bootstrap prompt. Execute it: scan the backend/API architecture and overwrite the file with stack-specific backend rules.
+
+### STEP 5 — Bootstrap COMERCIAL.md
+Read `.devbooster/rules/COMERCIAL.md`.
+The file contains a bootstrap prompt. Execute it: analyze the product's business model and overwrite the file with commercial positioning documentation.
+
+### STEP 6 — Confirm Completion
+After all files have been overwritten, report back to the user with:
+- A summary of what was detected in each domain (project, frontend, backend, commercial).
+- Any gaps or missing information that could not be auto-detected and may need manual input.
+
+---
+
+> [!NOTE]
+> This file can remain here safely. If you need to re-run the full bootstrap (e.g. after a major architectural change), simply ask your AI to "read DEVBOOSTER_INIT.md and re-execute all bootstrap steps."