Autonomous knowledge base for the mini-SDD framework. Always read this skill when working on a mini-SDD project or when any message mentions mini-SDD, mini-sdd-context, mini-sdd-spec, mini-sdd-plan, mini-sdd-implement, mini-sdd-init-config, context.md, spec.yaml, plan.md, ARTIFACT_MAIN_FOLDER, SPECS_SUBFOLDER, hooks config, or spec-driven development. Do not use for creating context files, writing specs, planning, or implementing features — those have their own skills.
Use this when you need to run a shell command on a connected tray follower —
specifically a `slicc … follow <runner>` CLI follower that lent its machine as
an exec target. Covers discovering targets (`host`, `ssh --list`), running
commands (`ssh <runtime-id> <command>`), what a runner is, timeouts and Ctrl+C,
and the important trust boundary: the command runs on the follower's real
machine, as the user who started it, OUTSIDE this leader's sudo policy.
107 production-grade QA engineering skills covering frontend, API, performance, mobile, security, CI, and AI/LLM testing. Use when writing or reviewing Playwright, pytest, Jest, k6, Cypress, Newman, or JUnit tests, auditing test coverage, designing test data strategies, or building quality gates in CI pipelines.
Review and critique existing designs, websites, or frontend code against design principles. Checks for common anti-patterns like generic fonts, poor contrast, inconsistent spacing, and lack of visual hierarchy. Use when the user asks to "review my design", "what's wrong with this layout", "critique my website", "how can I improve the design", "audit the UI", "check my frontend", "make it look more professional", or "why does this look off". Produces actionable feedback with specific fix suggestions referencing other skills.
Use when you have LC-MS peak/feature data, a curated suspect compound database with known m/z, retention time, and fragment ion coordinates, and you observe that traditional peak extraction algorithms have failed to detect ions corresponding to suspected contaminants or chemicals of interest.
Read a research finding or plan document and build it, placing generic/reusable capability in dskit and project-specific logic in the child. Use when the user asks to implement, build, or act on a research finding or plan.
View plans dashboard with progress tracking and timeline visualization. Use for kanban boards, plan status overview, phase progress, milestone tracking, project visibility.
Fix a neovim or dotfiles configuration issue. Adds a task to ~/github.com/josefaidt/dotfiles/notes.md and implements the fix. Use when you notice a neovim issue and want to fix it in your dotfiles.
Eng manager-mode plan review. Lock in the execution plan — architecture,
data flow, diagrams, edge cases, test coverage, performance. Walks through
issues interactively with opinionated recommendations. Use when asked to
"review the architecture", "engineering review", or "lock in the plan".
Proactively suggest when the user has a plan or design doc and is about to
start coding — to catch architecture issues before implementation.
Macroeconomic modeling, calibration, and comparative statics. Use when working with DSGE models, growth models, general equilibrium, CES production, welfare analysis, or policy counterfactuals.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Patterns for continuous autonomous agent loops with quality gates, evals, and recovery controls. Use when running an agent loop that must self-check, gate on evals, and recover from failures.
Audit an existing Coval evaluation setup for coverage, misleading scores, missing evidence, judge validation and execution risk. Read-only; use when inheriting an eval or deciding whether its results support a release decision.