saranskumar
- 97 skills
- 0 followers
- last month last updated
- ▌ Python Automation Script Designer · saranskumarUse this when designing Python scripts for automation, batch processing, file operations, data transformation, or internal workflows that need deterministic structure and safe environment handling.
- ▌ Python Service Structure Designer · saranskumarUse this when a Python service, package, or repository needs a maintainable internal structure for modules, domain logic, adapters, config, entrypoints, and tests. Trigger on requests about project layout and internal organization for Python systems.
- ▌ Supabase Storage Pattern Designer · saranskumarUse this when a Supabase app needs file or object storage design, bucket strategy, signed URL handling, metadata patterns, upload trust boundaries, or storage access controls.
- ▌ Growth Loop Designer · saranskumarDesign product-led growth loops, activation paths, and expansion mechanics for a software product. Use when the team needs onboarding-to-value planning, sharing or collaboration loops, retention hooks, or realistic post-launch growth motions tied to product usage.
- ▌ Monetization Planner · saranskumarUse when the team needs pricing, packaging, free-tier, trial, usage metering, or business-model guidance for a software product. Trigger on requests to design how the product should make money or control value access.
- ▌ API Contract Designer · saranskumarDesign API contracts from product flows and backend responsibilities. Use when the team needs resource models, action endpoints, request and response shapes, error handling, pagination rules, and contract clarity before implementation begins.
- ▌ Mvp Feature Prioritizer · saranskumarPrioritize features for an MVP or first release. Use when the team has too many ideas and needs must-have vs later vs never-for-v1 decisions tied to the core value loop, user pain, operational shortcuts, and launch feasibility.
- ▌ Frontend Scaffold Planner · saranskumarPlan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.
- ▌ Launch Readiness Reviewer · saranskumarReview whether a product, MVP, or feature is actually ready to launch. Use when the team needs a production-minded check across product quality, UX edge cases, auth and security, observability, support readiness, pricing readiness, and post-launch measurement.
- ▌ Implementation Plan Writer · saranskumarWrite an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.
- ▌ Product Philosophy Designer · saranskumarUse when the team needs a clear product point of view, product principles, or a concise philosophy statement before planning UX, features, or architecture. Trigger on requests about product vision, differentiation, or what the product should optimize for.
- ▌ Product Builder Orchestrator · saranskumarUse when the request is broad and spans idea evaluation, MVP planning, UX, frontend, backend, database, auth, integrations, and launch strategy. Trigger on asks like "build this app", "turn this idea into a product", "design the whole system", or "plan everything end to end".
- ▌ Product Philosophy Extractor · saranskumarExtract the core product philosophy, strategic posture, and design principles from a raw concept or founder brief. Use when the team needs a crisp product promise, guiding principles, product point of view, or a philosophy statement before scope and UX planning.
- ▌ Pricing And Monetization Planner · saranskumarDesign pricing, packaging, and monetization strategy for a software or AI product. Use when the team needs plan structure, free-tier logic, usage vs seat pricing tradeoffs, paywall timing, or monetization guardrails tied to product value and costs.
- ▌ Design · saranskumar bundleUse this skill when the user is designing any visual system, UI, graphic, layout, brand asset, or interface and needs structured, high-quality, communication-first design decisions across typography, layout, color, imagery, and UX.
- ▌ Refactor · saranskumarUse when code is hard to read, has duplication, is too complex, has grown beyond 300 lines, or needs restructuring without changing behavior. For extracting functions, simplifying nested logic, removing dead code, improving naming, splitting large files, and applying clean code principles. Activate when user says "clean this up", "this is messy", "simplify", "extract", or "improve readability".
- ▌ Debugging · saranskumar bundleUse when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".
- ▌ API Designer · saranskumarUse when the team needs API routes, action contracts, request and response shapes, error handling, pagination, or webhook patterns for a backend or BFF. Trigger on requests to design APIs before implementation.
- ▌ Code Reviewer · saranskumarUse this when reviewing code changes for correctness, maintainability, security-sensitive logic, boundary separation, and likely regressions across any supported runtime or framework.
- ▌ Skill Refiner · saranskumarUse when an existing Antigravity skill has weak triggers, vague instructions, missing constraints, or poor structure and needs to be improved. Trigger on requests to rewrite, tighten, split, or review a skill for better routing and reuse.
- ▌ System Reviewer · saranskumarUse this when reviewing a full system design, architecture plan, or cross-service implementation for operational risk, boundary clarity, security posture, deployability, and maintainability.
- ▌ Screen Architect · saranskumarUse when user flows already exist and the team needs a screen inventory, screen responsibilities, key states, and view hierarchy for a product or feature. Trigger on requests to break a flow into pages, views, or screen-level structure.
- ▌ SQL Optimization · saranskumarUse when debugging slow SQL queries, designing database indexes, or rewriting queries for better performance. For EXPLAIN analysis, index strategy, N+1 problem resolution, and query optimization patterns.
- ▌ UX Flow Designer · saranskumarDesign user journeys and task flows for a product concept or MVP. Use when the team needs primary flows, branch conditions, edge cases, onboarding paths, and end-to-end user movement before screen planning or UI implementation.
- ▌ Workflow Builder · saranskumar bundleUse when the team needs a repeatable multi-step workflow, pipeline, or operating sequence that connects multiple skills, systems, or product stages. Trigger on requests to design a workflow from idea to launch, onboarding to retention, or request to execution.
- ▌ CLI Tool Designer · saranskumarUse this when the deliverable is a CLI tool, command suite, operator utility, or local developer tool and the team needs command structure, UX, config, packaging, and safety planning across languages.
- ▌ Security Reviewer · saranskumarUse this when reviewing a feature, service, API, auth design, integration, job system, or deployment plan for security weaknesses, unsafe trust assumptions, input risks, or privilege issues.
- ▌ Data Flow Designer · saranskumarUse when the team needs to understand how data moves through frontend, backend, database, jobs, auth, and external integrations. Trigger on requests to map data flow, event flow, or state transitions across the system.
- ▌ Python API Builder · saranskumarUse this when designing or scaffolding a Python API service, endpoint structure, request validation approach, handler layout, or API-specific service patterns in FastAPI, Flask-style, or similar Python backends.
- ▌ Auth · saranskumarUse when implementing login, registration, session handling, protected routes, or role-based access.
- ▌ Integration Planner · saranskumarUse when a product needs third-party integrations such as payments, email, analytics, AI providers, storage, or internal services. Trigger on requests to plan integration boundaries, provider selection, failure handling, or sync strategies.
- ▌ User Journey Mapper · saranskumarUse this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.
- ▌ Worker Job Designer · saranskumarUse this when background workers or job processors need design or review. Trigger on requests about asynchronous processing, job payloads, retries, scheduling, worker ownership, or long-running tasks outside the request path.
- ▌ Express API Designer · saranskumarUse this when planning or refining an Express or Express-style Node.js API with route groups, middleware boundaries, validation, auth, error handling, and service layering.
- ▌ Interaction Designer · saranskumarUse this when the team needs detailed interaction behavior for user inputs, transitions, feedback, validation, confirmations, or stateful UI behavior that should be implementation-ready rather than purely visual.
- ▌ Node Service Designer · saranskumarUse this when designing or refining a Node.js backend service, daemon, worker, integration service, or internal runtime that is not just an Express route layer.
- ▌ Observability Planner · saranskumarUse this when the system needs logging, metrics, tracing, alerting, or operator-visible runtime signals for APIs, workers, integrations, serverless functions, or local-to-production supportability.
- ▌ Performance Optimizer · saranskumarUse this when the team needs to improve latency, throughput, render performance, query speed, worker throughput, or resource usage across frontend, backend, database, or background systems.
- ▌ UI Component Designer · saranskumarUse when the team needs reusable UI component patterns, component responsibilities, states, props, and interaction behavior for React, Next.js, or Tailwind-based interfaces. Trigger on requests to design a component system or define a component before coding it.
- ▌ Product · saranskumarUse when defining a feature's purpose and user value before building it, writing user stories, mapping user flows end-to-end, prioritizing what to build next, evaluating whether a feature solves a real problem, or reviewing scope to prevent over-engineering. Activate when user says "what should I build", "plan the feature", "is this the right approach", "define the requirements", or presents an idea without a clear user need.
- ▌ Access Control Planner · saranskumarUse this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.
- ▌ Accessibility Reviewer · saranskumarUse this when reviewing or designing UI for keyboard access, semantic structure, focus handling, labels, contrast, error communication, motion sensitivity, or screen-reader-friendly behavior.
- ▌ API Integration Helper · saranskumarUse this when frontend or service code needs help integrating with an API, provider, or internal backend contract. Trigger on requests about request flow, response handling, auth propagation, retries, or client-side integration patterns.
- ▌ Auth Strategy Designer · saranskumarDesign authentication and authorization strategy for a product or MVP. Use when the team needs sign-in methods, session model, user/workspace membership, roles, tenant boundaries, invitation flows, or permission enforcement plans.
- ▌ Design System Enforcer · saranskumarUse this when a codebase or design effort needs consistency enforcement for tokens, spacing, typography, color usage, component variants, and reusable interaction patterns.
- ▌ Firebase Auth Designer · saranskumarUse when the team needs authentication, identity providers, custom claims, session strategy, or permission design for a Firebase-backed app. Trigger on requests to design or review Firebase Auth architecture.
- ▌ Python Worker Designer · saranskumarUse this when a Python worker, consumer, scheduled processor, or background execution service needs design or review. Trigger on requests about Python async jobs, consumers, schedulers, or long-running background processes.
- ▌ Supabase Auth Designer · saranskumarUse when the team needs sign-in methods, profiles, sessions, invitations, memberships, or auth-related architecture for a Supabase app. Trigger on requests to design authentication and authorization using Supabase Auth.
- ▌ Security · saranskumarUse this skill when implementing any feature that touches user data, auth, APIs, file uploads, pe...
- ▌ Thinking · saranskumarUse before any complex or ambiguous task where the path forward is unclear. For breaking down multi-step problems, choosing between approaches, clarifying vague requirements, identifying hidden assumptions, planning before building, and preventing costly mistakes from starting in the wrong direction. Activate when user says "how should I approach this", "what's the best way to", "I'm not sure how to", or presents a problem without a clear solution.
- ▌ Error Handling Designer · saranskumarUse when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.
- ▌ Python CLI Tool Builder · saranskumarUse this when building or planning a Python command-line tool, command surface, argument model, package entrypoint, or automation-oriented CLI workflow.
- ▌ Trust Boundary Analyzer · saranskumarUse this when the system needs clear analysis of trusted versus untrusted execution contexts, external inputs, client/server boundaries, provider callbacks, or admin-level code paths. Trigger on requests about trust boundaries, attack surfaces, or where verification must happen.
- ▌ Backend Service Designer · saranskumarUse this when the team needs to design or refine a backend service, API-facing domain module, internal service, or runtime-specific server component in Python, Node.js, or another backend environment.
- ▌ Background Task Designer · saranskumarUse this when the system needs scheduled tasks, cron-style jobs, periodic maintenance, sync loops, cleanup tasks, or non-interactive background automation that is not simply an API request or queue worker.
- ▌ Database Schema Designer · saranskumarDesign an application database schema from product flows and backend responsibilities. Use when the team needs core entities, relationships, lifecycle fields, indexes, audit needs, tenancy boundaries, and migration-minded schema planning for an MVP or production system.
- ▌ Product Intake Processor · saranskumar bundleUse this when the user gives a broad app, system, service, tool, or feature request and it must be converted into structured implementation requirements, runtime assumptions, security concerns, likely components, and handoff tasks for developer or designer skills.
- ▌ Python Backend Architect · saranskumarUse this when the project needs Python-specific backend architecture for APIs, services, workers, scripts, or internal tools. Trigger on requests about Python runtime structure, framework fit, module boundaries, or service organization.
- ▌ Queue Processing Planner · saranskumarUse this when the system needs queue-backed processing design, message handling rules, delivery semantics, dead-letter strategy, or throughput planning. Trigger on requests about queues, brokers, message processing, and consumer coordination.
- ▌ Supabase Schema Designer · saranskumarUse when designing PostgreSQL tables, enums, relationships, migrations, storage metadata, or tenant-aware schema structures for a Supabase-backed app. Trigger on requests about Supabase schema planning or SQL-first data design.
- ▌ Config Structure Reviewer · saranskumarUse this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.
- ▌ Firebase Function Builder · saranskumarUse when building or planning Firebase Cloud Functions for webhooks, backend APIs, scheduled jobs, claim assignment, or privileged Firestore logic. Trigger on requests to create or review Firebase Functions.
- ▌ Firestore Schema Designer · saranskumar bundleUse when a Firebase app needs Firestore collection design, document shape, subcollection strategy, security rule implications, or query-aware data modeling. Trigger on requests to design Firestore data structures before implementation.
- ▌ Migration Safety Reviewer · saranskumar bundleUse this when reviewing database, storage, config, queue, or integration migrations for rollout safety, rollback feasibility, data correctness, and environment-specific deployment risk.
- ▌ React Component Generator · saranskumar bundleUse when Codex needs to generate or scaffold a React or Next.js component with clear props, state handling, Tailwind styling direction, accessibility, and file structure. Trigger on requests to create a component, page section, dashboard widget, form, modal, or reusable UI block.
- ▌ Responsive Design Planner · saranskumarUse when a web product or component needs responsive layout planning across mobile, tablet, and desktop. Trigger on requests about breakpoints, layout adaptation, content priority, or mobile-first UI behavior.
- ▌ Service Boundary Designer · saranskumarUse this when the team needs to decide how responsibilities should be split across services, modules, workers, APIs, or runtimes. Trigger on requests about service boundaries, ownership, modularity, monolith versus separation, or where logic should live.
- ▌ State Management Designer · saranskumarUse when the team needs to decide how frontend state should be organized across React or Next.js apps. Trigger on requests about local state, global state, server cache, forms, optimistic updates, or choosing between context, stores, and query-based patterns.
- ▌ Testing Strategy Designer · saranskumarUse when the team needs a testing plan covering unit, integration, end-to-end, contract, and security-adjacent checks for a product or feature. Trigger on requests to design practical testing strategy before or during implementation.
- ▌
- ▌ Performance · saranskumarUse when the app is slow, pages take too long to load, API responses exceed 200ms, memory usage is high, or renders are excessive. For profiling, identifying bottlenecks, optimizing React renders, reducing bundle size, improving database query speed, and measuring before/after improvements. Activate when user says "it's slow", "optimize this", "reduce load time", or "too many re-renders".
- ▌ Automation Script Designer · saranskumarUse this when designing scripts or small tools for automation, maintenance, CI tasks, file manipulation, config generation, or local workflow support across shell, Python, or mixed environments.
- ▌ Environment Config Planner · saranskumar bundleUse this when planning environment variables, config files, secrets, flags, and provider settings across local, CI, staging, production, serverless, or multi-runtime systems.
- ▌ Frontend Component Planner · saranskumarUse this when the team needs a component breakdown for a screen or feature that may or may not be React-specific. Trigger on requests to plan component responsibilities, composition, states, and boundaries before implementation.
- ▌ Runtime Validation Planner · saranskumarUse this when the system needs explicit runtime validation for API inputs, config, queue messages, webhook payloads, file metadata, or external provider responses in TypeScript, JavaScript, Python, or mixed systems.
- ▌ Secret Management Reviewer · saranskumar bundleUse this when reviewing or designing how secrets, API keys, service credentials, signing keys, tokens, and environment-specific credentials are stored, loaded, rotated, and kept out of untrusted runtimes.
- ▌ Architecture · saranskumarUse when designing a new system, choosing between architectural patterns, planning how components will connect, evaluating scalability and reliability trade-offs, or reviewing an existing system for structural problems. For system design, service boundaries, database design, API structure, monolith vs microservices decisions, and architecture decision records (ADRs). Activate when user says "how should I structure this", "design the system", "is this architecture right", or "plan the backend".
- ▌ Local Dev Workflow Designer · saranskumarUse this when a project needs a better local development workflow for setup, running services, seeding data, testing integrations, or managing multi-service developer environments.
- ▌ Serverless Function Builder · saranskumarUse this when designing or scaffolding serverless functions for APIs, webhooks, background handlers, or small trusted services across cloud runtimes. Trigger on requests about serverless handlers, event functions, or function-level architecture.
- ▌ Uiux Designer · saranskumarUse this skill when designing UI components, choosing color palettes, implementing responsive layouts, or reviewing code for UX issues. For landing pages, dashboards, e-commerce, SaaS, and mobile apps. Provides 50+ design styles, 97 color palettes, 57 font pairings, and stack-specific guidelines for React, Vue, Next.js, Flutter, SwiftUI, and more.
- ▌ Backend Architecture Planner · saranskumarPlan backend domains, services, jobs, integrations, and failure handling for a product or major feature. Use when UX and product scope are defined and the team needs a production-minded backend design without defaulting to premature microservices.
- ▌ Supabase Rls Policy Designer · saranskumar bundleUse when a Supabase app needs Row Level Security policies for multi-tenant access, ownership checks, roles, service paths, or safe data exposure. Trigger on requests to design or review Supabase RLS and SQL authorization logic.
- ▌ System Architecture Designer · saranskumarUse when the team needs a top-level system architecture spanning frontend, backend, auth, data stores, jobs, integrations, and deployment boundaries. Trigger on requests to design the overall system or validate a proposed architecture.
- ▌ Typescript Backend Architect · saranskumarUse this when the backend is TypeScript-first and needs architecture for services, APIs, workers, serverless handlers, validation boundaries, and runtime-aware module design.
- ▌ Idea Evaluator · saranskumarEvaluate a raw app, startup, SaaS, internal tool, marketplace, or AI product idea before planning features. Use when the user shares a vague concept and needs pain analysis, market realism, feasibility, differentiation, risks, or a build/no-build recommendation.
- ▌ Screen Planner · saranskumarPlan screens, views, and page responsibilities for a product flow. Use when user journeys already exist and the team needs a screen inventory, screen purpose, key states, and component-level responsibilities without jumping into visual styling too early.
- ▌ Deployment Readiness Reviewer · saranskumarUse this when reviewing whether an app, service, worker, CLI, or serverless system is ready for its target environment with respect to config, secrets, migrations, dependencies, observability, rollback, and runtime constraints.
- ▌ Environment Strategy Designer · saranskumarUse this when the project needs a clear strategy for local, test, staging, production, cloud, serverless, or hybrid environments. Trigger on requests about environment layout, runtime differences, environment-specific behavior, or deployment-context planning.
- ▌ Frontend Architecture Planner · saranskumarUse when the team needs route structure, feature modules, design-system boundaries, and frontend responsibilities for a React, Next.js, or Tailwind application. Trigger on requests about frontend architecture, app structure, pages, modules, or client-side delivery planning.
- ▌ Context Manager · saranskumarUse when context window is filling up, sessions are getting slow, or you need to preserve state across sessions. For context compression, state snapshots, search-first discipline, and cross-session memory management.
- ▌ Frontend Expert · saranskumarUse when creating React/TypeScript components, pages, or features. For modern patterns including Suspense, useSuspenseQuery, lazy loading, MUI v7 styling, TanStack Router, and performance optimization.
- ▌ Skill Generator · saranskumar bundleUse when the user wants to create a new Antigravity skill pack or add a focused skill folder with SKILL.md, references, examples, or scripts. Trigger on requests to generate a skill, scaffold a skill, or expand the local skill library.
- ▌ Frontend Data Fetching Planner · saranskumarUse this when a frontend feature needs a clear plan for server data fetching, caching, invalidation, mutations, optimistic UI, or auth-aware data loading.
- ▌ Supabase Edge Function Builder · saranskumar bundleUse when building or planning a Supabase Edge Function for authenticated server logic, webhooks, background triggers, third-party integrations, or privileged operations. Trigger on requests to create or review edge functions in a Supabase system.
- ▌ Firebase Security Rules Reviewer · saranskumarUse this when reviewing or designing Firebase security rules for Firestore or related client-accessed Firebase data. Trigger on requests about Firebase rules safety, access constraints, auth-claim checks, or client data exposure.
- ▌ Python Package Structure Planner · saranskumar bundleUse this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.
- ▌ Supabase Fullstack · saranskumar bundleUse this skill when the user is working with Supabase and needs help with Edge Functions, SQL schema or migrations, Auth, Row Level Security, database functions, local CLI workflows, or deployment. Use it for building features, reviewing Supabase code, creating migrations, writing policies, implementing auth-aware server logic, and debugging full Supabase app flows.