Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

aviralk1309

@aviralk1309 source repo

3 published skills

  1. ▌
    UI UX Reviewer · aviralk1309 bundle
    Review UI/UX like a senior product designer, not just a dev — layout, accessibility (WCAG 2.2), color contrast, mobile responsiveness, user flows, design consistency, and visual design quality (theme, typography, hierarchy). Use whenever the user shares a screenshot, URL, or component code and asks for feedback, a review, an audit, or "does this look good/professional." Trigger even without the word "UX" — e.g. "check this page", "is this accessible", "does this feel mobile friendly", "review my landing page", "pick a color scheme", "does this design look dated", "why does this feel off." Worldwide audience by default — not region-locked. Do NOT trigger for pure logic/backend bugs with no visual/interaction surface.
    0 installs
  2. ▌
    Fullstack Dev Expert · aviralk1309 bundle
    Senior full-stack engineering: JS/TS (React, Next.js, Node/Express/NestJS), Python (Django/DRF/Celery), Go, and Java/Spring Boot, plus MongoDB, PostgreSQL, Redis, Docker. Use for explaining code, building a feature, refactoring, debugging, or performance work in any stack — trigger without "full-stack" in the request: "why is this component re-rendering", "add a Django view for X", "my query is slow", "dockerize this app", "add a Spring Boot endpoint", "goroutine leak", "fix this JPA N+1". Also trigger for: code-level framework choice; product-owned vs. client-handoff decisions; test strategy/flaky tests; API versioning/deprecation; live prod incidents/postmortems; LLM-call integration (streaming, cost, prompt injection). For system/service-level architecture (monolith vs. microservices, service boundaries, event-driven design, infra scaling) defer to a dedicated architecture skill if present. Push production-grade defaults, calibrated to user experience level.
    0 installs
  3. ▌
    Senior Software Architect · aviralk1309 bundle
    Acts as a staff/principal software architect for system design and infra decisions. Use for: system design, monolith-vs-microservices, service boundaries, REST/GraphQL/gRPC API design, event-driven systems, DB schema/scaling, auth/authz, test strategy, CI/CD & IaC, security/appsec, observability/SRE, data pipelines, cloud cost/FinOps, AI/ML system design, platform engineering, compliance architecture, or SOLID/DRY/Clean Architecture review. Trigger even without the word "architecture" — e.g. "how should I structure this backend", "is this schema good", "one service or many", "how do I scale this", "review my API", "how do I test this", "set up my deploy pipeline", "set up monitoring", "reduce cloud costs", "how should I serve this ML model". Push toward production-grade answers, not toy defaults. Do NOT trigger for: algorithm/DSA/leetcode problems, single-function bug fixes, generic syntax questions, CSS-only styling, or throwaway scripts.
    0 installs