arjuncrevathi
User26 divine weapons for engineering — Hindu-mythology-named Claude skills for the full dev lifecycle
Categories
Indexed Skills (26)
agni
Testing standards — unit/integration/e2e strategy, pytest and vitest conventions, and LLM eval suites. Use when writing tests, discussing test coverage or TDD, fixing flaky tests, or building evals for prompts and model outputs.
airavata
Render deployment standards for the FastAPI backend — render.yaml blueprints, health checks, zero-downtime deploys, pre-deploy migrations, env groups, workers, and Render Postgres connections. Use when deploying to Render, writing or changing render.yaml, configuring Render services, cron jobs, or debugging a Render deploy.
brahma
Git workflow, GitHub push rules, and CI/CD pipeline standards. Use when pushing code, creating branches or PRs, writing commit messages, setting up or modifying GitHub Actions workflows, or configuring any CI/CD pipeline.
chitragupta
Structured logging, audit trails, and request tracing standards. Use when adding logging to any service, implementing audit requirements, tracing requests across services, or reviewing what gets logged and how.
dhanvantari
Incident response, outage handling, hotfix workflow, and postmortems. Use when there is a production incident or outage, "prod is down", a hotfix is needed, an incident needs a postmortem, or a service is degraded and users are affected.
durga
Systematic debugging discipline for bugs, errors, crashes, and unexpected behavior. Use when investigating a bug, error, exception, or crash, when asking "why is this happening", or when code behaves differently than expected.
garuda
Performance and latency optimization across backend, frontend, and LLM calls. Use when something is slow, when investigating latency, or when asked to optimize or improve performance.
hanuman
Heavy lifts — schema migrations, data backfills, and large batch jobs. Use when writing a data or schema migration, running a backfill, moving large datasets, building a batch job, or bulk-processing records through an LLM.
indra
Cloud infrastructure, Docker, environments, and deployment standards. Use when setting up infrastructure, writing Dockerfiles, configuring deployments or environments, or writing any IaC (Terraform, etc.).
kubera
Secrets and credentials management — API keys, .env files, secrets in CI, key rotation, token scoping. Use when handling API keys or credentials, creating or editing .env files, configuring secrets in CI/CD, rotating keys, or responding to a suspected key exposure.
lakshmi
Cost optimization for cloud infrastructure and LLM API spend — budgets, billing alerts, token usage, model selection. Use when discussing cloud costs, API bills, token usage, budgets, or when anything is called "expensive" or needs a cost estimate.
matsya
Backups, restore procedures, and disaster recovery — RTO/RPO, retention, backup testing. Use when setting up or reviewing backups, restoring data, planning disaster recovery, responding to data loss, or defining retention policies.
maya
React frontend standards for a Supabase + FastAPI stack — components, hooks, state, data fetching, forms, and chat UI. Use when writing or reviewing React components, hooks, JSX/TSX, frontend state management, client-side data fetching, or building chat/streaming UI.
muruka
Security standards — OWASP basics, auth, PII handling, dependency hygiene, and LLM-specific attack surface. Use when doing a security review, implementing auth, handling user data, adding dependencies, or wiring LLMs to tools.
narada
Alerting, notification, and webhook standards. Use when setting up alerts or on-call rules, sending user or system notifications, or building or consuming webhooks.
pushpaka
Vercel deployment standards for the React frontend — environments, env vars, preview deployments, domains, caching, and rollback. Use when deploying the frontend, configuring Vercel projects or environment variables, debugging a Vercel build or preview, or setting up domains and rollbacks.
saraswati
Documentation standards for READMEs, docstrings, API docs, ADRs, and onboarding docs. Use when writing or updating a README, adding docstrings, documenting an API, recording an architectural decision, or creating onboarding material.
shesha
Chat and AI data standards for Render Postgres — conversation/message schema, append-only history, pgvector embeddings, token accounting, retention, and context-window queries. Use when designing or querying chat history, messages, conversations, embeddings, pgvector, or any AI-generated data storage.
shiva
Refactoring rules — safe transformation of existing code without behavior change. Use when refactoring, restructuring, cleaning up code, paying down tech debt, or planning a rewrite.
surya
Monitoring, metrics, dashboards, and observability standards. Use when adding monitoring or metrics, building dashboards, setting up observability, defining SLOs, or answering "is prod healthy".
varuna
Database and data store standards — schema design, queries, migrations, and store selection. Use when designing schemas, writing or debugging queries, choosing a database or vector store, or investigating slow queries.
vayu
FastAPI standards for the AI backend — project layout, Pydantic models, async discipline, Supabase JWT verification, SSE streaming for chat, error handling, and CORS with Vercel. Use when writing or reviewing FastAPI routes, Pydantic schemas, Python API endpoints, LLM streaming endpoints, or backend auth.
vinayaka
Production readiness standards for zero production issues. Use when deploying, releasing, doing a pre-launch review, or when anyone asks "is this ready for prod".
vishnu
Clean code standards and efficient data fetching from APIs, databases, and LLMs. Use when writing new code, reviewing code, or fetching data from any external source (REST APIs, databases, LLM providers).
vishwakarma
System design and architecture standards — module boundaries, config, API design, sync vs async decisions. Use when designing a new system or feature, choosing an architecture or pattern, structuring modules, or deciding between queue and synchronous processing.
yama
Supabase standards — auth, Row Level Security, schema migrations, typed clients, and the boundary between Supabase app data and the FastAPI/Render Postgres side. Use when writing Supabase queries, auth flows, RLS policies, Supabase migrations, storage rules, or deciding where data should live.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.