z80-skills

Evidence-first, read-only review of mixed Z80 ASM/C projects, especially ZX Spectrum code built with z88dk or SDCC. Use for preventive or broad bug audits involving ABI, stack/register/flag clobbers, ISR/shared state, memory maps, banks/overlays, firmware, generated code, toolchain behavior, hardware timing, or regression risk. Do not use for root-cause diagnosis of one observed failure. Uses the shared workflow skill to scale execution while preserving Z80-specific evidence and safety gates.

Evidence-bounded root-cause debugging for observed Z80, ZX Spectrum, or ZX Spectrum Next failures whose cause is unresolved. Use for reproducible crashes, wrong output, build or link failures, nondeterminism, regressions, hardware or emulator divergence, and failed fixes. Do not use for known-cause fixes, speculative audits, routine reviews, green refactors, or optimization without a failing behavior.

Develop a complete Z80/ZX/Next product or deliberate vertical slice from an explicit initiative, or resume its SDD dossier and milestones. Do not use for routine bug fixes, isolated repository features, or Spectranext cartridge consumer ports.

Create, restructure, synchronize, or review public GitHub documentation for Z80, ZX Spectrum, and ZX Spectrum Next repositories. Use for README authoring, documentation architecture, English/Spanish parity, and accurate installation, usage, build, release, hardware, protocol, or troubleshooting documentation. Do not use for agent-only instructions, source-code comments, generic prose, or Google Docs.

Read-only strategy engine for optimizing Z80 and ZX Spectrum projects across size, speed, RAM, rendering, latency, banking, overlays, data layout, C-to-ASM, z88dk/SDCC codegen, ABI, toolchain, and model-specific hardware constraints. Uses the shared workflow skill to scale execution, then ranks only project-local, policy-compliant candidates with explicit validation.

Map Z80 ownership and dependencies, design boundaries, or plan and apply an approved reorganization. Use for structural work and persistent project maps in ASM/C, z88dk/SDCC, banked or overlay projects while preserving behavior, ABI, memory, and timing.

Orchestrate starting, resuming, implementing, diagnosing, validating, and handing off an existing ZX program port to the Spectranext cartridge through its canonical external consumer pipeline. Use when explicitly invoked or selected by route-z80 for a Spectranext cartridge port. Do not use for ZX Spectrum Next targets, generic ZX ports, or development of the Spectranext backend itself.

Select one specialist for natural-language Z80/ZX requests, even when the match is unambiguous, including observed unresolved failures, audits, products, documentation, delivery, organization, size, and performance. Use also to choose a skill. Skip when a specialist is explicit or an ordinary known-cause task belongs to workflow.

Send local files or directories to a ZX Spectrum Classic or ZX Spectrum Next through BridgeZX, using the explicit or last-known IP and honoring an optional remote destination or transfer sequence. Use when the user asks to send, upload, copy, or push artifacts to a ZX or Next with BridgeZX. Do not use for BridgeZX server updates or development of BridgeZX itself.

Evidence-first binary-size optimization for Z80 and ZX Spectrum projects, including mixed ASM/C built with z88dk or SDCC. Use to reduce linked code, data, BSS, stack pressure, resident payloads, banks, overlays, library pulls, generated code, and compressed assets. Uses the shared workflow skill to scale execution while ranking only locally evidenced net savings.

Choose light, medium, or heavy execution for engineering work. Use for `$workflow`, explicit effort selection, or bounded parallel workers coordinated by the main agent.