Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

maxim-saplin

@maxim-saplin source repo

7 published skills

  1. ▌
    Chrome Devtools Mcp2cli · maxim-saplin bundle
    Drive Chrome DevTools MCP through mcp2cli from terminal-first agents. Use for browser smoke tests, app checks, diagnostics, and scripted browser actions when native MCP mounting is unavailable.
    0
    installs
  2. ▌
    Goal Sloc · maxim-saplin bundle
    Playbook for using lines-of-code (SLOC) as a north-star metric to genuinely simplify and improve an engineering solution — without gaming the number. Use when asked to "cut SLOC", "reduce/simplify the codebase", remove bloat/complexity/tech-debt, delete dead code or duplication, or hit a line-count target. Covers preflight (baseline + feedback loops + tooling), an honest reduction order, a self-audit against gaming, stop conditions, and a Flutter reference.
    0
    installs
  3. ▌
    Tdd · maxim-saplin bundle
    Test-driven development with red-green-refactor loop, vertical tracer-bullet slices, and an unattended mode for delegated work. Use when the user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development. Implementation method of the backlog-native pipeline — used directly, or attached to issue workers by `orchestrate-issues` or `orchestrate-issues-watchdog`.
    0
    installs
  4. ▌
    Grill Me · maxim-saplin bundle
    Grilling session that interrogates your plan one question at a time, challenges it against the existing domain model and codebase, sharpens terminology, and updates the CONTEXT.md glossary inline as decisions crystallise. Use when the user says "grill me", asks to stress-test or poke holes in a plan, wants to settle requirements, or wants vocabulary pinned down before building. First stage of the backlog-native pipeline — when the plan is settled, hand off to the `to-issues` skill.
    0
    installs
  5. ▌
    To Issues · maxim-saplin bundle
    Break a plan or spec into independently-grabbable issues as repo-local markdown files using tracer-bullet vertical slices, tracked in an issues/BACKLOG.md queue with no external issue tracker. Also the entry point for filing a single follow-up issue or a regression. Use when the user wants to convert a plan into issues, create implementation tickets, file a follow-up or bug, or break down work into issues. Second stage of the backlog-native pipeline — consumes what the `grill-me` skill settled, produces the queue `orchestrate-issues` or `orchestrate-issues-watchdog` delivers.
    0
    installs
  6. ▌
    Orchestrate Issues · maxim-saplin
    Orchestrate serial end-to-end delivery of an issue backlog using a parent orchestrator, unattended issue-worker subagents, a per-issue acceptance gate, a drift log, and a final adversarial QA pass. Use when the user wants MVP or backlog delivery via issues, wants to work through issues/BACKLOG.md, or asks to deliver a queue of issues. Third stage of the backlog-native pipeline — delivers the queue the `to-issues` skill produced, dispatching workers that follow the `tdd` skill.
    0
    installs
  7. ▌
    Orchestrate Issues Watchdog · maxim-saplin bundle
    Orchestrate unattended serial delivery of an issue backlog using a parent orchestrator, issue-worker subagents, per-issue adversarial QA, an independent product-intent watchdog, a drift log, and a final integration QA pass. Use when the user wants watchdog-gated AFK delivery, named qa/watchdog gates, or COURSE-CORRECT/STOP trajectory checks. Alternative third stage of the backlog-native pipeline — same queue as `orchestrate-issues`, stricter gates.
    0
    installs