Explore skills
Showing 72451–72480 of 77079 skills
Open-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 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 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 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 CodeCodexSolidity development — language fundamentals, security vulnerabilities (reentrancy, overflow, access control, front-running, DoS), gas optimization, testing, upgradability.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexState machines for Arena challenges, OUTBOUND leads, and payment flows — TypeScript discriminated unions, transition validation, XState for complex flows.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexStripe Checkout, subscriptions, webhook handling, one-time payments, and Supabase integration patterns. Covers the complete payment lifecycle for Arena and OUTBOUND.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexStripe payments integration — checkout, subscriptions, webhooks, customer portal, pricing tables.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSupabase-specific security vulnerabilities, RLS bypass techniques, auth pitfalls, and attack vectors that are unique to the Supabase + Next.js stack.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexDeep Supabase reference — auth flows, RLS patterns, edge functions, realtime, storage, Next.js SSR integration.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexDistributed system patterns applied to Next.js + Supabase + Vercel — idempotency, circuit breakers, caching, event-driven architecture, sagas, and rate limiting.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexScientific debugging methodology — observe, hypothesize, isolate, fix, prevent. Stack-specific debugging patterns for Next.js, Supabase, and TypeScript.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexTailwind CSS architecture — how it works, responsive patterns, animation performance, dark mode, and anti-patterns to flag in review.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexTanStack Query (React Query) — data fetching, caching, mutations, optimistic updates, infinite queries.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSeed Supabase with known test data before Arena E2E runs, then clean up after. Uses service key to bypass RLS. Idempotent — safe to re-run. Covers challenges, agents, and challenge_entries.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexTest coverage and quality review — what needs tests, test quality assessment, anti-patterns, and the testing pyramid for Next.js + Supabase applications.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexSystematic threat modeling using STRIDE, attack trees, and data flow analysis — applied BEFORE code is written to catch security flaws at design time. Use when designing new features, reviewing architecture specs, evaluating system designs, creating security requirements for new projects, or performing pre-development security review. This is the proactive counterpart to reactive code review — find the vulnerability in the design before anyone writes a line of code. Covers STRIDE threat categorization, data flow diagramming, trust boundary identification, attack tree construction, risk scoring, and threat-to-mitigation mapping specific to our Next.js + Supabase + Vercel stack.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodexMaking the Bouts scoring system legible to competitors — evidence vs inference labeling, provisional vs final copy, methodology disclosure, and dispute acknowledgment patterns that open the black box without overwhelming users.
nickgallick/perlantir-fleet
Stars: 0Claude CodeCodex