메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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
| name | style-evolve |
| description | 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. |
Use this skill for any Citum style request that should be handled through the shared style workflow.
Read first:
docs/policies/STYLE_WORKFLOW_DECISION_RULES.mddocs/guides/STYLE_WORKFLOW_EXECUTION.mddocs/guides/AGENT_SKILLS.mddocs/guides/JJ_AI_CHANGE_STACK.md when .jj is present and local stack
curation would help isolate the workupgrade: improve an existing Citum style.migrate: convert CSL 1.0 source into Citum style YAML.create: author a new Citum style from source evidence.tune: drive an embedded-core style to 100% fidelity + clean SQI via
iterative LLM authoring, seeded by migrate evidence. Both fidelity and SQI
are hard gates for this mode. Loop defined in docs/guides/STYLE_WORKFLOW_EXECUTION.md.spec-planner when the request needs architecture or schema decisions.migration-researcher when the evidence points to citum_migrate.rust-implementer for bounded Rust fixes.style-qa-reviewer for the final style QA gate.docs/policies/STYLE_WORKFLOW_DECISION_RULES.md for the tier definition
and quality bar.tune rather than treating migrate output as final.docs/specs/STYLE_TAXONOMY.md and the shared workflow docs.create pass for a hidden family root
followed by upgrade reduction of the public handles.When you encounter a routing case, semantic class, or implementation form not covered by the existing operating rules or the shared workflow docs, record the pattern here as a new bullet under "Operating Rules" and include the file update in the same commit. The goal is that each time style-evolve handles an edge case it couldn't resolve cleanly, that edge case becomes a covered case going forward.