Use when going beyond basic linting to enforce advanced Python code quality gates. Triggers on: cognitive complexity, code duplication detection, architectural enforcement, import boundaries, dependency hygiene, test quality beyond coverage, mutation testing,…
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps, or screenshots. Also use when Sam says "write a blog post about [project]" or "turn this into a post".
Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when…
Automatically triggered when running security scans, auditing code for vulnerabilities, checking dependencies for CVEs, reviewing code for security issues, or hardening Python applications. Applies when discussing: security audit, vulnerability scan, bandit,…
Use when the user asks to check if a band is sketch, fascist, NSBM, or far-right. Also trigger for: "is [band] sketch?", "is [band] safe?", "sketch check [band]", "check [band] for fascist ties", "is [band] NSBM?", "is [band] fash?", "should I listen to…
Apply Sam Dumont's personal writing voice and style when drafting reports, blog posts, technical documentation, client communications, Slack messages, LinkedIn posts, or any written content. Use this skill whenever Sam asks to write, draft, review, or improve…
Use when starting significant features, evaluating build-vs-buy decisions, reframing failed approaches, or when the user mentions "outcome engineering", "o16g", "outcome-first", "what's the outcome", or "frame this as an outcome". Also use proactively when a…
Automatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing codebases for consistency. Applies when discussing: system design, technology choices,…