Tristan578
@Tristan578
Public Skills
developer-experience
by Tristan578
DX audit for SpawnForge — checks documentation freshness, cross-IDE consistency, CLAUDE.md accuracy, and onboarding quality. Use when completing features, auditing DX quality, or when documentation may be out of sync with code.
capability-review
by Tristan578
Forward-looking sister to changelog-review. Scans our SaaS + library stack (analytics, monitoring, observability, agent tracking, infrastructure, AI, payments, auth) against TODAY's provider changelogs / releases / betas to surface capabilities we are NOT yet using — newly shipped or long-available-but-unadopted — that could improve the product or our build harness. Every opportunity comes with its provider cost. Use for quarterly capability audits, when asking "what new features can we leverage," or before planning a growth/observability/infra initiative.
dispatch-builder
by Tristan578
Orchestrator checklist + canonical prompt template for dispatching builder agents against taskboard tickets. Use before dispatching any builder, when batching tickets for implementation, or when a dispatched builder's output is missing PR metadata (Closes link, milestone, changeset).
builder
by Tristan578
Implement a spec from specs/ into working code. Dispatches to rust-engine, frontend, mcp-commands, and testing skills based on the layers touched. Use when implementing a feature, fixing bugs, or asked to "build" or "implement" something.
design
by Tristan578
Design feature architecture for SpawnForge with specs in specs/. Use when planning new features, evaluating trade-offs between ECS/store/MCP approaches, or designing cross-layer changes that touch Rust engine + React + MCP simultaneously.
changelog-review
by Tristan578
Check changelogs for Bevy, Next.js, Zustand, wasm-bindgen, Rapier, and all SpawnForge deps. Use when training data may be stale, before major upgrades, or when a library API behaves unexpectedly.
cycle
by Tristan578
Run the full Plan → Build → Verify loop for a SpawnForge feature. Orchestrates planner → builder → validator in sequence. Use when implementing a complete feature end-to-end from spec to passing tests.
docs
by Tristan578
Write, update, and review SpawnForge docs — README, known-limitations, API references, user-facing copy, CLAUDE.md, and MCP command descriptions. Use when writing docs, reviewing doc quality (PASS/FAIL), or auditing for stale references.
claude-platform-reference
by Tristan578
"Use when you need details about SpawnForge's Claude Code platform setup — hooks, skills inventory, MCP servers, validation tools, or plugin config. Reference for the automation infrastructure."
api-middleware-migrate
by Tristan578
Migrate API routes from raw authenticateRequest to withApiMiddleware pattern. Takes a route file path, reads current auth/billing/validation, generates the middleware wrapper. Use when working on #7431, #7430, #7434.
babysit-prs
by Tristan578
Monitor open PRs for CI failures and review comments, then fix issues automatically. Use when PRs need to be driven to green — checks CI status, Sentry comments, merge conflicts, and applies fixes.
env-health-check
by Tristan578
Validate SpawnForge production environments — Vercel deployments, health APIs, Sentry, CD pipeline. Run after deploys or at session start when a silent breakage is suspected (broken CD, health endpoint down, env var missing).
autonomous-sprint
by Tristan578
Long-running autonomous session — ship fixes, run review board, push, resolve bot comments, repeat. No human intervention until PRs are merge-ready.
deploy-engine
by Tristan578
Build WASM engine (WebGL2 + WebGPU) and deploy to Cloudflare R2 CDN at engine.spawnforge.ai. Use when engine/ Rust code changes need to ship, or when asked to "deploy engine", "update CDN", or "publish WASM".
component-checklist
by Tristan578
"Use when adding a new ECS component, MCP command, or engine capability. Checklist of all files that must be updated across Rust engine, web layer, and integration points."
arch-validator
by Tristan578
Validate Rust engine architecture boundaries — ensure core/ has no browser deps, bridge/ is properly isolated. Run after any engine/ changes or when "architecture violation", "import boundary", or "bridge isolation" is mentioned.
architect-flow
by Tristan578
Spec-first architecture workflow for SpawnForge features. Use when planning new features, designing multi-system changes, or asked "how should we build X?" — produces a spec in specs/ before any code is written.
frontend
by Tristan578
Build SpawnForge React/Next.js UI — editor panels, Zustand store slices, engine event hooks, chat handlers, Tailwind styling. Use when adding components, stores, hooks, or any web/src/ code changes.
db-migrate
by Tristan578
Drizzle schema change workflow for SpawnForge Neon DB. Use when modifying schema.ts, generating migrations, applying migrations to production, or debugging FK/cascade issues.
build
by Tristan578
Build WebGL2 + WebGPU WASM engine variants and copy to web/public/. Use when engine/ Rust code changes, before E2E tests, or when lockfile drift is detected after cherry-picks or package.json edits.
kanban
by Tristan578
"Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria."
deploy-to-vercel
by Tristan578
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
claimable-postgres
by Tristan578
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL", "npx neon-new", "neon.new", "neon.new API", "claimable postgres API".
sync-pull
by Tristan578
"Pull changes from GitHub Project board into local taskboard. Syncs subtasks, description, priority, and re-links tickets by ULID metadata."