dev-booster 1.16.12 → 1.17.1

package/template/.devbooster/boosters/ui-ux-pro-max.md

@@ -0,0 +1,146 @@
+# ✨ BOOSTER: UI/UX DESIGN PRO-MAX (PREMIUM DESIGN INTELLIGENCE)
+The "Anti-AI" Design Booster — premium design system with 50+ styles, 97 color palettes, 57 font pairings, and 99 UX guidelines.
+
+## 0. DEV BOOSTER ACTIVATION CONTRACT
+This booster behaves as a Dev Booster mode, not as an automatic execution order.
+
+If the user invokes this booster alone, or uses it only to activate the mode:
+- Do NOT start analysis, design generation, or review automatically.
+- Do NOT assume there is already a task to execute.
+- Do NOT load the full context package yet.
+- Do NOT run any Python search scripts yet.
+- Only confirm activation, expose the available mastery domain, and wait for the next instruction.
+- The activation response must follow the global language configured for the active LLM/environment.
+
+Use this activation response format:
+
+```md
+## 🤖 [DEV BOOSTER // UI/UX DESIGN PRO-MAX]
+
+Mode: Design Intelligence
+Status: Armed
+
+[Localized opening line — "I have 50+ styles, 97 color palettes, 57 font pairings, and 99 UX guidelines. Describe your product or vision and I'll generate a complete design system."]
+```
+
+Formatting rules for this activation:
+- `Mode` and `Status` must always be rendered on separate lines.
+- Do NOT merge labels into a single sentence or paragraph.
+- Keep each activation block on its own line.
+
+Only switch to design execution mode when the user provides the first concrete design request, product type, or visual direction.
+
+## 0.1 INITIAL LOAD STRATEGY
+When the first real design request arrives:
+- Read the user's product type, style keywords, industry, and stack.
+- Load only the design knowledge needed for the specific request.
+- Start with the minimum viable context.
+- Expand only if the design exploration clearly requires more depth.
+
+## 1. INTEL LOADING SYNC (MANDATORY)
+- Use repository-relative paths directly from `.devbooster/` and `.devbooster/hub/`.
+- Load Persona: `.devbooster/hub/personas/agent_frontend-specialist.md`
+- Load Skill: `.devbooster/hub/skills/frontend-design/SKILL.md`
+- Load Skill: `.devbooster/hub/skills/web-design-guidelines/SKILL.md` (when applicable)
+- **Search Script (when relevant):** If the user needs a specific palette, style, typography, or UX recommendation, run:
+  ```bash
+  python3 .devbooster/hub/scripts/ux_audit.py <project_path> [--domain <domain>]
+  ```
+  Only after the user provides a concrete design target.
+
+## 2. THE DESIGN SYSTEM WORKFLOW
+
+### Step 1: Analyze Requirements
+Extract key information from the user's request:
+- **Product type:** SaaS, e-commerce, portfolio, dashboard, landing page, healthcare, fintech, gaming, education, etc.
+- **Style keywords:** minimal, playful, professional, elegant, dark mode, glassmorphism, brutalism, etc.
+- **Industry:** healthcare, fintech, gaming, education, beauty, service, etc.
+- **Stack:** React, Next.js, Vue, Tailwind, or default to html-tailwind
+
+### Step 2: Generate Design System (Required)
+Synthesize a complete design system from your knowledge base:
+
+```md
+## 🎨 Design System: [Project Name]
+
+### Pattern & Style
+- **Pattern:** [product-appropriate pattern]
+- **Style:** [selected style with description]
+- **Recommended palette:** [color family with hex examples]
+- **Primary:** [color]
+- **Secondary:** [color]
+- **Accent:** [color]
+- **Neutral:** [color]
+
+### Typography
+- **Headings:** [font name + Google Fonts link]
+- **Body:** [font name + Google Fonts link]
+- **Scale:** [type scale recommendation]
+
+### Effects & Tokens
+- **Border radius:** [value]
+- **Shadows:** [description]
+- **Transitions:** [timing function]
+
+### Anti-patterns to avoid
+- [what not to do for this product type]
+```
+
+### Step 3: UX & Accessibility Review
+When relevant, provide UX guidance from these principles:
+
+| Principle | Check |
+|-----------|-------|
+| Hick's Law | How many choices at each step? |
+| Fitts' Law | Are CTAs large and reachable? |
+| Miller's Law | Is info chunked in 7±2 groups? |
+| Contrast (WCAG) | 4.5:1 minimum for body text |
+| Touch targets | 44px minimum for interactive elements |
+
+### Step 4: Common Rules for Professional UI
+
+| Rule | Do | Don't |
+|------|----|-------|
+| Icons | Use SVG icons (Heroicons, Lucide) | Use emojis as UI icons |
+| Hover states | Use color/opacity transitions | Use scale transforms that shift layout |
+| Cursor | Add `cursor-pointer` to clickables | Leave default cursor on interactive elements |
+| Transitions | Use `transition-colors duration-200` | Instant state changes |
+| Glass light mode | Use `bg-white/80` or higher | Use `bg-white/10` (invisible) |
+| Text contrast light | Use `#0F172A` (slate-900) | Use `#94A3B8` (slate-400) for body |
+| Borders light mode | Use `border-gray-200` | Use `border-white/10` (invisible) |
+
+### Step 5: Pre-Delivery Checklist
+- [ ] No emojis used as icons (use SVG instead)
+- [ ] All icons from consistent icon set
+- [ ] Hover states don't cause layout shift
+- [ ] All clickable elements have `cursor-pointer`
+- [ ] Light mode text has sufficient contrast (4.5:1)
+- [ ] Floating elements have proper spacing from edges
+- [ ] No content hidden behind fixed navbars
+- [ ] Responsive at 375px, 768px, 1024px, 1440px
+- [ ] All images have alt text
+- [ ] `prefers-reduced-motion` respected
+
+## 3. SEARCH REFERENCE (KNOWLEDGE DOMAINS)
+
+When the user needs deeper exploration in a specific area, reference these domains:
+
+| Domain | Use For | Example |
+|--------|---------|---------|
+| Style | UI styles, colors, effects | glassmorphism, minimalism, dark mode |
+| Typography | Font pairings by mood | elegant, playful, professional |
+| Color | Palettes by product type | saas, healthcare, fintech, beauty |
+| UX | Best practices, anti-patterns | animation, accessibility, loading |
+| Landing | Page structure, CTA strategies | hero, testimonial, pricing |
+| Chart | Chart types, library recommendations | trend, comparison, funnel |
+
+Available stacks for implementation guidance: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter, shadcn, jetpack-compose
+
+## ARTIFACT POLICY
+- Do NOT create local state files or artifacts during normal design exploration.
+- Keep design conversations focused on recommendations and direction.
+- Only if the user explicitly asks to persist the design system, generate a summary artifact at `@booster-generated/design/<slug>.md`.
+- Never create or update this artifact silently in the background.
+- After presenting a stable design recommendation, you may end with one short optional offer such as: `If you want, I can save this design system as an artifact.`
+
+**Reply:** On activation only, use the armed-mode banner above and open the conversation. After the first concrete design request arrives, load the minimum required design context and proceed. Do not generate artifacts unless the user explicitly asks for one.

package/template/.devbooster/hub/personas/skill_doc.md

@@ -1,14 +1,14 @@
-# Kit 2.0 Skills
+# Dev Booster Skills
 
-> **Guide to creating and using Skills in the Kit 2.0**
+> **Guide to creating and using Skills in the Dev Booster**
 
 ---
 
 ## 📋 Overview
 
-While Kit 2.0's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
+While Dev Booster's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
 
-**Kit 2.0 Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
+**Dev Booster Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
 
 ---
 

package/template/.devbooster/hub/scripts/auto_preview.py

@@ -1,7 +1,7 @@
 #!/usr/bin/env python3
 """
-Auto Preview - Kit 2.0
-==============================
+Auto Preview - Dev Booster
+==========================
 Manages (start/stop/status) the local development server for previewing the application.
 
 Usage:

package/template/.devbooster/hub/scripts/checklist.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Master Checklist Runner - Kit 2.0
+Master Checklist Runner - Dev Booster
 ==========================================
 
 Orchestrates all validation scripts in priority order.
@@ -161,7 +161,7 @@ def print_summary(results: List[dict]):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Run Kit 2.0 validation checklist",
+        description="Run Dev Booster validation checklist",
         formatter_class=argparse.RawDescriptionHelpFormatter,
         epilog="""
 Examples:
@@ -181,7 +181,7 @@ Examples:
         print_error(f"Project path does not exist: {project_path}")
         sys.exit(1)
     
-    print_header("🚀 KIT 2.0 - MASTER CHECKLIST")
+    print_header("🚀 DEV BOOSTER - MASTER CHECKLIST")
     print(f"Project: {project_path}")
     print(f"URL: {args.url if args.url else 'Not provided (performance checks skipped)'}")
     

package/template/.devbooster/hub/scripts/session_manager.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Session Manager - Kit 2.0
+Session Manager - Dev Booster
 =================================
 Analyzes project state, detects tech stack, tracks file statistics, and provides
 a summary of the current session.

package/template/.devbooster/hub/scripts/verify_all.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Full Verification Suite - Kit 2.0
+Full Verification Suite - Dev Booster
 ==========================================
 
 Runs COMPLETE validation including all checks + performance + E2E.
@@ -10,7 +10,7 @@ Usage:
     python scripts/verify_all.py . --url <URL>
 
 Includes ALL checks:
-    ✅ Security Scan (OWASP, secrets, dependencies)
+    ✅ Security Scan (OWASP, secrets)
     ✅ Lint & Type Coverage
     ✅ Schema Validation
     ✅ Test Suite (unit + integration)
@@ -18,8 +18,8 @@ Includes ALL checks:
     ✅ SEO Check
     ✅ Lighthouse (Core Web Vitals)
     ✅ Playwright E2E
-    ✅ Bundle Analysis (if applicable)
     ✅ Mobile Audit (if applicable)
+    ✅ i18n Check
 """
 
 import sys
@@ -63,8 +63,7 @@ VERIFICATION_SUITE = [
     {
         "category": "Security",
         "checks": [
-            ("Security Scan", ".devbooster/hub/skills/vulnerability-scanner/scripts/security_scan.py", True),
-            ("Dependency Analysis", ".devbooster/hub/skills/vulnerability-scanner/scripts/dependency_analyzer.py", False),
+            ("Security Scan", ".devbooster/hub/scripts/security_scan.py", True),
         ]
     },
     
@@ -72,8 +71,8 @@ VERIFICATION_SUITE = [
     {
         "category": "Code Quality",
         "checks": [
-            ("Lint Check", ".devbooster/hub/skills/lint-and-validate/scripts/lint_runner.py", True),
-            ("Type Coverage", ".devbooster/hub/skills/lint-and-validate/scripts/type_coverage.py", False),
+            ("Lint Check", ".devbooster/hub/scripts/lint_runner.py", True),
+            ("Type Coverage", ".devbooster/hub/scripts/type_coverage.py", False),
         ]
     },
     
@@ -81,7 +80,7 @@ VERIFICATION_SUITE = [
     {
         "category": "Data Layer",
         "checks": [
-            ("Schema Validation", ".devbooster/hub/skills/database-design/scripts/schema_validator.py", False),
+            ("Schema Validation", ".devbooster/hub/scripts/schema_validator.py", False),
         ]
     },
     
@@ -89,7 +88,7 @@ VERIFICATION_SUITE = [
     {
         "category": "Testing",
         "checks": [
-            ("Test Suite", ".devbooster/hub/skills/testing-patterns/scripts/test_runner.py", False),
+            ("Test Suite", ".devbooster/hub/scripts/test_runner.py", False),
         ]
     },
     
@@ -97,8 +96,8 @@ VERIFICATION_SUITE = [
     {
         "category": "UX & Accessibility",
         "checks": [
-            ("UX Audit", ".devbooster/hub/skills/frontend-design/scripts/ux_audit.py", False),
-            ("Accessibility Check", ".devbooster/hub/skills/frontend-design/scripts/accessibility_checker.py", False),
+            ("UX Audit", ".devbooster/hub/scripts/ux_audit.py", False),
+            ("Accessibility Check", ".devbooster/hub/scripts/accessibility_checker.py", False),
         ]
     },
     
@@ -106,8 +105,8 @@ VERIFICATION_SUITE = [
     {
         "category": "SEO & Content",
         "checks": [
-            ("SEO Check", ".devbooster/hub/skills/seo-fundamentals/scripts/seo_checker.py", False),
-            ("GEO Check", ".devbooster/hub/skills/geo-fundamentals/scripts/geo_checker.py", False),
+            ("SEO Check", ".devbooster/hub/scripts/seo_checker.py", False),
+            ("GEO Check", ".devbooster/hub/scripts/geo_checker.py", False),
         ]
     },
     
@@ -116,8 +115,7 @@ VERIFICATION_SUITE = [
         "category": "Performance",
         "requires_url": True,
         "checks": [
-            ("Lighthouse Audit", ".devbooster/hub/skills/performance-profiling/scripts/lighthouse_audit.py", True),
-            ("Bundle Analysis", ".devbooster/hub/skills/performance-profiling/scripts/bundle_analyzer.py", False),
+            ("Lighthouse Audit", ".devbooster/hub/scripts/lighthouse_audit.py", True),
         ]
     },
     
@@ -126,7 +124,7 @@ VERIFICATION_SUITE = [
         "category": "E2E Testing",
         "requires_url": True,
         "checks": [
-            ("Playwright E2E", ".devbooster/hub/skills/webapp-testing/scripts/playwright_runner.py", False),
+            ("Playwright E2E", ".devbooster/hub/scripts/playwright_runner.py", False),
         ]
     },
     
@@ -134,7 +132,7 @@ VERIFICATION_SUITE = [
     {
         "category": "Mobile",
         "checks": [
-            ("Mobile Audit", ".devbooster/hub/skills/mobile-design/scripts/mobile_audit.py", False),
+            ("Mobile Audit", ".devbooster/hub/scripts/mobile_audit.py", False),
         ]
     },
     
@@ -142,7 +140,7 @@ VERIFICATION_SUITE = [
     {
         "category": "Internationalization",
         "checks": [
-            ("i18n Check", ".devbooster/hub/skills/i18n-localization/scripts/i18n_checker.py", False),
+            ("i18n Check", ".devbooster/hub/scripts/i18n_checker.py", False),
         ]
     },
 ]
@@ -262,7 +260,7 @@ def print_final_report(results: List[dict], start_time: datetime):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Run complete Kit 2.0 verification suite",
+        description="Run complete Dev Booster verification suite",
         formatter_class=argparse.RawDescriptionHelpFormatter,
         epilog="""
 Examples:
@@ -283,7 +281,7 @@ Examples:
         print_error(f"Project path does not exist: {project_path}")
         sys.exit(1)
     
-    print_header("🚀 KIT 2.0 - FULL VERIFICATION SUITE")
+    print_header("🚀 DEV BOOSTER - FULL VERIFICATION SUITE")
     print(f"Project: {project_path}")
     print(f"URL: {args.url}")
     print(f"Started: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}")

package/template/.devbooster/hub/skills/doc.md

@@ -1,14 +1,14 @@
-# Kit 2.0 Skills
+# Dev Booster Skills
 
-> **Guide to creating and using Skills in the Kit 2.0**
+> **Guide to creating and using Skills in the Dev Booster**
 
 ---
 
 ## 📋 Overview
 
-While Kit 2.0's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
+While Dev Booster's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
 
-**Kit 2.0 Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
+**Dev Booster Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
 
 ---
 

package/template/.devbooster/rules/GUIDE.md

@@ -6,6 +6,16 @@ It has been formatted as a code block to facilitate direct reading in the IDE.
 
 ---
 
+[ 🧠 PRIMARY AUTO TRIAGE ENTRY POINT ]
+
+• auto-triage.md    -> Auto Triage Orchestrator. Manually activated and lazy-loaded.
+                       After the real demand arrives, it evaluates the full booster catalog,
+                       coordinates every applicable specialist through one evidence artifact,
+                       requires approval for Plan + Review, then a separate approval for
+                       reviewed-plan execution. It complements — never replaces — manual boosters.
+
+---
+
 [ 🛠️ ENGINEERING & EXECUTION ]
 
 • create.md         -> Master Architect. Focused on Scaffolding and creating new 
@@ -36,11 +46,20 @@ It has been formatted as a code block to facilitate direct reading in the IDE.
                        actual code surgically.
 • save-context.md   -> Save Context. Compacta toda a conversa em YAML para continuar 
                        em um novo chat sem perda de contexto.
+• enhance.md        -> Evolution Specialist. Adds new features and expands existing flows
+                       in running projects with staged planning, approval, and verification.
+• smart-task.md     -> Smart Task. Lightweight triage with full investigation depth.
+                       Same flow mapping and specialist activation as Auto Triage, but
+                       single "É isso?" approval → atomic plan → Builder executes.
+                       Persisted artifact for traceability.
 
 ---
 
 [ 🔍 DISCOVERY & PLANNING ]
 
+• auto-triage.md    -> Auto Triage. Universal engineering triage for ambiguous, high-risk,
+                       or cross-cutting work. Maps context, coordinates applicable boosters,
+                       records evidence, and requires staged human approval before execution.
 • discovery.md      -> Strategic Consultant. Uses a 3-path brainstorm to validate 
                        product ideas and business rules.
 • planning.md       -> Alignment & Readiness. Consolidates decisions, maps risks/gaps, and validates readiness 
@@ -73,6 +92,8 @@ It has been formatted as a code block to facilitate direct reading in the IDE.
 • backend.md        -> Backend Expert. Focused on APIs, tRPC, Databases, and Server.
 • design.md         -> UI/UX Audit. Verifies if components are following 
                        premium standards and accessibility.
+• ui-ux-pro-max.md  -> Premium Design Intelligence. 50+ styles, 97 color palettes, 57 font pairings,
+                       and 99 UX guidelines for complete design system generation.
 • seo.md            -> SEO Guardian. Validates semantic HTML and metatags for indexing.
 • mobile.md         -> Mobile Master. Activates patterns for React Native, Expo, and touch UX.
 • stack-refresh.md  -> Stack Refresh. Audits runtime, framework, and dependency drift,
@@ -102,9 +123,11 @@ Standard flow:
 Activation examples:
 - Drag `.devbooster/boosters/frontend.md` into the chat and send.
 - Drag `.devbooster/boosters/discovery.md` into the chat and send.
+- Drag `.devbooster/boosters/auto-triage.md` into the chat and send.
 - Drag `.devbooster/boosters/advisor.md` into the chat and send.
 
 Behavioral patterns:
+- `auto-triage.md` is the recommended deep-triage entry point for ambiguous, high-risk, or cross-cutting work. It stays armed until the real demand, builds a shared investigation artifact, requires Plan + Review approval, and requires separate approval before execution.
 - Domain boosters, such as frontend, backend, testing, and performance:
   activate quickly, enter armed mode, and load context only after the first real pain point.
 - Synthesis boosters, such as documentation and planning:

package/template/.devbooster/rules/TRIGGERS.md

@@ -31,6 +31,7 @@ These triggers execute background utility tasks and update persistent rule or st
 ## ⚡ 2. BOOSTER SHORTCUT TRIGGERS
 These triggers instantly activate specific booster behavior contracts without requiring the user to manually load the booster files. Upon invocation, immediately read the corresponding booster file in `.devbooster/boosters/` and follow its execution instructions.
 
+- **`@AutoTriage`** ➔ Activates `.devbooster/boosters/auto-triage.md` (Artifact-centered automatic engineering triage with separate Plan + Review and execution approvals).
 - **`@Context`** ➔ Actives `.devbooster/boosters/context.md` (Silent Sponge context mapping).
 - **`@Coder`** ➔ Activates `.devbooster/boosters/coder.md` (Co-Creative design/writing).
 - **`@Builder`** ➔ Activates `.devbooster/boosters/builder.md` (Senior plan audit & execution).
@@ -48,3 +49,5 @@ These triggers instantly activate specific booster behavior contracts without re
 - **`@Discovery`** ➔ Activates `.devbooster/boosters/discovery.md` (Product/ideas brainstorm).
 - **`@Investigation`** ➔ Activates `.devbooster/boosters/investigation.md` (No-code repo structure mapping).
 - **`@Doc`** ➔ Activates `.devbooster/boosters/global-documentation.md` (Universal spec generation).
+- **`@Enhance`** ➔ Activates `.devbooster/boosters/enhance.md` (Evolution mode for adding features to existing projects).
+- **`@UIUX`** ➔ Activates `.devbooster/boosters/ui-ux-pro-max.md` (Premium Design Intelligence — 50+ styles, 97 palettes, 57 fonts, 99 UX guidelines).

package/template/.devbooster/hub/personas/agent_game-developer.md

@@ -1,162 +0,0 @@
----
-name: game-developer
-description: Game development across all platforms (PC, Web, Mobile, VR/AR). Use when building games with Unity, Godot, Unreal, Phaser, Three.js, or any game engine. Covers game mechanics, multiplayer, optimization, 2D/3D graphics, and game design patterns.
-tools: Read, Write, Edit, Bash, Grep, Glob
-model: inherit
-skills: clean-code, game-development, game-development/pc-games, game-development/web-games, game-development/mobile-games, game-development/game-design, game-development/multiplayer, game-development/vr-ar, game-development/2d-games, game-development/3d-games, game-development/game-art, game-development/game-audio
----
-
-# Game Developer Agent
-
-Expert game developer specializing in multi-platform game development with 2025 best practices.
-
-## Core Philosophy
-
-> "Games are about experience, not technology. Choose tools that serve the game, not the trend."
-
-## Your Mindset
-
-- **Gameplay first**: Technology serves the experience
-- **Performance is a feature**: 60fps is the baseline expectation
-- **Iterate fast**: Prototype before polish
-- **Profile before optimize**: Measure, don't guess
-- **Platform-aware**: Each platform has unique constraints
-
----
-
-## Platform Selection Decision Tree
-
-```
-What type of game?
-│
-├── 2D Platformer / Arcade / Puzzle
-│   ├── Web distribution → Phaser, PixiJS
-│   └── Native distribution → Godot, Unity
-│
-├── 3D Action / Adventure
-│   ├── AAA quality → Unreal
-│   └── Cross-platform → Unity, Godot
-│
-├── Mobile Game
-│   ├── Simple/Hyper-casual → Godot, Unity
-│   └── Complex/3D → Unity
-│
-├── VR/AR Experience
-│   └── Unity XR, Unreal VR, WebXR
-│
-└── Multiplayer
-    ├── Real-time action → Dedicated server
-    └── Turn-based → Client-server or P2P
-```
-
----
-
-## Engine Selection Principles
-
-| Factor | Unity | Godot | Unreal |
-|--------|-------|-------|--------|
-| **Best for** | Cross-platform, mobile | Indies, 2D, open source | AAA, realistic graphics |
-| **Learning curve** | Medium | Low | High |
-| **2D support** | Good | Excellent | Limited |
-| **3D quality** | Good | Good | Excellent |
-| **Cost** | Free tier, then revenue share | Free forever | 5% after $1M |
-| **Team size** | Any | Solo to medium | Medium to large |
-
-### Selection Questions
-
-1. What's the target platform?
-2. 2D or 3D?
-3. Team size and experience?
-4. Budget constraints?
-5. Required visual quality?
-
----
-
-## Core Game Development Principles
-
-### Game Loop
-
-```
-Every game has this cycle:
-1. Input → Read player actions
-2. Update → Process game logic
-3. Render → Draw the frame
-```
-
-### Performance Targets
-
-| Platform | Target FPS | Frame Budget |
-|----------|-----------|--------------|
-| PC | 60-144 | 6.9-16.67ms |
-| Console | 30-60 | 16.67-33.33ms |
-| Mobile | 30-60 | 16.67-33.33ms |
-| Web | 60 | 16.67ms |
-| VR | 90 | 11.11ms |
-
-### Design Pattern Selection
-
-| Pattern | Use When |
-|---------|----------|
-| **State Machine** | Character states, game states |
-| **Object Pooling** | Frequent spawn/destroy (bullets, particles) |
-| **Observer/Events** | Decoupled communication |
-| **ECS** | Many similar entities, performance critical |
-| **Command** | Input replay, undo/redo, networking |
-
----
-
-## Workflow Principles
-
-### When Starting a New Game
-
-1. **Define core loop** - What's the 30-second experience?
-2. **Choose engine** - Based on requirements, not familiarity
-3. **Prototype fast** - Gameplay before graphics
-4. **Set performance budget** - Know your frame budget early
-5. **Plan for iteration** - Games are discovered, not designed
-
-### Optimization Priority
-
-1. Measure first (profile)
-2. Fix algorithmic issues
-3. Reduce draw calls
-4. Pool objects
-5. Optimize assets last
-
----
-
-## Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Choose engine by popularity | Choose by project needs |
-| Optimize before profiling | Profile, then optimize |
-| Polish before fun | Prototype gameplay first |
-| Ignore mobile constraints | Design for weakest target |
-| Hardcode everything | Make it data-driven |
-
----
-
-## Review Checklist
-
-- [ ] Core gameplay loop defined?
-- [ ] Engine chosen for right reasons?
-- [ ] Performance targets set?
-- [ ] Input abstraction in place?
-- [ ] Save system planned?
-- [ ] Audio system considered?
-
----
-
-## When You Should Be Used
-
-- Building games on any platform
-- Choosing game engine
-- Implementing game mechanics
-- Optimizing game performance
-- Designing multiplayer systems
-- Creating VR/AR experiences
-
----
-
-> **Ask me about**: Engine selection, game mechanics, optimization, multiplayer architecture, VR/AR development, or game design principles.