Explore skills

Set up a build/test/lint validation loop for the current project. Detects the tech stack and configures CLAUDE.md with verification commands.

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.

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

Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error h

Use this skill when naming or renaming a GitHub repository, product, CLI, plugin, skill pack, framework, app, or public developer project. It reverse-engineers association-based open-source naming patterns and produces product name, repo slug, tagline, About description, topics, rejected names, and README hero copy.

Rewrite GitHub repository names, About descriptions, README intros, and website tool cards so they communicate practical user value.

Creates CLAUDE.md/AGENTS.md from the harness template (if absent) and configures docs/agents/ so harness skills know the issue tracker, triage labels, domain docs, GitHub Project board, and session state location. Run before first use of triage, to-prd, to-issues, context-handover, or session-start — or if those skills appear to be missing context. Typically consumes <30% of a context window.

Use when Claude Code needs to explain a SpecDD spec, target, behavior, or effective spec chain without editing it.

Use when Claude Code needs to get oriented in a SpecDD project before later work, while making no edits.

Review a pull request or diff and return ornate, Early Modern English comments — one per finding, each anchored to `file:line`. Use when the user types /shakespeare-review or asks for a "bard review". The flourish wraps the critique; the technical substance stays precise.

Ornate output mode. Answers the user in Early Modern English — thou/thee, -eth/-est endings, inverted syntax, rhetorical flourish. Deliberately inflates output tokens for comedic and aesthetic effect while keeping all technical substance intact. Supports intensity levels: lite, full (default), bard, sonnet, prose. Use when user says "shakespeare mode", "talk like shakespeare", "bard mode", or invo

[PM Twin] Your digital peer product manager — assess project state, fill gaps, recommend next action.