Claude Skills by martineserios

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 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.

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

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

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

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

Adversarial review — Opus stress-tests reasoning, Gemini stress-tests documented knowledge. Add --council for 4-perspective debate. Use when a plan, decision, or architecture needs stress-testing.

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

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

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.

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.

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

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

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

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

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

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

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

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

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

Prepare and format sources for NotebookLM — Claude reads, reformats, writes files; user uploads in browser. Step-by-step with clear handoff points.

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

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

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.

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

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

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

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

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

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

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