arjuncrevathi
- 26 skills
- 0 followers
- 6 hours ago last updated
- ▌ Agni · arjuncrevathiTesting 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.
- ▌ Maya · arjuncrevathiReact 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.
- ▌ Vayu · arjuncrevathiFastAPI 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.
- ▌ Yama · arjuncrevathiSupabase 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.
- ▌ Durga · arjuncrevathiSystematic 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.
- ▌ Indra · arjuncrevathiCloud infrastructure, Docker, environments, and deployment standards. Use when setting up infrastructure, writing Dockerfiles, configuring deployments or environments, or writing any IaC (Terraform, etc.).
- ▌ Shiva · arjuncrevathiRefactoring 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 · arjuncrevathiMonitoring, metrics, dashboards, and observability standards. Use when adding monitoring or metrics, building dashboards, setting up observability, defining SLOs, or answering "is prod healthy".
- ▌ Brahma · arjuncrevathiGit 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.
- ▌ Garuda · arjuncrevathiPerformance 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.
- ▌ Kubera · arjuncrevathiSecrets 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.
- ▌ Matsya · arjuncrevathiBackups, 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.
- ▌ Muruka · arjuncrevathiSecurity 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 · arjuncrevathiAlerting, notification, and webhook standards. Use when setting up alerts or on-call rules, sending user or system notifications, or building or consuming webhooks.
- ▌ Shesha · arjuncrevathiChat 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.
- ▌ Varuna · arjuncrevathiDatabase 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.
- ▌ Vishnu · arjuncrevathiClean 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).
- ▌ Hanuman · arjuncrevathiHeavy 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.
- ▌ Lakshmi · arjuncrevathiCost 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.
- ▌ Airavata · arjuncrevathiRender 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.
- ▌ Pushpaka · arjuncrevathiVercel 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.
- ▌ Vinayaka · arjuncrevathiProduction readiness standards for zero production issues. Use when deploying, releasing, doing a pre-launch review, or when anyone asks "is this ready for prod".
- ▌ Saraswati · arjuncrevathiDocumentation 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.
- ▌ Chitragupta · arjuncrevathiStructured 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 · arjuncrevathiIncident 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.
- ▌ Vishwakarma · arjuncrevathiSystem 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.