All authors

Claude Skills by jgamaraalv
github.com/jgamaraalv62 skills1 installs85 views
- Accessibility A11yBuild inclusive, WCAG-compliant UIs. Use for a11y, screen readers, ARIA, keyboard nav, contrast, or accessibility audits.Votes: 0GitHub stars: 4
- Architecture Blueprint GeneratorAnalyze a codebase and generate Project_Architecture_Blueprint.md — detected stacks and architecture patterns, diagrams, layers, cross-cutting concerns, extension guidance. Use to document, map, or blueprint a project's architecture or keep it consistent.Votes: 0GitHub stars: 4
- Backend Delivery LoopContinuous backend delivery loop — cycles subagents through test → diagnose → fix → review → secure → re-test until the suite, quality, and security gates are clean. Use to develop, fix, harden, or finish a backend feature/service/endpoint.Votes: 0GitHub stars: 4
- Backend DesignDesign backend systems — REST/GraphQL/gRPC APIs, microservices, database schemas, auth, caching, message queues, scalability. Use when designing backend services, APIs, data models, distributed systems, or auth flows.Votes: 0GitHub stars: 4
- Backend Dev GuidelinesShared backend guide for Langfuse's Next.js/tRPC/BullMQ/TypeScript monorepo — tRPC routers, public REST endpoints, BullMQ processors, services, Prisma/ClickHouse access, Zod validation, and backend tests across web/worker/shared.Votes: 0GitHub stars: 4
- Backend TestingTurn backend test ambiguity into one practical test packet — API/service/repo/auth coverage, fixture & seed/reset strategy, mock-vs-container choices, contract checks, and flaky-suite stabilization across local and CI.Votes: 0GitHub stars: 4
- Backend To Frontend Handoff DocsCreate API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.Votes: 0GitHub stars: 4
- Building ComponentsGuide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.Votes: 0GitHub stars: 4
- Bullmq SpecialistBullMQ Redis-backed job queues in Node.js/TypeScript — workers, delayed/repeatable jobs, flows, rate limiting, retries. Use for background jobs, job scheduling, or reliable async processing.Votes: 0GitHub stars: 4
- Canvas DesignCreate beautiful visual art in .png and .pdf documents using design philosophy. Use when the user asks to create a poster, piece of art, design, or other static visual piece.Votes: 0GitHub stars: 4
- Code PatternsThe bar for any code you write, edit, or review. Read these rules whenever you are writing or reading any codeVotes: 0GitHub stars: 4
- Components Composition PatternsReact composition patterns that scale — compound components, render props, context providers, lifting state. Use when refactoring boolean-prop-heavy components or designing flexible, reusable component APIs (incl. React 19)Votes: 0GitHub stars: 4
- Conventional CommitWrite and apply Conventional Commits — type(scope): subject, imperative mood, with body and BREAKING CHANGE footer when needed. Use when committing staged work or asked to write, review, or standardize a commit message.Votes: 0GitHub stars: 4
- Core Web VitalsCore Web Vitals reference for measuring, diagnosing, and improving LCP, INP, and CLS page performance against Google's thresholdsVotes: 0GitHub stars: 4
- Create SvgCreate professional SVG logos, brand identities, icons, wordmarks, and visual marks — multiple concepts, layouts, and color variations. Use when asked to design a logo, brand identity, icon, or visual mark.Votes: 0GitHub stars: 4
- Css ArchitectureOrganize CSS using BEM, SMACSS, and CSS-in-JS patterns. Use when building scalable, maintainable styling systems with proper naming conventions.Votes: 0GitHub stars: 4
- Cypress AuthorCreates, updates, and fixes Cypress tests (E2E and component) — use to write, add, update, or fix failing/flaky tests, even if the user only says "tests". For explaining or reviewing without edits, prefer cypress-explain.Votes: 0GitHub stars: 4
- Cypress DocsSearch and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.Votes: 0GitHub stars: 4
- Cypress ExplainExplains Cypress tests (E2E and component) and how Cypress works — use to understand, review, or critique tests without editing code, even if the user only says "tests". For creating or fixing tests, prefer cypress-author.Votes: 0GitHub stars: 4
- Delivery Loop RetroWrite a structured retrospective of a delivery-loop run (frontend-delivery-loop, backend-delivery-loop, or fullstack-delivery-loop) that judges what went well, what went badly, where time/roundtrips/tool calls were wasted and in which skill or agent, how the agents integrated, and the session id + trace file paths — then save it as a Markdown report for skill-evolution-factory to act on. Use this the moment a delivery loop finishes (or stalls), whenever the user says "retro", "post-mortem", "...Votes: 0GitHub stars: 4
- DiagnoseDisciplined diagnosis loop for hard bugs and performance regressions — reproduce → hypothesise → instrument → fix → regression-test. Use when asked to diagnose/debug, something is broken or failing, or a perf regression is reported.Votes: 0GitHub stars: 4
- Fastify Best PracticesDevelop, configure, and debug Fastify (Node.js/TypeScript) servers and REST APIs — routes, plugins, JSON Schema validation, hooks, auth, serialization, performance, deployment. Triggers: Fastify, server.ts, app.ts, fastify.config.Votes: 0GitHub stars: 4
- Figma Code ConnectCreate or update Figma Code Connect template files (.figma.ts/.figma.js) that map Figma components to code. Use for Code Connect, Figma component mapping, design-to-code.Votes: 0GitHub stars: 4
- Frontend Delivery LoopContinuous frontend delivery loop — cycles subagents through test → diagnose → fix → review → re-test until E2E and review are clean. Use to develop, fix, harden, or finish a frontend feature/epic verified by tests.Votes: 0GitHub stars: 4
- Frontend FundamentalsFront-end system-design reference — box model, rendering/reflow, DOM & Web APIs, virtualisation, state design, network transports, web performance.Votes: 0GitHub stars: 4
- Fullstack Delivery LoopContinuous fullstack delivery loop — cycles a combined frontend+backend team through test → diagnose → fix → review → secure → re-test, building both layers together in cross-side vertical-slice waves until every E2E/suite, code-quality, visual-fidelity, and security gate is clean. Use to develop, fix, harden, or finish a feature that spans the API and the UI in one coordinated loop, instead of running the frontend and backend loops back-to-back.Votes: 0GitHub stars: 4
- Grill MeInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".Votes: 0GitHub stars: 4
- Hunt Race ConditionHunting playbook for race-condition / TOCTOU vulnerabilities — concurrent-request abuse, HTTP/2 single-packet attacks, double-redeem / double-spend, MFA-OTP & email-verify races, rate-limit bypass. Use when hunting races or TOCTOU bugs.Votes: 0GitHub stars: 4
- ImpeccableUse when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty statesVotes: 0GitHub stars: 4
- Mermaid DiagramsCreate software diagrams in Mermaid — class, sequence, flowchart, ERD, C4, state, gitgraph, gantt. Use to "diagram", "visualize", "map out", or "show the flow" of architecture, database schemas, code structure, or user/app flows.Votes: 0GitHub stars: 4
- Nestjs Best PracticesNestJS best practices — 40 rules across modules, DI, error handling, security, performance, testing, database, API design, microservices, and deployment. Use when writing, reviewing, or refactoring NestJS code.Votes: 0GitHub stars: 4
- Nextjs Best PracticesNext.js App Router principles. Server Components, data fetching, routing patterns.Votes: 0GitHub stars: 4
- Nextjs PerformanceNext.js performance optimization for Core Web Vitals, image/font optimization, caching, streaming, bundle size, and Server Components. Use when fixing LCP/INP/CLS, implementing next/image or next/font, configuring unstable_cache, converting Client to Server Components, streaming with Suspense, or reducing bundle size. Covers Next.js 16 + React 19 patterns.Votes: 0GitHub stars: 4
- Nodejs Backend PatternsBuild production-ready Node.js backend services with Express/Fastify — middleware, error handling, auth, database integration, and API design. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices.Votes: 0GitHub stars: 4
- Owasp Security ReviewReview code and architectures against the OWASP Top 10:2025. Use to audit for vulnerabilities, guide remediation, or write secure code. Triggers: "security review", "OWASP audit", "check for vulnerabilities", "is this code secure".Votes: 0GitHub stars: 4
- Performance HunterPerformance optimization specialist — profiling, caching, latency, N+1, connection pools, p99 tail latency, async, load-testing. Use when performance, slow queries, profiling, caching, optimization, or database latency are mentioned.Votes: 0GitHub stars: 4
- Playwright Best PracticesWrite, debug, and maintain Playwright tests — flaky tests, Page Object Model, locators/waits, fixtures, network mocking, auth, CI/CD. Covers E2E, component, API, visual, a11y, and extension testing.Votes: 0GitHub stars: 4
- Postgresql Code ReviewReview SQL, schemas, and migrations for PostgreSQL best practices — JSONB, arrays, ENUMs/domains, PL/pgSQL, RLS, privileges. Use when reviewing any PostgreSQL DDL, query, function, or migration.Votes: 0GitHub stars: 4
- Postgresql OptimizationPostgreSQL-specific development — JSONB, arrays, custom/range types, full-text search, window functions, indexing, and extensions. Use when writing, tuning, or modeling anything on PostgreSQL.Votes: 0GitHub stars: 4
- PostmanFull API lifecycle via the Postman MCP Server — sync OpenAPI specs to collections, generate typed clients, run API tests, create mocks, publish docs, OWASP audits. Use for Postman, collections, specs, mocks, or SDKs.Votes: 0GitHub stars: 4
- Prisma PostgresPrisma Postgres setup and operations — Console, create-db CLI, Management API, and the TypeScript SDK. Use when provisioning Prisma Postgres databases, linking a local project, or integrating programmatic provisioning with service tokens or OAuth.Votes: 0GitHub stars: 4
- Pro State MachineProfessional React state-machine patterns. Use when implementing complex state logic, reducers, multi-step forms, async flows, or any component coordinating multiple states.Votes: 0GitHub stars: 4
- Race ConditionRace condition and TOCTOU testing for web apps. Use when testing one-time operations, concurrent HTTP abuse, rate-limit bypass, Turbo Intruder gates, HTTP/2 single-packet attacks, and CWE-362-style synchronization gaps.Votes: 0GitHub stars: 4
- React Best PracticesReact/Next.js best-practices reviewer for TSX/JSX. Triggers when writing or reviewing React components to check structure, hooks, accessibility, performance, and TypeScript patterns.Votes: 0GitHub stars: 4
- React PerformanceReact performance: unnecessary re-renders, memoization (React.memo/useMemo/useCallback), React Compiler, Context, concurrent features, code splitting, and Core Web Vitals.Votes: 0GitHub stars: 4
- React QueryGuidelines for using React Query for data fetching, caching, and server state synchronization in React applicationsVotes: 0GitHub stars: 4
- Redis CoreCore Redis modeling — choose the right data structure and consistent colon-separated key names. Use when designing a Redis data model, caching, building counters, leaderboards, or sessions, choosing Hash vs JSON, or reviewing key naming.Votes: 0GitHub stars: 4
- Redis Query EngineRedis Query Engine (RQE) — FT.CREATE schema design, field-type choice, DIALECT 2 syntax, efficient FT.SEARCH/FT.AGGREGATE, zero-downtime index swaps. Use when creating, querying, or optimizing search indexes on Hash or JSON documents.Votes: 0GitHub stars: 4
- Redis SecurityRedis production hardening — authentication (requirepass/ACL users), TLS, least-privilege ACLs, network restriction (bind, protected-mode, firewall), and disabling dangerous commands. Use when deploying, locking down, or auditing a Redis instance.Votes: 0GitHub stars: 4
- RefactorSurgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.Votes: 0GitHub stars: 4