bodangren

Use this skill to create or update the root AGENTS.md file to register AgenticDev skills for AI agent discovery. Triggers include "register AgenticDev", "update AGENTS.md", "setup agent guide", or initializing a new project.

Use this skill at the beginning of any session or when needing to understand available project documentation. Provides just-in-time context by scanning YAML frontmatter from all markdown files in the docs/ directory without loading full content.

Use this skill to validate that Markdown files are in standard locations. Scans for .md files outside of predefined allowed directories and outputs warnings to prevent documentation sprawl. Triggers include "validate docs", "check markdown locations", or as part of quality checks.

Use this skill for early-stage project planning. It leverages the Gemini CLI to generate high-quality first drafts of Product Briefs, Research Documents, and full PRDs, guiding users from idea to validated requirements. Triggers include "create PRD", "product brief", or "validate requirements".

Use this skill when starting a new project or adding AgenticDev to an existing project. Scaffolds the directory structure (docs/specs, docs/changes) and configuration files needed for the spec-driven development workflow.

Use this skill to migrate existing projects to the AgenticDev structure. It uses an AI-powered analysis to intelligently discover, categorize, and migrate documentation, generate rich frontmatter, and preserve git history.

Use this skill to discover all available AgenticDev skills and their capabilities. Provides a bootstrap context for AI agents by listing all skills, their descriptions, and script paths from the .claude/skills/ directory.

Use this skill to propose changes via the Spec PR process. It uses the Gemini CLI to generate high-quality draft specifications and to analyze PR feedback, accelerating the spec-driven development workflow. Triggers include "create spec" or "propose change".

Replace primitive 3D shapes with real GLB models — animated characters, world props, buildings, and scenery for Three.js games. Use when the user says "add 3D models", "replace the boxes with real models", "add GLB assets", or "make the 3D game look real". For 2D pixel art, use add-assets instead. Do NOT use for 2D pixel art (use add-assets) or gameplay changes (use add-feature).

Record a high-FPS autonomous promo video of a Phaser game using Playwright. Triggers on: promo video, gameplay recording, marketing video, game capture.

Add Playwright QA tests to a game — visual regression, gameplay verification, and performance. Use when the user says "add tests", "test my game", "add QA", "check for bugs", or "add visual regression tests". Do NOT use for manual playtesting or gameplay design.

Review an existing game codebase for architecture, performance, and best practices. Use when the user says "review my game", "code review", "check my game architecture", "is my game well structured", or "audit my game code". Do NOT use for making changes — this is read-only analysis. Use improve-game to implement fixes.

Build 3D browser games with Three.js using event-driven modular architecture. Use when creating a new 3D game, adding 3D game features, setting up Three.js scenes, or working on any Three.js game project.

Build vocabulary learning browser games with Next.js, React, and Konva. Use when creating a new vocabulary game, adding features to existing vocab games, or working with the advantage-games codebase.

Generate photorealistic 3D worlds and environments with the World Labs Marble API — Gaussian Splat scenes from text prompts or reference images. Use when the user says "generate a 3D world", "create an environment", "make a 3D scene", or "use World Labs". Requires WLT_API_KEY environment variable.

Build vocabulary learning games using React-Konva canvas architecture with strict TDD workflow and phased development. Use this skill when the user wants to: (1) Create a new vocabulary game from scratch, (2) Resume work on an existing game track, (3) Build a mini-game for language learning. Triggers include: "create a vocab game", "build a new game", "make a vocabulary game", "resume game development", "/vocab-game-builder", "new mini-game".

Write or revise a student-facing Excel lesson for Math for Business Operations. Use for lessons 4 or 5 to 6 when the lesson teaches a new Excel tool, workbook pattern, or automation move before project rehearsal. This skill is for business-pressure hooks, explicit tool anatomy, safe simulator practice, workbook build sprints, workbook audit/explanation, and reflection. Do not use for lesson 1 launch lessons, lesson 2 to 3 or 4 accounting-principles lessons, lesson 7 project rehearsal, or lesson 8-10 project lessons.

Write or revise a student-facing accounting-principles lesson for Math for Business Operations. Use for lessons 2-4 when the lesson teaches an accounting concept, valuation method, or manual procedure before Excel automation. This skill is for explicit instruction, scaffolded practice, algorithmic phase-4 mastery practice, MCQ exit tickets, and reflection. Do not use for launch lessons, Excel-principles lessons, or project lessons.

Write or revise a student-facing group project lesson for Math for Business Operations. Use for lessons 8-10 or any milestone-style project lesson where each group works with its own assigned dataset while keeping the same workbook structure established in the project rehearsal lesson. This skill is for project kickoff, group workbook setup, build milestones, testing, recommendation writing, peer critique, rehearsal, presentation readiness, and final handoff. Do not use for launch lessons, accounting-principles lessons, Excel build lessons, or shared-data project rehearsal lessons.

Write or revise a student-facing launch lesson for Math for Business Operations. Use for Lesson 1 or any lesson explicitly designated as a launch lesson. This skill is for lessons that introduce the founder problem, unit scoreboard, shared simulation, and phase-by-phase launch flow. Do not use for accounting-principles lessons, Excel-principles lessons, or project lessons.

Write or revise a student-facing project rehearsal lesson for Math for Business Operations. Use for lesson 7 or any guided transfer lesson that rehearses the project workbook, quality standard, evidence chain, audit routine, and presentation expectations before students begin the real project. This skill is for shared teacher-data workbook orientation, guided group practice, guided audit, final polish, peer critique, transfer checks, and project handoff. Do not use for launch lessons, accounting-principles lessons, Excel build lessons, or independent project lessons.

Scaffold a new feature component set (Form, List, Detail + tests) following project conventions

Create a new PDF export template following project conventions

Compile a workbook project into a preview-ready HTML document

Validate workbook content JSON files against the Zod schema and report issues

Build and query a SQLite knowledge graph of a TypeScript codebase. Use this skill for structural code questions, callers, dependencies, paths, impact, architecture, and documentation-contract audits.

Generate a vitest test file following project TDD conventions

Use whenever the user is producing AP Precalculus Manim explainer videos in this project, including writing narration, storyboards, scenes.py, shared helpers, or reviewing renders. This skill enforces the project's 3Blue1Brown-inspired visual methodology, the six-stage production pipeline, ManimGL conventions, and the quality bar (one core idea, one anchor example, one misconception, AP-style takeaway).

Create and validate a Prisma migration with schema checks