matoous/son-of-anton
Small, adaptable Codex skills for candid engineering, investigation, and writing.
Apply a lightweight engineering workflow with simple designs, evidence-led decisions, focused verification, candid feedback, and plain writing. Use when the user asks for Anton or this working style.
Sketch data models, interfaces, and ownership before a consequential design change. Use when asked to architect or design a feature, or when implementation would otherwise commit to an uncertain structure.
Write, review, refactor, test, and debug modern idiomatic Go in my preferred style.
Explain how existing code or a subsystem works, tracing runtime flow, ownership, and boundaries from source evidence. Use for code walkthroughs and placement or layering questions; use why for historical rationale.
Find and read RFCs, Internet-Drafts, and working-group material in IETF Datatracker. Use for standards research, RFC or draft lookups, protocol requirements, document status, and revision history.
Maintain SumUp's Python, PHP, Go, TypeScript, .NET, Java, and Rust SDK repositories, including OpenAPI generators, public exports, dependency upgrades, and failing PRs or CI. Use for work on these SDKs individually or across languages; consumer checkout integration work belongs to the integration skills.
Coordinate parallel Codex subagents and return one consolidated report. Use when the user asks to swarm a task or requests parallel coverage, exploration, or competing solutions.
Fix a bug with a focused failing-before and passing-after regression check. Use when the user requests TDD or a regression test, or when a bug has a clear, cheap local test path.
Write or review technical documentation, RFCs, READMEs, PR descriptions, and commit messages for a specific audience and task. Use for technical writing work; use unslop for a wording-only cleanup.
Edit prose to remove filler, vague claims, and artificial phrasing while preserving meaning and voice. Use when asked to unslop, simplify, or make writing sound natural and direct.
Investigate why existing code or a design decision took its current shape using history, discussion, and documentation. Use for rationale and tradeoff questions; use how for runtime behavior.