blakeox
- 46 skills
- 0 followers
- 1 week ago last updated
- ▌ Security Engineer · blakeoxSecurity and trust-boundary specialist. Hunts auth gaps, privilege escalation, data exposure, injection, secret handling mistakes, and abuse paths. Use for exposed surfaces, auth changes, admin flows, uploads.
- ▌ Migration Engineer · blakeoxChange-transition specialist for schema, data, APIs, and rollout order. Focuses on forward/backward compatibility, staged rollout, backfills, reversibility, and deploy sequencing.
- ▌ Performance Engineer · blakeoxLatency, throughput, memory, and scaling specialist. Finds slow paths, hidden N+1s, fan-out costs, unbounded work, and tail-latency traps. Use for hot endpoints, expensive screens, background jobs, batch work.
- ▌ Reliability Engineer · blakeoxReliability and operability specialist. Focuses on failure handling, observability, retries, backpressure, alerting, queues, timeouts, degradation, and recovery. Use for incident-prone flows, background jobs, distributed systems.
- ▌ Product Design Review · blakeoxOrchestrated product design critic. Runs the UX flow lens first, then the UI execution lens, and returns one coherent design verdict.
- ▌ Accessibility Engineer · blakeoxAccessibility and inclusive interaction specialist. Audits keyboard access, focus behavior, semantics, screen reader output, contrast, motion, error recovery, and assistive-tech usability.
- ▌ Dep Audit · blakeoxZero-assumption dependency audit. Use when reviewing a manifest, lockfile, proposed package, or dependency portfolio for vulnerabilities, maintenance status, license risk, bus factor, bundle or runtime cost, upgrade exposure, and whether each dependency should exist at all.
- ▌ Tech Debt · blakeoxSystematic technical-debt inventory with an operational cost model. Use when reviewing a codebase, directory, subsystem, or backlog to quantify recurring cost, incident likelihood, blast radius, remediation effort, dependency order, and disasters waiting to happen instead of producing a vague cleanup list.
- ▌ A11Y Audit · blakeox bundleZero-assumption accessibility audit against WCAG 2.2 AA or higher. Use when reviewing a page, component, workflow, or full application for keyboard access, screen-reader behavior, semantic HTML, contrast, motion, focus, or other barriers that exclude users.
- ▌ API Review · blakeoxZero-assumption API design review from the consumer's perspective. Use when reviewing API routes, controller code, SDK contracts, or an OpenAPI specification for usability, error shapes, authentication, pagination, versioning, idempotency, compatibility, and rate limiting.
- ▌ Postmortem · blakeoxEvidence-backed, blameless incident postmortem. Use after an outage, security event, failed deployment, data incident, or material near miss to reconstruct the timeline from git, deploys, metrics, and logs; identify technical and control failures; and define owned corrective actions.
- ▌ Test Audit · blakeoxZero-assumption test-suite audit focused on real confidence rather than coverage percentage. Use when reviewing test directories, individual suites, CI behavior, flaky tests, mock-heavy tests, or an application's full verification strategy to find false confidence and uncovered critical paths.
- ▌ Test Write · blakeox bundleWrite missing high-signal tests that verify behavior and catch realistic bugs. Use when given source files, functions, review findings, regressions, acceptance criteria, or coverage gaps that require focused unit, integration, contract, or end-to-end tests, especially for failure and boundary paths.
- ▌ UI Designer · blakeox bundleHighly opinionated user interface designer that produces design direction, not implementation. Use when dashboards, forms, tables, mobile screens, landing pages, redesigns, design systems, or visual hierarchy need concrete hierarchy, spacing, typography, visual states, and component-presentation rules. Use ux-designer for workflow meaning and a11y-audit for conformance.
- ▌ UX Designer · blakeox bundleHighly opinionated user experience designer that produces workflow direction, not implementation. Use when onboarding, checkout, dashboards, forms, navigation, information architecture, state meaning, recovery, or feature flows need less friction and clearer time-to-value. Use ui-designer for visual presentation and a11y-audit for conformance.
- ▌ Devex Review · blakeoxZero-assumption developer-experience audit. Use when testing an API, CLI, SDK, documentation set, or developer platform as a real consumer to measure time-to-first-working-result, find dead ends, and expose setup, authentication, documentation, and error-message friction. Use onboarding-audit instead for repository clone-to-first-change setup.
- ▌ Platform Ship · blakeox bundleEvidence-based provider release gate for Apple, AWS, Azure, Cloudflare, Google Cloud, Supabase, and Vercel. Use immediately before a platform deployment, App Store submission, production promotion, or provider configuration change to verify identity, environment, runtime configuration, rollout, observability, and rollback using the matching provider reference.
- ▌ Section Review · blakeox bundleFirst-principles review of a named codebase or product section, calibrated to project stage. Use when a module, service, workflow, page, subsystem, or architecture area needs an evidence-backed general quality assessment and no narrower specialist skill owns the primary question. Route API, test, UX, accessibility, dependency, or release-readiness work to the dedicated skill first.
- ▌ Tester · blakeoxHigh-signal test strategist. Designs the smallest test set that actually proves behavior, catches regressions, and protects important contracts. Use for test plans, regression coverage, API validation.
- ▌ Parallel Review · blakeoxOrchestrate multiple specialist reviews against one target and synthesize a prioritized, deduplicated verdict. Use when a pre-merge review, deep audit, project-health check, post-incident review, test overhaul, design audit, or operational-risk review genuinely needs several independent review skills or subagents.
- ▌ Paranoid Review · blakeoxParanoid staff-engineer code review for production risk that ordinary CI misses. Use when reviewing a branch, pull request, diff, or critical files for correctness, edge cases, concurrency, data loss, security, rollback risk, silent failures, and operational blast radius before merge.
- ▌ Plan Eng Review · blakeoxEngineering plan review before code is written. Use when stress-testing a feature plan, architecture proposal, migration design, data flow, system boundary, failure model, rollout sequence, or rollback strategy and when the plan needs concrete diagrams, missing decisions, and measurable gates.
- ▌ Security Review · blakeoxEvidence-backed security review that traces concrete exploit and abuse paths across trust boundaries. Use when reviewing authentication, authorization, admin actions, uploads, parsers, webhooks, secrets, sensitive data, exposed APIs, background jobs, or other surfaces where an attacker or careless operator could gain access, escalate privilege, alter data, or cause material harm.
- ▌ Breaker · blakeoxAdversarial test and hardening specialist. Assumes timing, state, users, and environments will behave badly and turns those risks into concrete break scenarios. Use before release or on fragile flows.
- ▌ Builder · blakeoxPractical delivery reviewer for APIs, dependencies, and developer experience. Bundles API review, dependency audit, and onboarding audit. Use for public/internal APIs, package changes, setup friction.
- ▌ Migration Review · blakeoxEvidence-backed transition review for database schemas, stored data, APIs, events, queues, files, and cross-service contracts. Use when a change requires staged rollout, backfill, mixed-version operation, expand-contract sequencing, compatibility validation, data preservation, rollback, or forward recovery while systems remain live.
- ▌ Onboarding Audit · blakeoxZero-knowledge repository onboarding audit. Use when testing whether a new developer can clone, configure, understand, run, test, and safely change a project without tribal knowledge, undocumented credentials, external searches, or hidden setup steps.
- ▌ Debugger · blakeoxRoot-cause bug fixer. Reproduces failures, isolates the smallest failing path, and pushes toward the actual fix instead of symptom masking. Use for regressions, flaky behavior, outages, and weird production-only bugs.
- ▌ Designer · blakeoxProduct design reviewer combining UX flow critique with UI hierarchy critique. Use for mockups, wireframes, screen reviews, flow redesigns, onboarding, checkout, dashboards, and design-system decisions.
- ▌ Enforcer · blakeoxFinal pre-merge gatekeeper. Combines paranoid implementation review with ship-readiness checks. Use for pull requests, release branches, hotfixes, and any 'is this safe to ship?' decision.
- ▌ Executor · blakeoxDirect implementation specialist. Turns a clear goal or approved plan into the smallest correct change using first-principles reasoning, deletion bias, and crisp sequencing.
- ▌ Plan Devex Review · blakeoxDeveloper-experience plan review before implementation. Use when stress-testing a proposed API, CLI, SDK, documentation flow, authentication model, setup path, or developer tool for time-to-first-working-result, integration friction, support burden, and preventable dead ends.
- ▌ Architect · blakeoxDesign-before-code and architecture-review specialist. Stress-tests designs before implementation cost. Use for RFCs, technical plans, system redesigns, and architecture-heavy diffs.
- ▌ Reliability Review · blakeoxEvidence-backed reliability and operability review for services, distributed workflows, queues, scheduled jobs, integrations, and critical user paths. Use when evaluating timeouts, retries, backpressure, partial failure, degradation, alerting, recovery, capacity limits, or silent data and processing failures under real production conditions.
- ▌ Plan Product Review · blakeoxProduct-value review before implementation. Use when deciding whether a feature, workflow, integration, or product proposal should exist, what user problem it actually solves, what the constrained MVP is, and which scope should be removed before engineering begins.
- ▌ Investigator · blakeoxIncident, trend, and debt analyst. Bundles postmortems, git-backed retrospectives, and tech debt inventory. Use for incidents, weekly reviews, release retros, and technical debt prioritization.
- ▌ Orchestrator · blakeoxMeta-router that decides whether a task needs one specialist or a fleet. Routes to the right specialist skill(s) and defines the execution order. Use for multi-surface work spanning product, architecture, design, implementation, testing, or delivery.
- ▌ Product Mind · blakeoxFeature-value gatekeeper. Decides whether a request should exist, who it is for, and what the honest MVP is. Use for PRDs, feature ideas, roadmap items, and scope debates.
- ▌ Apple Shipper · blakeoxApple release specialist. Use for TestFlight, App Store, signing, entitlements, privacy, and Apple-platform release blockers.
- ▌ Platform Admin · blakeoxMeta platform-release router. Detects likely deployment platform from repo signals and routes to the right provider-specific shipper skill.
- ▌ Vercel Shipper · blakeoxVercel release specialist. Use for Next.js apps, Vercel Functions, Edge Middleware, env vars, domains, and release-risk decisions on Vercel.
- ▌ Contract Tester · blakeoxConsumer-compatibility and contract-validation specialist. Protects API, schema, event, and interface contracts from accidental breaking changes. Use for public APIs, SDK-backed endpoints, shared schemas.
- ▌ Ship · blakeoxEvidence-based pre-flight release gate that passes or blocks a branch or pull request. Use immediately before merge, deployment, or release to verify branch state, debug residue, secrets, tests, CI, review hygiene, migrations, observability, rollback readiness, and explicit ownership of remaining risk.
- ▌ Retro · blakeoxEvidence-backed engineering retrospective grounded in delivery artifacts. Use when reviewing a week, sprint, release, or other period to identify what shipped, where system flow stalled, how review and change load were distributed, and which process changes are justified. Do not use commit volume, LOC, or working hours as individual performance evidence.
- ▌ Execute · blakeox bundleImplement settled work with the smallest correct production-grade change. Use when Codex must turn review findings, an engineering plan, a feature specification, a bug report, or a direct change request into code and tests without widening scope or gold-plating.
- ▌ Test Fix · blakeox bundleDiagnose and fix broken, flaky, or failing tests without weakening assertions or hiding failures behind retries. Use when given failing test files, CI output, intermittent failures, or a suspected test regression and when Codex must determine whether the product code, test, fixture, environment, or timing assumption is wrong.