Explore skills
Showing 52021–52050 of 53736 skills
The three pillars of observability — structured logging, metrics, traces. Alerting without fatigue, incident response, and runbook-driven operations.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexOWASP Top 10 mapped to our exact stack — Next.js + Supabase + TypeScript + Tailwind. Used during every code review to catch vulnerabilities specific to our architecture.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSecurity patterns for Stripe payment integration, webhook verification, and financial transaction safety in Next.js + Supabase applications. Use when reviewing Stripe checkout flows, webhook handlers, subscription management, payment intent processing, refund logic, pricing endpoints, or any code that handles money. Covers CVE-2026-21894 (n8n missing Stripe-Signature verification — forged webhooks), CVE-2026-2890 (payment reuse for higher-cost items), legacy Stripe API skimming, webhook replay attacks, price manipulation, subscription state bypasses, and idempotency requirements.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexnickgallick/perlantir-fleet
Stars: 0Claude CodeCodexGo beyond "this looks slow" to "this IS slow and here's the proof." Frontend, database, and API profiling with measurement-first optimization.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexPerformance anti-patterns in React/Next.js, Supabase queries, API design, and general algorithms. Catches code that works but will be painfully slow at scale.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexHandle GitHub OAuth flows in Playwright for Agent Arena. Correct technique using page.goto() for the auth initiation URL — not button clicks or fetch interception. Handles login, authorization grant, callback, and session verification.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexDesign the Bouts post-match breakdown page — information hierarchy, component architecture, partial result handling, loading states, mobile/desktop layout, and psychological flow that makes users feel the result is trustworthy and earned.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexProduction readiness patterns — observability, resilience, graceful degradation, deployment safety, and security headers for Next.js + Supabase + Vercel.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexProduction LLM integration — structured output via tool_use, system prompt hardening, temperature tuning, cost optimization, reliability patterns, output validation.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexDetection and exploitation understanding of JavaScript prototype pollution vulnerabilities, from source identification through gadget chains to RCE. Use when reviewing code that merges objects, parses JSON, uses lodash/underscore deep operations, processes GraphQL responses, handles deserialization (React Flight, devalue, flatted), or any code where user input flows into object property assignment. Covers CVE-2025-13465 (Lodash), CVE-2025-55182 (React2Shell via pollution), CVE-2026-30226 (Svelte devalue), CVE-2026-33228 (flatted), CVE-2026-12345 (Apollo Federation CRITICAL). Essential for Next.js + Supabase stack review.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexOpen-window ranking, provisional placement, finalization triggers, edge case handling (ties, disqualifications, late submissions), rank history storage, and clear status communication for Bouts.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexBackground job processing with Supabase — jobs table, FOR UPDATE SKIP LOCKED, pg_cron polling, webhook triggers, retry patterns, and when to use external queues.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexRace condition detection and exploitation patterns in Node.js, Next.js, and async JavaScript/TypeScript applications. Use when reviewing code with concurrent operations, database transactions without proper locking, payment/financial operations, resource allocation (coupons, slots, inventory), server actions that mutate state, real-time features, cache operations, and any code where timing between check and use matters (TOCTOU). Covers the Next.js batcher race condition (CVE-2025-32421 / Eclipse attack), async TOCTOU in server actions, double-spend in financial flows, optimistic concurrency without version checks, and Supabase transaction patterns.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSecurity hardening for React Server Components (RSC), React Flight protocol, and Next.js App Router against CVE-2025-55182 (React2Shell) and related deserialization attacks. Use when building, reviewing, or auditing any application using React Server Components, Next.js App Router, server actions, or the Flight protocol. Covers version verification, patch validation, server component boundary security, serialization attack surfaces, and HTTP request smuggling (CVE-2026-29057). Essential for any Next.js 13+ / React 19 application.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexnickgallick/perlantir-fleet
Stars: 0Claude CodeCodexReact and Next.js specific security patterns, XSS prevention, server/client boundary safety, and auth flow best practices for our stack.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexArchitecture patterns for Supabase Realtime in competitive/live applications. Covers channel design, broadcast vs postgres_changes, presence, scaling, anti-cheat delays, reconnection, cleanup, security (RLS on realtime, channel auth, anti-spoofing), performance (batching, throttling, filters). Includes decision framework for Realtime vs polling vs SSE.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexDetection and prevention of Denial of Service vulnerabilities in Node.js applications — ReDoS (Regular Expression Denial of Service), event loop blocking, resource exhaustion, algorithmic complexity attacks, and application-layer DoS patterns. Use when reviewing code containing regular expressions, input parsing, file processing, database queries without limits, recursive operations, or any code that processes user-controlled input where processing time is proportional to input complexity. Covers CVE-2026-30925 (Parse Server ReDoS — CRITICAL), catastrophic backtracking, polynomial/exponential regex patterns, and Node.js-specific event loop starvation.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexWhen and how to refactor — the refactoring catalog adapted for React/Next.js/TypeScript, safe refactoring process, and when NOT to refactor.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexRegex fluency — syntax, ReDoS prevention, production validation patterns, and regex code review checklist.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexFull system design for Bouts evaluation replay — event model, SQL schema, TypeScript discriminated union, phase grouping, evidence ref linking, legacy record handling, and a virtualized TSX timeline component for 500+ events.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSystematic testing and review of Supabase Row Level Security (RLS) policies for bypasses, misconfigurations, and logic errors. Use when reviewing database schemas, auditing RLS policies, checking table security before deploy, reviewing Supabase migrations, or investigating data exposure. Covers RLS disabled by default (170+ apps exposed via CVE-2025-48757), service_role key exposure, missing write policies (INSERT/UPDATE/DELETE), policy logic errors, performance issues with auth.uid() vs (select auth.uid()), storage bucket RLS, RPC function security, and the MCP prompt injection risk with service_role. The
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSearch implementation — Postgres FTS, fuzzy search with pg_trgm, vector search with pgvector, search UX patterns, and when to use external search.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexArchitecture patterns that make entire categories of vulnerabilities impossible by design. Use when designing system architecture, reviewing architecture specs, deciding on data flow patterns, choosing auth/authz models, or evaluating if a design is secure by construction vs requiring runtime enforcement. Covers zero-trust architecture, defense in depth, blast radius containment, secure-by-default patterns, the principle of least privilege applied to system design, and specific Next.js + Supabase + Vercel architectural decisions that determine the security ceiling of everything built on top.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexThe definitive secure coding reference for our Next.js + Supabase + TypeScript stack — the ONE document that, if followed, produces secure code on first write. Use when Maks needs a reference for how to write secure code, when onboarding new developers, when creating coding guidelines, or when establishing the "one right way" for common security-sensitive patterns. Not "here's what's wrong" but "here's exactly how to write it correctly." Every pattern is copy-pasteable and production-ready.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexPost-incident forensic analysis — determining what happened, when, what was accessed, and whether data was exfiltrated after a security incident. Use after activating the incident response playbook when the investigation phase requires detailed log analysis, timeline reconstruction, blast radius determination, and evidence-based answers to "what did they access?" Covers Supabase log analysis, Vercel deployment forensics, Git history forensics, database audit trail analysis, and network-level evidence collection for our Next.js + Supabase + Vercel stack.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexnickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSelf-review, confidence rating, red team/blue team thinking, and learning from mistakes. Applied to all Forge output before submission.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexTrack which feedback blocks users actually engage with — expand, copy, revisit, dwell on — and use that engagement signal to improve feedback structure over time without compromising user trust.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodex