citum-core

High-throughput migration waves converting priority parent CSL 1.0 styles to Citum with repeatable before/after metrics and migration-engine gap recommendations. Fidelity is the hard gate.

Standardized QA gate for style work. Verifies fidelity, SQI drift, formatting defects, and regression surface. Produces approve/reject verdict with numbered findings.

Iterative LLM hand-tuning loop for embedded-core styles. Drives a style to 100% fidelity and clean SQI. Both are hard gates. Seeded from migrate evidence, not from the converter output as a terminal deliverable.

Autonomous research loop for Citum migration fidelity gaps and converter-focused Rust fixes.

Single human-facing command for all Citum style work. Use whenever someone asks to fix, improve, convert, create, or tune a citation style. Routes to upgrade, migrate, create, or tune. Always use this rather than calling internal skills directly.

Public entrypoint for Citum style work. Activate on: 'upgrade', 'migrate', 'create', 'tune', any style authoring request, or any request to fix/improve/convert a Citum or CSL citation style. Route to the shared workflow docs and internal roles.

Repo-owned test soundness auditor and navigator for citum-core. Reasons from a spec (not the implementation) to classify each test as good, suspicious, broken, or redundant; simultaneously reviews the spec for ambiguity, contradiction, and silence, halting to prompt the user when a spec defect blocks an honest verdict. Records state in the living ledger docs/architecture/TEST_SOUNDNESS_STATUS.md — never ephemeral JSON. Trigger on: "/test-soundness-review", "review my tests against the spec", "audit test soundness", "are my tests vacuous", "find broken tests", "find redundant tests", "are these tests just for the sake of it", "test quality review", "review the spec while you're at it", "what's the state of our test quality", "what test audits are outstanding", "what's next for test soundness". Also trigger proactively after a disambiguation, sorting, algorithm, or engine feature is implemented when the user asks "do the tests actually cover the spec?". Takes up to two arguments: /test-soundness-review [spec-pa

Domain knowledge for test coverage in citum-core. Use this skill whenever you're implementing a feature, fixing a bug, writing tests, or claiming something is "tested" in citum-core. Trigger on any task involving: adding fixture data, writing Rust tests, running the oracle, validating style behavior, or checking whether a code path is exercised. This skill tells you what reference shapes are required to test each behavior, and provides a pre/post checklist so nothing slips through.

One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cleanup.

Legacy alias for style-evolve. Use it only when older docs or workflows still reference the original name.

Fast, consistent branch/PR workflow with explicit change-type quality gates and concise evidence-first PR descriptions.

Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.

Task tracking and issue management for this Citum project using the `beans` CLI. Always use this skill — never TodoWrite — when the user mentions tasks, todos, work items, what to work on next, creating/updating/closing issues, or asks about project status. Trigger on: "what should I work on", "what's next", "create a task for", "mark that done", "I finished", "close this", "what's in progress", "next task", "check my tasks", "/beans next", "track this", "log a bug", "what's blocking me", "mark it complete", "I'm done with". Also trigger at the start of any multi-step task to check for an existing bean before creating one.

Autonomous research loop that improves citum-migrate converter fidelity by iterating on Rust code in crates/citum_migrate/src/. Measures fidelity across a corpus of priority styles, clusters failure patterns, attempts targeted Rust fixes, validates with cargo nextest, keeps improvements, reverts failures. Does NOT modify style YAML.

Fast targeted maintenance for an existing Citum style. Use for punctuation/layout bugs, missing type-variants entries, or syntax modernization. Not for migrations or batch waves.

Expand or maintain the engine behavior coverage report in citum-core. Use this skill when converting additional citum-engine integration suites into behavior-oriented tests, adding them to the nextest-backed Markdown/HTML report, refining behavior summaries, or updating the published docs report without increasing PR CI time.

Expand or maintain the migration behavior coverage report in citum-core. Use this skill when converting reviewer-facing citum-migrate suites into behavior-oriented tests, adding them to the nextest-backed Markdown/HTML report, refining behavior summaries, or updating the published docs report without increasing PR CI time.

Documentation standards workflow for Citum specs, policies, architecture snapshots, guides, and references. Use this skill when creating or updating project documentation and choosing the correct docs directory/template.

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.