Loading...
Loading...
Found 5 Skills
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Translate text between languages while preserving meaning and context
Create or update glossary entries in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires a glossary artifact. This skill is mandatory for AsciiDoc glossaries unless the user explicitly opts out for the current project or session.
Used to audit codebases to ensure their naming complies with established terminology and specifications. This Skill should be used when you need to enforce a project's 'Ubiquitous Language', identify deviations in method/variable/parameter naming, and propose modification suggestions.
Normalize terminology across a draft (canonical terms + synonym policy) without changing citations or meaning. **Trigger**: terminology, glossary, consistent terms, 术语统一, 统一叫法, 术语表. **Use when**: the draft has concept drift (same thing called 2–3 names) or global-review flags terminology inconsistency. **Skip if**: you are still changing the outline/taxonomy heavily (do that first). **Network**: none. **Guardrail**: do not add/remove citation keys; do not introduce new claims; avoid moving citations across subsections.