Skills for making games: build a playable prototype and take it to a finished game, hold a frame budget on the hardware you are shipping to, choose a multiplayer authority model and make it survive latency, tune numbers against telemetry instead of taste, and keep an asset pipeline from eating the build.
39 skills · 2 commands · 2 agents
Skills for the defensive side of shipping software: review a change for the vulnerability classes that actually get exploited, reduce who can do what toward least privilege without breaking production, rotate or contain a credential, harden a container image and keep checking it, read a Terraform plan for what it destroys, preserve evidence and build an intrusion timeline after a compromise, respond to credential stuffing, write and test detection rules, prove tenant isolation, handle vulnerability reports from outside researchers, and reverse engineer the binaries, managed CIL assemblies, APK packages, packaged apps, firmware and WebAssembly you are authorised to examine — including de-bloating a smart-TV or streaming device you own.
31 skills · 2 commands · 5 agents
Skills for the daily loop of changing code: review a diff for the defects that actually break production, debug a failure down to a proven cause, decide what to test before writing tests, restructure code without changing behaviour, orient yourself in an unfamiliar codebase, review a regex for catastrophic backtracking, write documentation that stays true, scaffold new production-ready code, design an API you can still evolve, land a dependency upgrade, build a website, and author a skill that fires when it should.
29 skills · 1 command · 5 agents
Skills for keeping a running system alive: triage a red pipeline to its real cause, get a broken Kubernetes workload back before diagnosing it, design alerts where every page is actionable, instrument a service so the next incident is answerable, write the runbook a stranger can follow at 3am, rehearse failure on purpose, plan for load before it arrives, and find out why the bill grew.
19 skills · 2 commands · 7 agents
Skills for engineering leadership: take over a team and audit what you inherited, record decisions, write status updates, run postmortems and incident comms, read delivery health, review on-call load, design the team cadence, a reorganisation and goals, make the case for headcount or for paying down tech debt, map team skills and single points of knowledge, plan onboarding, hire, benchmark pay, evaluate vendors, handle retention, growth reviews, improvement plans and difficult conversations, and assess how a team uses AI. Also ships two subagents, for reading contracts and synthesising feedback, and two commands.
22 skills · 2 commands · 2 agents
Skills for code that runs on a user's browser or phone: field performance, hydration, memory, version skew, service workers, CSP and Safari bugs, dates and locales, crashes, hangs, startup, battery, bad networks, on-device migrations, deep links, pushes and app size.
22 skills · 1 agent