dev-booster 1.16.12 → 1.17.1

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

@@ -1,222 +0,0 @@
-#!/usr/bin/env python3
-"""
-Conversion Script: React Best Practices → .devbooster Format
-Merges 59 individual rules into 8 grouped section files
-"""
-
-import os
-import re
-from pathlib import Path
-from typing import Dict, List, Tuple
-
-# Section metadata from _sections.md
-SECTIONS = {
-    'async': {
-        'number': 1,
-        'title': 'Eliminating Waterfalls',
-        'impact': 'CRITICAL',
-        'description': 'Waterfalls are the #1 performance killer. Each sequential await adds full network latency. Eliminating them yields the largest gains.'
-    },
-    'bundle': {
-        'number': 2,
-        'title': 'Bundle Size Optimization',
-        'impact': 'CRITICAL',
-        'description': 'Reducing initial bundle size improves Time to Interactive and Largest Contentful Paint.'
-    },
-    'server': {
-        'number': 3,
-        'title': 'Server-Side Performance',
-        'impact': 'HIGH',
-        'description': 'Optimizing server-side rendering and data fetching eliminates server-side waterfalls and reduces response times.'
-    },
-    'client': {
-        'number': 4,
-        'title': 'Client-Side Data Fetching',
-        'impact': 'MEDIUM-HIGH',
-        'description': 'Automatic deduplication and efficient data fetching patterns reduce redundant network requests.'
-    },
-    'rerender': {
-        'number': 5,
-        'title': 'Re-render Optimization',
-        'impact': 'MEDIUM',
-        'description': 'Reducing unnecessary re-renders minimizes wasted computation and improves UI responsiveness.'
-    },
-    'rendering': {
-        'number': 6,
-        'title': 'Rendering Performance',
-        'impact': 'MEDIUM',
-        'description': 'Optimizing the rendering process reduces the work the browser needs to do.'
-    },
-    'js': {
-        'number': 7,
-        'title': 'JavaScript Performance',
-        'impact': 'LOW-MEDIUM',
-        'description': 'Micro-optimizations for hot paths can add up to meaningful improvements.'
-    },
-    'advanced': {
-        'number': 8,
-        'title': 'Advanced Patterns',
-        'impact': 'VARIABLE',
-        'description': 'Advanced patterns for specific cases that require careful implementation.'
-    }
-}
-
-
-def parse_frontmatter(content: str) -> Tuple[Dict, str]:
-    """Parse markdown frontmatter and body"""
-    if not content.startswith('---'):
-        return {}, content
-
-    parts = content.split('---', 2)
-    if len(parts) < 3:
-        return {}, content
-
-    # Parse YAML frontmatter manually (simple key: value)
-    frontmatter = {}
-    for line in parts[1].strip().split('\n'):
-        if ':' in line:
-            key, value = line.split(':', 1)
-            frontmatter[key.strip()] = value.strip()
-
-    body = parts[2].strip()
-    return frontmatter, body
-
-
-def parse_rule_file(filepath: Path) -> Dict:
-    """Parse a single rule file"""
-    with open(filepath, 'r', encoding='utf-8') as f:
-        content = f.read()
-
-    frontmatter, body = parse_frontmatter(content)
-
-    # Extract prefix from filename
-    filename = filepath.stem
-    prefix = filename.split('-')[0]
-
-    return {
-        'filename': filepath.name,
-        'prefix': prefix,
-        'title': frontmatter.get('title', filename),
-        'impact': frontmatter.get('impact', ''),
-        'impactDescription': frontmatter.get('impactDescription', ''),
-        'tags': frontmatter.get('tags', ''),
-        'body': body,
-        'frontmatter': frontmatter
-    }
-
-
-def group_rules_by_section(rules_dir: Path) -> Dict[str, List[Dict]]:
-    """Group all rules by their section prefix"""
-    grouped = {prefix: [] for prefix in SECTIONS.keys()}
-
-    for rule_file in sorted(rules_dir.glob('*.md')):
-        # Skip special files
-        if rule_file.name.startswith('_'):
-            continue
-
-        rule = parse_rule_file(rule_file)
-        prefix = rule['prefix']
-
-        if prefix in grouped:
-            grouped[prefix].append(rule)
-        else:
-            print(f"[WARNING] Unknown prefix '{prefix}' in file: {rule_file.name}")
-
-    return grouped
-
-
-def generate_section_file(section_prefix: str, rules: List[Dict], output_dir: Path):
-    """Generate a merged section file"""
-    if not rules:
-        print(f"[WARNING] No rules found for section: {section_prefix}")
-        return
-
-    section_meta = SECTIONS[section_prefix]
-    section_num = section_meta['number']
-    section_title = section_meta['title']
-    impact = section_meta['impact']
-    description = section_meta['description']
-
-    # Sort rules by title
-    rules.sort(key=lambda r: r['title'])
-
-    # Build content
-    content = f"""# {section_num}. {section_title}
-
-> **Impact:** {impact}
-> **Focus:** {description}
-
----
-
-## Overview
-
-This section contains **{len(rules)} rules** focused on {section_title.lower()}.
-
-"""
-
-    # Add each rule
-    for i, rule in enumerate(rules, 1):
-        rule_id = f"{section_num}.{i}"
-        title = rule['title']
-        rule_impact = rule['impact']
-        tags = rule['tags']
-        body = rule['body']
-
-        content += f"""---
-
-## Rule {rule_id}: {title}
-
-"""
-
-        if rule_impact:
-            content += f"**Impact:** {rule_impact}  \n"
-
-        if tags:
-            content += f"**Tags:** {tags}  \n"
-
-        content += f"\n{body}\n\n"
-
-    # Write file
-    output_file = output_dir / f"{section_num}-{section_prefix}-{section_title.lower().replace(' ', '-')}.md"
-    output_file.write_text(content, encoding='utf-8')
-    print(f"[OK] Generated: {output_file.name} ({len(rules)} rules)")
-
-
-def main():
-    """Main conversion function"""
-    # Paths
-    base_dir = Path(__file__).parent.parent.parent.parent.parent
-    rules_dir = base_dir / "others/agent-skills/skills/react-best-practices/rules"
-    output_dir = base_dir / ".zed/prompts/skill_react-best-practices"
-
-    print(f"[*] Reading rules from: {rules_dir}")
-    print(f"[*] Output to: {output_dir}")
-    print()
-
-    # Check if rules directory exists
-    if not rules_dir.exists():
-        print(f"[ERROR] Rules directory not found: {rules_dir}")
-        return
-
-    # Group rules
-    print("[*] Grouping rules by section...")
-    grouped_rules = group_rules_by_section(rules_dir)
-
-    # Stats
-    total_rules = sum(len(rules) for rules in grouped_rules.values())
-    print(f"[*] Found {total_rules} total rules")
-    print()
-
-    # Generate section files
-    print("[*] Generating section files...")
-    for section_prefix in SECTIONS.keys():
-        rules = grouped_rules[section_prefix]
-        generate_section_file(section_prefix, rules, output_dir)
-
-    print()
-    print("[SUCCESS] Conversion complete!")
-    print(f"[*] Generated 8 section files from {total_rules} rules")
-
-
-if __name__ == '__main__':
-    main()

package/template/.devbooster/hub/skills/behavioral-modes/SKILL.md

@@ -1,242 +0,0 @@
----
-name: behavioral-modes
-description: AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
-allowed-tools: Read, Glob, Grep
----
-
-# Behavioral Modes - Adaptive AI Operating Modes
-
-## Purpose
-This skill defines distinct behavioral modes that optimize AI performance for specific tasks. Modes change how the AI approaches problems, communicates, and prioritizes.
-
----
-
-## Available Modes
-
-### 1. 🧠 BRAINSTORM Mode
-
-**When to use:** Early project planning, feature ideation, architecture decisions
-
-**Behavior:**
-- Ask clarifying questions before assumptions
-- Offer multiple alternatives (at least 3)
-- Think divergently - explore unconventional solutions
-- No code yet - focus on ideas and options
-- Use visual diagrams (mermaid) to explain concepts
-
-**Output style:**
-```
-"Let's explore this together. Here are some approaches:
-
-Option A: [description]
-  ✅ Pros: ...
-  ❌ Cons: ...
-
-Option B: [description]
-  ✅ Pros: ...
-  ❌ Cons: ...
-
-What resonates with you? Or should we explore a different direction?"
-```
-
----
-
-### 2. ⚡ IMPLEMENT Mode
-
-**When to use:** Writing code, building features, executing plans
-
-**Behavior:**
-- **CRITICAL: Use `clean-code` skill standards** - concise, direct, no verbose explanations
-- Fast execution - minimize questions
-- Use established patterns and best practices
-- Write complete, production-ready code
-- Include error handling and edge cases
-- **NO tutorial-style explanations** - just code
-- **NO unnecessary comments** - let code self-document
-- **NO over-engineering** - solve the problem directly
-- **NO RUSHING** - Quality > Speed. Read ALL references before coding.
-
-**Output style:**
-```
-[Code block]
-
-[Brief summary, max 1-2 sentences]
-```
-
-**NOT:**
-```
-"Building [feature]...
-
-✓ Created [file1]
-✓ Created [file2]
-✓ Updated [file3]
-
-[long explanation]
-
-Run `npm run dev` to test."
-```
-
----
-
-### 3. 🔍 DEBUG Mode
-
-**When to use:** Fixing bugs, troubleshooting errors, investigating issues
-
-**Behavior:**
-- Ask for error messages and reproduction steps
-- Think systematically - check logs, trace data flow
-- Form hypothesis → test → verify
-- Explain the root cause, not just the fix
-- Prevent future occurrences
-
-**Output style:**
-```
-"Investigating...
-
-🔍 Symptom: [what's happening]
-🎯 Root cause: [why it's happening]
-✅ Fix: [the solution]
-🛡️ Prevention: [how to avoid in future]
-```
-
----
-
-### 4. 📋 REVIEW Mode
-
-**When to use:** Code review, architecture review, security audit
-
-**Behavior:**
-- Be thorough but constructive
-- Categorize by severity (Critical/High/Medium/Low)
-- Explain the "why" behind suggestions
-- Offer improved code examples
-- Acknowledge what's done well
-
-**Output style:**
-```
-## Code Review: [file/feature]
-
-### 🔴 Critical
-- [issue with explanation]
-
-### 🟠 Improvements
-- [suggestion with example]
-
-### 🟢 Good
-- [positive observation]
-```
-
----
-
-### 5. 📚 TEACH Mode
-
-**When to use:** Explaining concepts, documentation, onboarding
-
-**Behavior:**
-- Explain from fundamentals
-- Use analogies and examples
-- Progress from simple to complex
-- Include practical exercises
-- Check understanding
-
-**Output style:**
-```
-## Understanding [Concept]
-
-### What is it?
-[Simple explanation with analogy]
-
-### How it works
-[Technical explanation with diagram]
-
-### Example
-[Code example with comments]
-
-### Try it yourself
-[Exercise or task]
-```
-
----
-
-### 6. 🚀 SHIP Mode
-
-**When to use:** Production deployment, final polish, release preparation
-
-**Behavior:**
-- Focus on stability over features
-- Check for missing error handling
-- Verify environment configs
-- Run all tests
-- Create deployment checklist
-
-**Output style:**
-```
-## Pre-Ship Checklist
-
-### ✅ Code Quality
-- [ ] No TypeScript errors
-- [ ] ESLint passing
-- [ ] All tests passing
-
-### ✅ Security
-- [ ] No exposed secrets
-- [ ] Input validation complete
-
-### ✅ Performance
-- [ ] Bundle size acceptable
-- [ ] No console.logs
-
-### 🚀 Ready to deploy
-```
-
----
-
-## Mode Detection
-
-The AI should automatically detect the appropriate mode based on:
-
-| Trigger | Mode |
-|---------|------|
-| "what if", "ideas", "options" | BRAINSTORM |
-| "build", "create", "add" | IMPLEMENT |
-| "not working", "error", "bug" | DEBUG |
-| "review", "check", "audit" | REVIEW |
-| "explain", "how does", "learn" | TEACH |
-| "deploy", "release", "production" | SHIP |
-
----
-
-## Multi-Agent Collaboration Patterns (2025)
-
-Modern architectures optimized for agent-to-agent collaboration:
-
-### 1. 🔭 EXPLORE Mode
-**Role:** Discovery and Analysis (Explorer Agent)
-**Behavior:** Socratic questioning, deep-dive code reading, dependency mapping.
-**Output:** `discovery-report.json`, architectural visualization.
-
-### 2. 🗺️ PLAN-EXECUTE-CRITIC (PEC)
-Cyclic mode transitions for high-complexity tasks:
-1. **Planner:** Decomposes the task into atomic steps (`task.md`).
-2. **Executor:** Performs the actual coding (`IMPLEMENT`).
-3. **Critic:** Reviews the code, performs security and performance checks (`REVIEW`).
-
-### 3. 🧠 MENTAL MODEL SYNC
-Behavior for creating and loading "Mental Model" summaries to preserve context between sessions.
-
----
-
-## Combining Modes
-
----
-
-## Manual Mode Switching
-
-Users can explicitly request a mode:
-
-```
-/brainstorm new feature ideas
-/implement the user profile page
-/debug why login fails
-/review this pull request
-```

package/template/.devbooster/hub/skills/game-development/2d-games/SKILL.md

@@ -1,119 +0,0 @@
----
-name: 2d-games
-description: 2D game development principles. Sprites, tilemaps, physics, camera.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# 2D Game Development
-
-> Principles for 2D game systems.
-
----
-
-## 1. Sprite Systems
-
-### Sprite Organization
-
-| Component | Purpose |
-|-----------|---------|
-| **Atlas** | Combine textures, reduce draw calls |
-| **Animation** | Frame sequences |
-| **Pivot** | Rotation/scale origin |
-| **Layering** | Z-order control |
-
-### Animation Principles
-
-- Frame rate: 8-24 FPS typical
-- Squash and stretch for impact
-- Anticipation before action
-- Follow-through after action
-
----
-
-## 2. Tilemap Design
-
-### Tile Considerations
-
-| Factor | Recommendation |
-|--------|----------------|
-| **Size** | 16x16, 32x32, 64x64 |
-| **Auto-tiling** | Use for terrain |
-| **Collision** | Simplified shapes |
-
-### Layers
-
-| Layer | Content |
-|-------|---------|
-| Background | Non-interactive scenery |
-| Terrain | Walkable ground |
-| Props | Interactive objects |
-| Foreground | Parallax overlay |
-
----
-
-## 3. 2D Physics
-
-### Collision Shapes
-
-| Shape | Use Case |
-|-------|----------|
-| Box | Rectangular objects |
-| Circle | Balls, rounded |
-| Capsule | Characters |
-| Polygon | Complex shapes |
-
-### Physics Considerations
-
-- Pixel-perfect vs physics-based
-- Fixed timestep for consistency
-- Layers for filtering
-
----
-
-## 4. Camera Systems
-
-### Camera Types
-
-| Type | Use |
-|------|-----|
-| **Follow** | Track player |
-| **Look-ahead** | Anticipate movement |
-| **Multi-target** | Two-player |
-| **Room-based** | Metroidvania |
-
-### Screen Shake
-
-- Short duration (50-200ms)
-- Diminishing intensity
-- Use sparingly
-
----
-
-## 5. Genre Patterns
-
-### Platformer
-
-- Coyote time (leniency after edge)
-- Jump buffering
-- Variable jump height
-
-### Top-down
-
-- 8-directional or free movement
-- Aim-based or auto-aim
-- Consider rotation or not
-
----
-
-## 6. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Separate textures | Use atlases |
-| Complex collision shapes | Simplified collision |
-| Jittery camera | Smooth following |
-| Pixel-perfect on physics | Choose one approach |
-
----
-
-> **Remember:** 2D is about clarity. Every pixel should communicate.

package/template/.devbooster/hub/skills/game-development/3d-games/SKILL.md

@@ -1,135 +0,0 @@
----
-name: 3d-games
-description: 3D game development principles. Rendering, shaders, physics, cameras.
-allowed-tools: Read, Write, Edit, Glob, Grep
----
-
-# 3D Game Development
-
-> Principles for 3D game systems.
-
----
-
-## 1. Rendering Pipeline
-
-### Stages
-
-```
-1. Vertex Processing → Transform geometry
-2. Rasterization → Convert to pixels
-3. Fragment Processing → Color pixels
-4. Output → To screen
-```
-
-### Optimization Principles
-
-| Technique | Purpose |
-|-----------|---------|
-| **Frustum culling** | Don't render off-screen |
-| **Occlusion culling** | Don't render hidden |
-| **LOD** | Less detail at distance |
-| **Batching** | Combine draw calls |
-
----
-
-## 2. Shader Principles
-
-### Shader Types
-
-| Type | Purpose |
-|------|---------|
-| **Vertex** | Position, normals |
-| **Fragment/Pixel** | Color, lighting |
-| **Compute** | General computation |
-
-### When to Write Custom Shaders
-
-- Special effects (water, fire, portals)
-- Stylized rendering (toon, sketch)
-- Performance optimization
-- Unique visual identity
-
----
-
-## 3. 3D Physics
-
-### Collision Shapes
-
-| Shape | Use Case |
-|-------|----------|
-| **Box** | Buildings, crates |
-| **Sphere** | Balls, quick checks |
-| **Capsule** | Characters |
-| **Mesh** | Terrain (expensive) |
-
-### Principles
-
-- Simple colliders, complex visuals
-- Layer-based filtering
-- Raycasting for line-of-sight
-
----
-
-## 4. Camera Systems
-
-### Camera Types
-
-| Type | Use |
-|------|-----|
-| **Third-person** | Action, adventure |
-| **First-person** | Immersive, FPS |
-| **Isometric** | Strategy, RPG |
-| **Orbital** | Inspection, editors |
-
-### Camera Feel
-
-- Smooth following (lerp)
-- Collision avoidance
-- Look-ahead for movement
-- FOV changes for speed
-
----
-
-## 5. Lighting
-
-### Light Types
-
-| Type | Use |
-|------|-----|
-| **Directional** | Sun, moon |
-| **Point** | Lamps, torches |
-| **Spot** | Flashlight, stage |
-| **Ambient** | Base illumination |
-
-### Performance Consideration
-
-- Real-time shadows are expensive
-- Bake when possible
-- Shadow cascades for large worlds
-
----
-
-## 6. Level of Detail (LOD)
-
-### LOD Strategy
-
-| Distance | Model |
-|----------|-------|
-| Near | Full detail |
-| Medium | 50% triangles |
-| Far | 25% or billboard |
-
----
-
-## 7. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Mesh colliders everywhere | Simple shapes |
-| Real-time shadows on mobile | Baked or blob shadows |
-| One LOD for all distances | Distance-based LOD |
-| Unoptimized shaders | Profile and simplify |
-
----
-
-> **Remember:** 3D is about illusion. Create the impression of detail, not the detail itself.