sealad886

Use first to route end-to-end, ambiguous, multi-phase, review, release, incident, or decommission work through the minimum sufficient project-delivery lifecycle when depth, state, or authority is unclear.

Close delivery by capturing outcomes, learning, technical debt, follow-up work, reusable decisions, and measurable process improvements in canonical project knowledge.

Coordinate delivery across authorized trackers, documents, meetings, calendars, messages, and operational systems while preserving canonical sources, exact targets, write authority, traceability, and read-after-write evidence.

Update canonical project knowledge for users, developers, operators, reviewers, releases, and future agents. Use for docs-only work or whenever a change affects behavior, interfaces, configuration, architecture, operations, migration, status, or release communication.

Prepare, validate, and—when explicitly authorized—execute integration, CI/CD, versioning, deployment, rollback, monitoring, post-release verification, and hotfix/change-management work.

Assess and improve security, privacy, risk, reliability, observability, supportability, and operational readiness across requirements, design, implementation, review, or release.

Select, execute, and report risk-based validation for a change or release candidate. Use for unit, integration, end-to-end, contract, regression, invariant, static, performance, security, CI-parity, and failure-triage evidence.

Turn accepted requirements and design into a risk-scaled delivery plan with WBS, milestones, dependencies, critical path, ownership, estimates, RAID, communication, change control, and multi-PR/release slicing.

Optimize Python MLX inference and generation loops with warmup, batching, cache handling, synchronization, quantization, and memory checks.

Guide MLX Metal profiling, mx.fast escalation, custom Metal kernels, and C++ extensions when profiling proves kernel-level bottlenecks.

Route Python-first MLX optimization work on Apple Silicon to focused audit, training, inference, Metal, or bridge workflows.

Audit Python MLX repos for lazy-eval, synchronization, compile, dtype, memory, progress, and benchmark issues.

Advise on Python-first MLX integration with Swift, C, C++, and non-native language boundaries.

Optimize Python MLX training loops with value_and_grad, accumulation, checkpointing, dtype, validation cadence, memory telemetry, and progress reporting.

Design how Chromium extensions interact with page DOM and coordinate between content scripts, service workers, and extension pages. Use when deciding how to inject code, pass messages, structure isolated-world logic, or debug cross-context state flow.

Prepare Chromium extensions for packaging, Chrome Web Store submission, Microsoft Edge Add-ons submission, and controlled release management. Use when assembling a release build, writing listing metadata, validating review readiness, or planning update rollout.

Review Chromium extensions for least-privilege permissions, safe host access, CSP and remote-code compliance, and narrow resource exposure. Use when adding permissions, auditing a manifest, preparing a store review narrative, or tightening extension security boundaries.

Debug Chromium browser extensions across service workers, content scripts, and extension pages, and write reproducible Playwright-based tests. Use when loading unpacked extensions, inspecting runtime contexts, building smoke tests, or diagnosing permission, lifecycle, and messaging issues.

Choose and implement the right Chromium extension UI surfaces such as popup, side panel, options page, commands, context menus, and offscreen documents. Use when deciding how the user should enter a workflow, where state should live, or how much UI should persist across tabs.

Plan Manifest V3 Chromium extensions around the right execution contexts, permissions, storage, and background model. Use when designing a new extension, migrating older background-page code, choosing between service workers and content scripts, or reviewing an extension manifest and folder layout.

Use when bumping npm package versions, publishing prereleases, promoting to stable, or reasoning about this repo's GitHub Actions-based npm release flow