Explore skills

Audit any system for human usability against Nielsen's 10 heuristics. Deterministic checklist — same 10 heuristics, same severity scale, same report structure every run. Works on UI screens, CLI flows, API response patterns, user journeys, component code, or any described interface. Invoke when user says "usability audit", "UX review", "heuristic evaluation", "audit for usability", "check this for

Trace the root cause of a bug or unexpected behaviour. Use when the user says "why is this broken", "why does this fail", "whybroken", "something's wrong with X", or pastes an error. Never patches symptoms — always finds the cause first.

Claude Code의 statusline HUD 플러그인. context 사용량, tool 활동, agent 추적, todo 진행상황을 실시간으로 표시한다. statusline 설정, HUD 커스터마이징, 또는 context 모니터링이 필요할 때 사용한다.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Scan the codebase for AI-generated slop in comments and docstrings — temporal markers, self-referential AI framing, narrative WHAT-comments, marketing padding — and propose tightened rewrites, routing claim-bearing docstrings that need a code-grounded rewrite to its sibling /techne:reslop. Use when the user wants to audit pending changes or the whole codebase for verbose, low-value commentary left

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.

Check a documentation file for drift against the actual codebase — CLI commands, file paths, config keys, function signatures, version numbers, environment variables — and propose corrections. Use when the user wants to audit README.md, docs/*.md, or similar for claims that no longer match reality. Drift usually comes from refactors that forgot to update the docs.

Audit a plan's design decisions — library, framework, pattern, and architecture choices in IMPL.md / ROADMAP.md — for missing `# research(YYYY-MM):` provenance, then web-search to ground them. Use when you want architectural choices verified against current best practice before they harden into code, rather than resting on training-cutoff recall. Catches committed decisions stated as fact but neve

Rewrite docstrings and comments by reading the actual implementation, call sites, and tests — produce grounded, factual prose instead of deleting slop. Sibling of /techne:deslop. Use when the user wants to replace overhyped or hallucinated documentation with accurate one- or two-line descriptions derived from what the code actually does.

Cross-repo drift audit across linked repos listed in `~/.claude/techne.toml` (configurable per-user). Read-only inspection of CI action pins, toolchain pins in pyproject.toml, skill-context structural parity, GitHub merge settings, open PRs, and branch hygiene. Triggers on phrases like "audit the sisters", "are the sisters in sync", "check cross-repo drift", or when multiple sister repos are menti

Run an observed live dev session — Claude drives an interactive REPL in a named tmux session, the human spectates read-only via `tmux attach -r`. Use when the user wants to play through, debug, or explore a service's REPL together. Trigger phrases include "let's do a live smoke", "run a theoros session", "I want to spectate while you drive the CLI", "start an observed dev run". Reads per-repo fact

Review the current project state and continuously guide the project toward better Harness and Compound Engineering practices. Identify: - behaviors that align with best practices - anti-patterns or weak workflows - missing operational discipline, evals, harnesses, or feedback loops Then recommend the next highest-leverage step, including: - what to do next - why it matters now - what commands, too