jhutchison0
Userdoctrine as code
Categories
Indexed Skills (7)
designing-clear-data-displays
House figure style distilled from Edward Tufte's books and course. Eight kernel rules with tests, before/after pairs, and a review protocol for every chart, figure, map, table, or data-bearing layout. Use when drawing or reviewing any data display.
maintaining-project-context
Maintain CONTEXT.md at the repo root capturing the project's identity, mission, current state, and key constraints. Use at the start of significant new work, when the project mission or scope changes, when an agent needs to understand the project quickly, or when the project's relationship with downstream consumers changes.
maintaining-ubiquitous-language
Maintain a project-specific glossary of domain terms in LANGUAGE.md at the repo root. Use when a new domain term emerges in conversation, when reviewing code that uses inconsistent terminology, when onboarding a new contributor or agent, or when an existing definition becomes stale.
shift-left-testing
Multi-tier testing strategy with vertical-slicing (tracer-bullet) TDD, mocks, fixtures, simulation, property-based invariants, numeric tolerances, legacy characterization, script/CLI testing, CI integration, and explicit anti-patterns. Use when setting up test infrastructure, designing test strategy, implementing mocks, or driving feature work via test-first one-cycle-at-a-time TDD.
using-topic-branches
Branch by work shape, not by domain. Lead-only doc/ADR/small-refactor work lands directly on main; team-deployed or multi-agent code work with an audit gate uses a short-lived topic branch that is merged and then deleted (local + origin) immediately. Use when starting a unit of work, deciding whether to branch, merging at a gate, or auditing standing branches across a repo.
writing-simple-and-direct
House prose style distilled from Barzun's Simple and Direct. Eight kernel rules with expansions, before/after patterns, and a review protocol for every prose artifact (SITREPs, reviews, proposals, ADRs, session docs, backbriefs, commit messages). Use when writing or reviewing any prose artifact.
traversing-the-knowledge-base
Traverse this repo's knowledge base by its existing link graph (typed session-doc headers, markdown links, path mentions) instead of blind keyword search. Use when tracing why an artifact exists, assessing blast radius before editing a living doc, orienting on session lineage, or checking reference integrity.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.