Agent Claude Code
Review backend designs, TRDs, architecture changes, module boundaries, API contracts, and implementation plans before coding. Use for high-risk or cross-cutting backend work.
Agent Claude Code
Review backend designs, TRDs, architecture changes, module boundaries, API contracts, and implementation plans before coding. Use for high-risk or cross-cutting backend work.
Agent Claude Code
Review database migrations, query changes, transaction boundaries, RLS/tenant isolation, locking, indexes, backfills, and production rollout safety.
Agent Claude Code
Implement production Go backend changes with clean architecture, explicit errors, context-first APIs, tests, and focused verification. Use for non-trivial Go backend feature/bug implementation.
Agent Claude Code
Security and data-safety review for backend/API/database changes, especially authz, tenant isolation, tokens/codes, billing, RLS, secrets, and unsafe logs.
Agent Claude Code
Design and implement focused tests for Go backend behavior, edge cases, authz, tenancy, database consistency, concurrency, and bug reproductions.
Command Claude Code
Bootstrap a new Claude Code installation with Indra's engineering persona, memory, and project context.
Command Claude Code
Review staged and unstaged Go code changes before pushing. Checks security vulnerabilities, hexagonal architecture violations, Go code quality, and test coverage. Reports findings grouped by severity (HIGH/MEDIUM/LOW) and returns a PASS or BLOCK verdict.
Command Claude Code
Create, update, or improve a Technical Requirements Document (TRD) as a senior software engineer. Use /trd to start from scratch (interview-driven), /trd update to reverse-engineer from the codebase with gap analysis, or /trd improve to improve an existing TRD.
Skill Claude CodeCodex
Full TRD-to-GitHub-issues pipeline for any repo. Use this skill whenever the user invokes /vibe-engineering, mentions "vibe engineering", wants to implement a TRD, wants to break down a technical spec into tickets, or says anything like "bikin issues dari TRD ini", "breakdown TRD", or "buat github issues dari spec…
Cursor rule Cursor
Senior backend engineering identity and operating model.
Cursor rule Cursor
Database and operations standards — migrations, queries, transactions, observability.
Cursor rule Cursor
Go backend engineering standards — architecture, error handling, concurrency, API design.
Cursor rule Cursor
Engineering operating model — workflow, risk classification, scope discipline.
Cursor rule Cursor
Security and data safety standards — authz, secrets, injection, tenant isolation.
Cursor rule Cursor
Testing and verification standards — TDD, test quality, verification strategy.
Cursor rule Cursor
Uncertainty and sources — epistemic honesty, citation standards, fact-checking.
Cursor rule Cursor
Second-brain vault and qmd MCP guidance.
Skill Claude CodeCodex
Research a user-requested topic and file a bounded synthesis in the local second-brain. Triggers on autoresearch, research and file, deep dive into, or investigate a topic.
Skill Claude CodeCodex
Create or edit an Obsidian JSON Canvas for local second-brain material. Triggers on create canvas, add to canvas, canvas new, or canvas add note.
Skill Claude CodeCodex
Clean a web page before ingesting it into the local second-brain. Triggers on defuddle, clean this page, strip this URL, or remove web clutter.
Skill Claude CodeCodex
Create Obsidian Bases views over local second-brain notes. Triggers on create a base, Obsidian Bases, database view, or dynamic note table.
Skill Claude CodeCodex
Write valid Obsidian Markdown for the local second-brain. Triggers on write Obsidian note, wikilink, callout, embed, or Obsidian syntax.
Skill Claude CodeCodex
Save a durable answer or decision to the local second-brain. Triggers on save this, file this, keep this, save this answer, or save this session.
Skill Claude CodeCodex
Use the personal second-brain vault for relevant nontrivial work, durable decisions, source ingest, and inbox review. Search it before repeating prior research; capture durable outcomes as inbox drafts; curate only when asked.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: