HyperCode-V2.4

Deploys and manages the mint-pet-confirm Supabase Edge Function in HyperCode-V2.4. Use when deploying, updating, debugging, or verifying the pet minting confirmation flow on Base Sepolia.

HyperCode V2.4 Trivy CVE scanning — Phase 8 PR gate, Phase 9 hardening pattern (apt + pip pinning), weekly fleet scan, baseline of 13 HIGH (all Debian-unfixable). Use when the user says "trivy scan", "CVE check", "scan agents", "Phase 9 hardening", "build secure", "security pipeline", or wants to vet a new Dockerfile.

Running, rebuilding, debugging, and inspecting the HyperCode V2.4 29-container Docker stack — compose ops, network topology (frontend-net/backend-net/agents-net/data-net/obs-net), agent ports (127.0.0.1:), health checks, log tailing, and the network-migrate script. Use when the user says "containers down", "compose up", "rebuild agents", "agent X not healthy", "redis/postgres connection", "network isolation", or hits any Docker stack issue.

HyperCode V2.4 Phase 10N OTLP distributed tracing — OpenTelemetry → Tempo → Grafana. View traces, debug missing spans, the OTLP_EXPORTER_DISABLED flag. Use when the user says "tracing", "Tempo", "OTel", "OTLP", "traces missing", "view a request flow", "Grafana traces", or "Phase 10N".

HyperCode V2.4 Phase 10 status board (10A FastAPI/starlette → 10N OTLP tracing) — what shipped, what's next, where each phase lives. Use when the user asks "what phase are we on", "phase 10X status", "what's next after 10K", "is 10F live", or wants to plan/extend a Phase 10 mission.

HyperCode V2.4 Stripe Checkout + webhook flow — Phase 10F (API), 10G (DB writes), 10I (e2e), 10K (price IDs locked). Routes, prices, webhook events, signature verification, rate-limit exemption. Use when the user says "stripe", "checkout", "webhook failing", "subscription event", "price ID", "10F/10G/10I", or hits any payment-related issue.

Full Railway cloud deployment mastery — CLI commands, deployment patterns, database management, environment config, CI/CD pipelines, debugging, scaling, and Docker workflows. Use this skill whenever the user mentions Railway, railway.app, `railway up`, deploying to Railway, Railway services, Railway databases, Railway volumes, Railway env vars, Railway logs, Railway domains, Railway CI/CD, or any Railway error or debug scenario. Also trigger for HyperCode V2.4, BROski Bot, HyperAgent-SDK, or any Hyperfocus Zone service that needs cloud deployment on Railway. Even if the user just says "deploy my app" or "get this live" and Railway is in context — use this skill. ALWAYS trigger for Railway topics, even if the user only mentions one small aspect of it.

Designs and builds Discord servers for the Hyperfocus Zone. Invoke when user wants to tidy up a Discord server, build new channels/roles, or optimize for neurodivergent focus.

HyperCode Mission Control dashboard — Next.js/React frontend patterns, CognitiveUplink WebSocket UI, useHyperSync hook, useSensoryProfile neurodivergent UX hook, and dashboard component conventions. Use when working on dashboard components, WebSocket client code, frontend state management, or the neurodivergent UI layer.

Spawns, configures, and registers new HyperCode agents into the Crew Orchestrator. Use when user asks to create a new agent, add a specialist to the system, or when Agent X needs to deploy a new capability. Handles agent spec creation, Docker service wiring, and Redis pub/sub registration automatically.

Configures and manages the HyperCode MCP (Model Context Protocol) gateway that connects Claude and other AI models to HyperCode services. Use when adding new MCP tools, debugging MCP connections, registering new servers, or wiring external services like GitHub, Slack, or databases into the agent ecosystem.

Guide the creation and onboarding of a new HyperCode agent in a neurodivergent-friendly, step-by-step way. Use when asked to create, scaffold, or register a new agent into HyperCode V2.4.

HyperCode competency reference pack. Invoke when onboarding devs or planning work needing Docker/FastAPI/agents/observability/security patterns.

Emil Kowalski's animation and micro-interaction principles for component-level polish. Use when adding animations, transitions, hover states, page transitions, state change effects, or any motion to UI components in the HyperCode dashboard or Course frontend. Also use when reviewing existing animations for quality.

Load testing and performance benchmarking for HyperCode V2.4. Use when writing k6 or locust load tests, setting up performance baselines, running stress tests against the API, verifying P99 latency targets, or adding load testing to CI. Target: 1000 req/sec, P99 < 100ms.

Build and manage Grafana dashboards, datasources, and alerts for HyperCode V2.4. Use when creating new dashboards, adding Prometheus panels, wiring Loki log queries, correlating Tempo traces, or setting up AlertManager webhooks. Also covers the Mission Control dashboard build.

Build the 5 ADHD-first Hyperfocus Features for HyperCode V2.4 — Micro-Achievement Git Hook, HyperSplit Agent, Session Snapshot Agent, Morning Briefing, and Focus/Panic Mode. Use when working on any of these 5 features or adding new neurodivergent-first tooling. Full build prompts and patterns inside.

Cross-repo integration patterns for the 3-repo HyperCode ecosystem — Course ↔ V2.4 ↔ SDK. Use when working on Merge Roadmap Phase 3 (agent access shop), Phase 4 (npm run graduate), or Phase 5 (course metrics in Grafana). Also covers API contracts, shared secrets, and the identity bridge between systems.

Stripe payment integration for HyperCode V2.4 — checkout sessions, webhook verification, plan management, and E2E testing. Use when working on Stripe checkout, webhook handling, payment success flows, or running local Stripe tests.

Supabase integration patterns for the HyperCode ecosystem — Edge Functions, RLS policies, DB webhooks, migrations, and the Supabase ↔ V2.4 sync bridge. Use when working on token sync, Supabase Edge Functions, database webhooks, RLS rules, or any Supabase-side work in the Course repo. Also covers the critical manual setup steps.

Design auditor and anti-slop detector. Use when cleaning up existing UI, doing a design review pass, refactoring older components, or before any UI tweaking phase. Run this FIRST on any surface that was built fast and needs polish. Catches AI slop, inconsistencies, accessibility issues, and design drift.

Premium dark UI aesthetic brain for HyperCode and BROski-verse surfaces. Use when designing new pages, dashboards, hero sections, token visualizers, dNFT game UI, or any surface that needs strong visual identity. Enforces dark OLED aesthetics, cinematic motion, and anti-generic patterns. Primary design driver for Mission Control, BROskiPets, and landing pages.

Instant session restore for the HyperCode ecosystem — reads WHATS_DONE.md, CLAUDE_CONTEXT.md, and recent git history to deliver a sharp "welcome back" briefing in seconds. Use this skill the moment Lyndz (or any HyperCode dev) says anything like: "where was I", "catch me up", "what was I doing", "what did I build", "remind me what's next", "restore context", "new session", "I forgot what I was doing", "what's the project status", or just opens a session and seems unsure where to start. Also trigger proactively at the start of any session in the HyperCode project if no clear task has been given yet. This skill is the antidote to ADHD context-switching paralysis — use it generously and early.

🧠 EXPERIMENTAL — HyperCode's agent self-awareness layer. Agents that know what they are, report their own cognitive state, detect their own performance degradation, and can formally petition the Evolutionary Pipeline for upgrades. Use when building self-aware agents, implementing health self-reporting, designing the agent upgrade petition system, or exploring the Consciousness Protocol spec.

The cognitive core of HyperCode. Handles LLM prompt assembly, memory injection, conversation history, RAG retrieval, and agent handoffs. Use when working on Brain.think(), memory caps, context overflow, prompt engineering, conversation persistence, or the handoff system between agents.

Builds and maintains the BROski Discord bot (commands, moderation, Redis caching, deployment). Use for Discord.py patterns, safety checks, environment setup, and Dockerized bot workflows.

Manages the BROski$ coin economy, XP system, achievements, and gamification for HyperCode. Use when awarding coins for completed tasks, leveling up agents or users, checking balances, or triggering achievement unlocks. Publishes all economy events to the BROski$ Redis channel.

Reviews code changes in the HyperCode codebase for quality, security, agent safety, and architectural consistency. Use when asked to review a PR, check new agent code, audit a module, or validate changes before merging. Applies HyperCode-specific patterns and checks MCP/Skills compliance.

Manages all Docker and Docker Compose operations for HyperCode services. Use when asked to start, stop, restart, scale, or inspect any HyperCode service, container, or network. Knows the full docker-compose file map and correct start order. Also handles log inspection and container health.

Manages HyperSync encrypted session handoff — serializes, compresses, and encrypts chat/session state so it can be resumed in a fresh context. Covers threshold detection, AES-256-GCM envelopes, single-use resume tokens, Redis storage, optional MinIO backchannel, and frontend resume flow.

Manages Redis pub/sub channels, streams, and memory for HyperCode inter-agent communication. Use when inspecting agent messages, publishing system events, debugging communication between agents, or wiring new agents into the event bus. Knows all HyperCode channel naming conventions.

Covers HyperCode's internal security model — AES-256-GCM encrypted envelopes, KEYRING key management, anti-replay via Redis nonces, JWT conventions, secret scanning, and threat model. Use when working on agent-to-agent communication security, adding new internal endpoints, rotating keys, or hardening the event bus.

Runs the HyperCode Skills 2.0 self-improvement loop. Tests, scores, and rewrites agent skills and prompts automatically using binary eval criteria. Use when asked to improve a skill, run evals, benchmark performance, or trigger the Karpathy autoresearch loop. This is the evolutionary pipeline trigger.

Create structured API documentation for a selected endpoint.

Generate a comprehensive unit test suite for the selected code.

Analyze and refactor selected code to improve performance.

Audit selected code for security vulnerabilities and propose fixes.