Saturate
- 30 skills
- 0 followers
- 17 hours ago last updated
- ▌ Tdd · saturateGuides test-driven development with RED-GREEN-REFACTOR cycle, prove-it pattern for bugs, and consumer-driven interface testing. Prefers real implementations over mocks. Use when writing tests first, TDD, test driven development, red green refactor, prove a bug, writing tests, test first, or when asked to add tests before implementation.
- ▌ Plan · saturateBreak work into small verifiable tasks with acceptance criteria and dependency ordering. Produces tasks/plan.md.
- ▌ Push · saturateRuns project quality gates before pushing. Auto-detects lint, format, typecheck, test, and build commands from project config. Fixes auto-fixable issues and amends the last commit. Use when pushing, git push, pushing changes, push to remote, or before creating a PR.
- ▌ Ship · saturateRun parallel pre-launch review with code-reviewer, security-auditor, and test-engineer, then synthesize a go/no-go decision.
- ▌
- ▌ Commit · saturateCommits staged changes using Conventional Commits with auto-detected scope, work item linking, and secret scanning. Use when committing, making a commit, git commit, save changes, commit changes, commit my work, or when triggered by incremental-implementation.
- ▌ Debugging · saturateSystematic debugging workflow that follows evidence instead of guessing. Checks APM and monitoring first, gathers context through available tools, localizes to layer, and tracks what has been tried to prevent loops. Use when debugging, fixing a bug, something is broken, error investigation, troubleshooting, diagnosing issues, finding root cause, or when stuck on a problem.
- ▌ Knowledge · saturate bundleStores learnings in and recalls knowledge from the Obsidian vault. Use `/knowledge store` after a session where something worth keeping was learned, or `/knowledge recall <topic>` to check for existing notes before starting work. Triggers on save knowledge, remember this, what do I know about, check notes, recall, look up prior knowledge.
- ▌
- ▌ API Design · saturate bundleDesigns APIs with contract-first, consumer-driven approach including validation at boundaries, consistent error responses, and security focus. Generates types from OpenAPI/Swagger. Use when designing an API, creating endpoints, API architecture, REST design, building an API, defining contracts, new service, or when starting API work.
- ▌ No AI Slop · saturate bundleGuides prose writing to avoid AI-generated slop patterns. Applies structural variety, voice authenticity, and a multi-step self-review with worked examples.
- ▌ Code Review · saturatePerforms self-review during development by checking changed code for bugs, security issues, performance problems, and test gaps. Runs inline before committing or creating PRs. Use when reviewing own code, self-review, check my changes, review before commit, review my code, code review, quality check, or when triggered by incremental-implementation before a PR.
- ▌ Idea Refine · saturateSharpens vague ideas into actionable briefs by generating 3-5 options with tradeoffs, checking technical feasibility, and defining scope with a "Not Doing" list. Use when brainstorming, refining an idea, scoping a feature, exploring options, defining requirements, what should we build, unclear requirements, or when starting something new without a clear spec.
- ▌ Safe Delete · saturateSafely handles recursive file/directory deletion by classifying targets, backing up what can't be recovered, and verifying nothing is lost before committing the delete. Use when running rm -rf, rm -r, deleting directories, removing files recursively, cleaning up paths, delete folder, remove directory, or clean up.
- ▌ Code Metrics · saturate bundleRuns code metric tools (scc for LOC, lizard for cyclomatic complexity, jscpd for duplicate detection) to produce triage signals for audits, cleanup, and refactoring prioritization. Use when asked for code health metrics, complexity hotspots, duplicate code, LOC breakdown, technical debt signals, what to clean up first, pre-audit analysis, or to feed metric context into other skills like codebase-audit or simplify. Not a fix-it tool — it surfaces flags, not mandates.
- ▌ Pre Planning · saturate bundleGathers context from multiple sources before entering plan mode, including git remote work items, codebase structure, reference projects, and memories. Detects platform from git remote. Use when starting planning, before plan mode, gather context, prep for planning, kickoff, starting a new feature, beginning work on a task, or before implementing something non-trivial.
- ▌ Skill Router · saturateMeta-skill that maps tasks to the right skill. Consult at the start of any non-trivial task to pick the right workflow skill, and before specific actions (installing deps, committing, opening PRs, reviewing) to pick the right action skill. Loaded automatically at session start by the skill-router plugin.
- ▌ Norriq Writing · saturate bundleWriting guide for NORRIQ content. Kills AI tells, enforces plain language in Danish and English. Use for any customer-facing text, internal docs, PR descriptions, emails, or posts.
- ▌ Launch Checklist · saturateValidates full deployment readiness beyond code, checking infrastructure, Docker configuration, Kubernetes manifests, environment config, monitoring, security headers, and pipeline status. Use when launching, deploying to production, release readiness, go-live, deployment check, pre-launch, shipping to prod, or when preparing for production deployment.
- ▌ Documentation Adrs · saturateRecords architecture decisions to memory provider when significant technical choices are made. Lightweight format capturing what was decided, why, alternatives considered, and tradeoffs. Use when recording a decision, documenting architecture, ADR, architecture decision record, why did we choose, technical decision, or when a significant choice is made about dependencies, patterns, or infrastructure.
- ▌ Security Deep Dive · saturatePerforms red team security analysis with threat modeling, attack surface mapping, auth flow analysis, and dependency chain audits. Goes beyond checklists to think like an attacker. Use when doing security audit, penetration testing, threat modeling, security review, attack surface analysis, red team assessment, or when codebase-audit flags serious security concerns.
- ▌ Code Simplification · saturateSimplifies code safely using Chesterton's Fence principle - understanding why code exists before changing it. Makes one change at a time with verification after each. Use when simplifying code, reducing complexity, refactoring, cleaning up, making code simpler, untangling, or when code feels unnecessarily complex.
- ▌ Performance Profiling · saturateGuides active performance investigation with measure-identify-fix-measure cycle for both frontend and backend. Triggers chrome-devtools for frontend profiling. Use when profiling performance, investigating slow code, optimizing speed, performance issues, slow page, slow API, latency problems, or when something feels sluggish.
- ▌ Evaluating Dependencies · saturateEvaluates packages before installation across npm, pnpm, yarn, bun, cargo, pip, uv, go, and nuget. Checks footprint, maintenance status, alternatives, license, and security. Use when adding dependencies, choosing between libraries, optimizing bundle size, or running npm install, pnpm add, yarn add, bun add, cargo add, pip install, uv add, go get, or dotnet add package.
- ▌ Frontend UI Engineering · saturateGuides frontend UI development with component hierarchy, separation of concerns, accessibility as requirement, and performance awareness. Framework-agnostic, detects stack from project. Triggers chrome-devtools for verification. Use when building UI, frontend development, creating components, UI engineering, component architecture, building pages, or when working on frontend code.
- ▌ Doubt Driven Development · saturateSubjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
- ▌ Incremental Implementation · saturateBuilds features in vertical slices where each slice is implemented, tested, verified, and committed before moving to the next. Triggers code-review before creating PRs and make-pr when complete. Use when implementing a feature, building incrementally, vertical slices, step by step implementation, building a feature, or when starting to code a planned feature.
- ▌ Stats · saturateQuery Claude Code usage stats from observability logs. Shows costs, session summaries, tool usage, token consumption, and more. Use when asked about costs, usage, stats, spending, session history, most-used tools, or token usage. Invoked with /stats or when asking questions like "how much have I spent today?"
- ▌ Make Pr · saturate bundleCreates pull requests on GitHub or Azure DevOps by analyzing commits and generating descriptions. Detects platform from git remote and uses gh CLI or az CLI. Use when asked to create PR, open PR, make pull request, submit PR, create pull request, new PR, raise PR, push PR, open pull request, submit changes, PR workflow, or when user mentions PR creation. Generates casual, context-aware PR descriptions that explain WHY not WHAT.
- ▌ Codebase Audit · saturate bundlePerforms comprehensive codebase audit checking architecture, tech debt, security vulnerabilities, test coverage, documentation, dependencies, and maintainability. Use when auditing a project, assessing codebase health, running security scans, checking for vulnerabilities, reviewing code quality, analyzing tech debt, or asked to audit/analyze the entire codebase.