claude

brana

AI development system — skills, agents, and hooks for systematic software engineering with Claude Code

3 on GitHubby Martin Eseriosv1.0.0MITupdated 23 days agodevelopment
/

Plugin brana from marketplace brana in martineserios/thebrana. Commands read from the repo's manifest — 22 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (64)

  • acquire-skills

    Find and install skills for what you're doing — tech or reasoning gaps. Matches activity and tech context to relevant skills. Use when entering unfamiliar tech, stuck on a reasoning challenge, or no skill fits.

  • caveman

    Ultra-compressed mode — 65-75% fewer tokens, preserving technical accuracy. Strips filler, hedging, pleasantries. Code/commits stay in normal language.

  • cloud-run-basics

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

  • critical-thinking-logical-reasoning

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

  • decision-matrix

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

  • event-driven-architect

    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

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

  • first-principles

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

  • gcp-cloud-run

    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.

  • inversion

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

  • jobs-to-be-done

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

  • llm-evaluation

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

  • nextjs-patterns

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

  • pre-mortem

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

  • second-order-thinking

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

  • six-thinking-hats

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

  • supabase-postgres

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

  • supabase-skill

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

  • supabase

    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.

  • swot-analysis

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

  • systems-thinking

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

  • vercel-react

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

  • vitest

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

  • web-design

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

  • webhook-handler-patterns

    Best practices for webhook handlers: verify → parse → handle idempotently. Covers idempotency, error handling, retry logic, framework-specific gotchas (Express, Next.js, FastAPI). Use when implementing any webhook receiver.

  • align

    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.

  • backlog

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

  • bash-defensive-patterns

    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.

  • brainstorm

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

  • cargo-machete

    Detect and remove unused dependencies in Rust projects using cargo-machete.

  • challenge

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

  • claudemd

    Audit or generate a CLAUDE.md for any project. Natural companion to /brana:align — run audit after align on brownfield projects.

  • client-retire

    Archive a client's patterns and mark them as historical. Use when retiring a client or archiving its knowledge for future reference.

  • close

    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.

  • decide

    Decision support — criteria, scenarios, patterns, recommendation.

  • design-system

    Token architecture and component specs: three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, slide generation. Use for design tokens, systematic design, brand-compliant presentations.

  • discover

    Runtime catalog — list all installed skills, agents, and active hooks. Use when you want to know what's available.

  • do

    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.

  • docs

    Generate and update living documentation — tech docs, user guides, philosophy overview. Composable building block for CLOSE and other skills.

  • domain-driven-design

    DDD tactical patterns — entities, value objects, aggregates, domain services, repositories, specifications, bounded contexts (Python/TypeScript).

  • export-pdf

    Convert a markdown file to PDF using mdpdf. Use when exporting proposals, SOPs, or any markdown document to PDF.

  • fix

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

  • gemini

    Delegate to agy (Gemini worker) — ROUTE→ENRICH→DELEGATE→APPLY→EXTRACT→PERSIST. Use for research, boilerplate, doc drafts, batch summarization.

  • grad-mechanism-design

    Mechanism design (reverse game theory): incentive-compatible rules for allocation — auctions, voting, matching. Use when designing or evaluating a mechanism for incentive compatibility and rationality.

  • gsheets

    Google Sheets via MCP — read, write, create, list, share spreadsheets. Use when reading, writing, or managing Google Sheets data.

  • impeccable

    Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,

  • log

    Capture events — links, calls, meetings, ideas — into an append-only log. Bulk mode for WhatsApp dumps. Use when something happened.

  • mcp-builder

    MCP server development guide — build, test, and deploy MCP servers.

  • memory

    Knowledge system ops — recall, pollinate, audit docs. Subcommands: recall, pollinate, review. Use for pattern queries, cross-client transfer, or audits.

  • meta-templates

    Manage Meta WhatsApp templates — submit, status, audit, pull, appeal. Use for any WhatsApp BSP client with ~/.config/brana/meta/<client>.env provisioned.

  • onboard

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

  • plugin

    Manage Claude Code plugins — add marketplaces, install, update, remove, list. Use when installing plugins, checking status, or managing the registry.

  • product-brainstorming

    Brainstorm product ideas, explore problem spaces, and challenge assumptions as a thinking partner. Use when exploring an opportunity, generating solutions, or stress-testing an idea before converging on a direction.

  • reconcile

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

  • research

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

  • retrospective

    Store a learning — classify type, route to canonical destination. Use after discoveries, unexpected issues, workarounds, or when a reusable pattern emerges.

  • review

    Business review — weekly health check, monthly close, or ad-hoc audit. Subcommands: weekly, monthly, check. Use for periodic reviews or metrics assessment.

  • rust-skills

    Rust best practices — 179 rules across 14 categories for idiomatic, optimized Rust code.

  • scheduler

    Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.

  • ship

    Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.

  • sitrep

    Situational awareness — where am I, what was I doing, what's next. Context recovery after compression, confusion, or mid-session reorientation.

  • terminal-diagrams

    Reference for drawing any diagram as plain monospace terminal text — box-drawing/ASCII, no external renderer. Read when work-preferences.md's trigger fires.

  • verify-docs

    Periodic doc verification — runs validate.sh structural check, samples assumption rows for semantic review. Run quarterly to collect drift evidence.

  • web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", or \"vs best practices\".

Slash commands (1)

  • /brana:repo-cleanup

    Commit accumulated spec doc changes: survey, group by logical batch, branch, commit, merge

Subagents (14)

  • challenger-calibration

    Severity scoring guide with few-shot examples and hard thresholds for the challenger agent.

  • archiver

    Archive project patterns and knowledge when retiring. Categorize as transferable, historical, or deletable. Use when retiring a project or archiving knowledge. Not for: active project work, pattern recall, daily operations.

  • build-evaluator

    Grade completed implementation against task acceptance criteria. Use at close step after a build. Not for: plan review, code quality, style, PR gating.

  • challenger

    Adversarially review a plan, architecture decision, or approach. Stress-test before commitment. Use when a significant decision is being made. Not for: data collection, project diagnostics.

  • client-scanner

    Scan client project structure, detect tech stack, check brana alignment. Use when entering an unfamiliar client project or for project health checks. Not for: business stage classification, knowledge recall, web research.

  • daily-ops

    Daily venture focus card — health snapshot, pending actions, experiments. Use at session start on a venture project. Not for: deep metrics analysis, pipeline management, project alignment checks.

  • debrief-analyst

    Extract errata, learnings, and patterns from a work session. Use at end of implementation sessions or when notable learnings emerge. Not for: adversarial review, project scanning, knowledge recall.

  • gemini

    Delegate to agy (Gemini Flash). Use for research, boilerplate, doc drafts, batch summarization. Not for: knowledge recall, project diagnostics.

  • memory-curator

    Recall patterns from knowledge system, cross-pollinate across clients, check knowledge health. Use when starting work on a topic or periodic checks. Not for: codebase search, project scanning.

  • metrics-collector

    Collect venture metrics from snapshots, experiments, pipeline, financials. Use when /brana:review runs (weekly, monthly, or check). Not for: daily focus cards, deal-level analysis, general research.

  • pipeline-tracker

    Pipeline status — deal stages, overdue follow-ups, conversion trends. Use when pipeline or deal-related work is happening. Not for: broad metrics aggregation, daily priorities, venture diagnostics.

  • pr-reviewer

    Review PR diffs for code quality, bugs, and style issues. Auto-triggered on PR creation. Not for: implementation, file editing, test writing.

  • scout

    Fast research for codebase exploration and web search. Use when finding files, searching code, or fetching external info. Not for: knowledge recall, project diagnostics, business analysis.

  • venture-scanner

    Diagnose a business project — classify stage, recommend frameworks, identify gaps. Use when first encountering a business project or for health audits. Not for: tech stack assessment, daily operations, metrics collection.

Hooks (30)

  • PreToolUse

    bash "$HOME/.claude/hooks/pre-tool-use.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/tdd-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/spec-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/feedback-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/memory-write-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/plan-mode-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/worktree-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/doc-gate.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/main-guard.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/branch-verify.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/branch-name-warn.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/no-attribution-commit.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/secret-scan.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/commit-msg-verify.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/branch-checkout-warn.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/bash-risk-classifier.sh"

  • PreToolUse

    bash "$HOME/.claude/hooks/runner-verb-guard.sh"

  • PreToolUse

    "$HOME/.local/bin/rtk" hook claude

  • PostToolUse

    bash "$HOME/.claude/hooks/post-tool-use.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/skill-sentinel.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/post-plan-challenge.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/post-pr-review.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/task-completed.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/hallucination-detect.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/bash-output-compress.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/post-sale.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/post-tasks-validate.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/post-hooks-json.sh"

  • PostToolUse

    bash "$HOME/.claude/hooks/memory-index-sync.sh"

  • PostToolUse

    bash ${CLAUDE_PLUGIN_ROOT}/hooks/hooks-auto-deploy.sh

View source on GitHub

More from martineserios/thebrana

All 2 plugins →

Source of truth for the code every brana cockpit mod carries (allowlist, run, state, probe, snapshot). Never installed: the engine refuses imports outside a plugin's folder, so system/scripts/mods-sync-shared.sh vendors these files into each mod's hooks/_shared/ and validate Check 77a asserts the copies are byte-identical.

3

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

nextjs

claude

Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.

6 skills

vercel/next.js 143,495

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

AI-powered codebase understanding — analyze, visualize, and explain any project

9 skills · 10 agents · hooks

Egonex-AI/Understand-Anything 92,410

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

Maintain brana?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins