thebrana

End a session — extract learnings, write handoff, store patterns, detect doc drift. Use when ending a work session or when the user says done/bye/closing.

Build anything — features, bug fixes, refactors, spikes, migrations. Auto-detects strategy, integrates with backlog, enforces TDD. The unified dev command.

Align a project to brana practices — assess gaps, plan, implement, verify. Auto-detects type. Use when setting up a new project or realigning an existing one.

Scan and diagnose a project, or scaffold a new client from scratch. Works for code and venture clients. Auto-detects project type.

Manage the backlog — plan, track, navigate phases and streams. Use when planning phases, viewing roadmaps, or restructuring work.

Structured bug fix — reproduce (failing test), diagnose, fix (minimal change), verify, commit. Enforces test-first. Use when a bug needs a methodical fix.

Unified maintenance — detect drift, run security checks, cascade spec propagation, knowledge hygiene. Scoped via --scope flag. Default: consistency.

Research a topic, doc, or creator — check sources, follow references, produce findings. Use when starting deep research on a topic or external source.

Adversarial review — Fable 5 stress-tests reasoning, Gemini checks knowledge. Use before plan or architecture decisions.

DDD tactical patterns for complex business modeling including entities, value objects, aggregates, domain services, repositories, specifications, and bounded contexts. Python dataclass implementations with TypeScript alternatives. Use when building rich domain models, enforcing invariants, or separating domain logic from infrastructure.

DDD tactical patterns for complex business modeling including entities, value objects, aggregates, domain services, repositories, specifications, and bounded contexts. Python dataclass implementations with TypeScript alternatives. Use when building rich domain models, enforcing invariants, or separating domain logic from infrastructure.

Interactive idea maturation — explore, research, shape raw ideas into actionable plans. Use when you have a rough idea and want to think it through.

Surface hidden assumptions, detect logical fallacies, examine evidence quality, and stress-test arguments before committing to them.

Weighted criteria scoring for multi-option decisions — makes trade-offs explicit and defensible with sensitivity analysis.

Bottom-up reasoning from fundamentals — strip assumptions, interrogate each one, rebuild from what's actually true.

Backward-from-failure thinking — define what would guarantee failure, then systematically avoid it.

Understand what customers are actually hiring a product to do — functional, emotional, and social dimensions — to design solutions that win.

Prospective hindsight — imagine the project already failed, then diagnose why. Surfaces hidden risks before commitment.

Chain-reaction mapping — trace consequences beyond the obvious first effect to reveal hidden risks and opportunities.

Six parallel thinking perspectives — White/Red/Black/Yellow/Green/Blue — to separate facts, feelings, risks, benefits, creativity, and process.

Map Strengths, Weaknesses, Opportunities, Threats — then generate cross-referenced strategic moves (SO, WO, ST, WT).

Map players, stocks, flows, and feedback loops to understand why a system behaves the way it does — and where leverage lives.

Critical thinking and logical reasoning analysis skills for when you are explicitly asked to critically analyse written content such as articles, blogs, transcripts and reports (not code).

Help users think in systems and understand complex dynamics. Use when someone is dealing with multi-stakeholder problems, trying to understand second-order effects, managing platform ecosystems, or analyzing complex organizational dynamics.

Find and install skills for what you're doing — tech stack AND thinking/reasoning gaps. Analyzes activity type (deciding, strategizing, challenging, analyzing, planning) and tech context to surface relevant skills. Use when entering unfamiliar tech, stuck on a reasoning challenge, or when no local skill covers the current task.

Decision support — criteria, scenarios, patterns, recommendation.

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

Alias for /brana:backlog start with freeform text. Routes to the best skill or creates a task. Use /brana:backlog start directly for the same behavior.

Cloud Run expert guidance. Use when deploying services, running jobs, or managing worker pools for HTTP, scheduled tasks, or background processing.

Design event-driven systems: contracts, topics, consumers, retries, idempotency, and sagas. Use for asynchronous workflows, reliability patterns, retry/replay design, DLQ handling. NOT for CRUD APIs or ETL pipelines.

FastAPI best practices + Pydantic. Use when building or reviewing FastAPI APIs.

Production-ready Cloud Run on GCP: containerized services, Cloud Run Functions, cold start optimization, Pub/Sub integration, Cloud SQL, Secret Manager, concurrency tuning. Covers sharp edges and gotchas.

LLM evaluation — automated metrics, human feedback, benchmarking. Use when testing performance, measuring AI quality, or establishing evaluation frameworks.

Next.js App Router — Server Components, Actions, streaming, caching. Use when building or migrating Next.js apps.

Postgres optimization — 70 rules (queries, indexes, RLS, concurrency). Use when writing SQL or reviewing schema.

Use when doing ANY task involving Supabase: Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues, supabase-js, @supabase/ssr, RLS, schema migrations, CLI, MCP server. Includes security checklist.

Core Supabase — DB, Auth, Realtime, Storage, RLS, Edge Functions. Triggers on ANY Supabase task.

React/Next.js performance — 70 rules (waterfalls, bundle, re-renders). Use when reviewing or writing React/Next.js code.

Vitest unit testing — Vite-powered, Jest-compatible. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

UI review against Web Interface Guidelines. Use when asked to review UI, check accessibility, or audit design.