101 skills · sorted by relevance
Clarify a project's business concepts and terminology through concrete scenarios and comparisons with code. Record agreed definitions in a glossary and document significant design trade-offs in ADRs, records explaining why a decision was made.
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.
Ask an agent to restate an unclear message with more background, using the conversation's language and the project's glossary. It applies simplified technical writing guidance to help explain how the discussion reached its current point.
Ask the agent to explain its last message again with some context. The revised explanation uses ASD-STE100, a simplified technical English standard, and the vocabulary defined in the project's glossary.
Sets up shared project rules and a glossary so people and AI agents work from the same context. It preserves existing documents, introduces additional records when needed, and provides a check mode to audit inconsistencies.
Translate English skill documentation into Simplified Chinese while preserving commands, code, paths, and identifiers. Follow a shared glossary, refresh changed content, and review document structure and public indexes to keep the localized edition consistent.
Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.
Update Chatbox Pro interface translations by reviewing code changes and the surrounding screen context. The skill identifies affected translation keys, follows a shared glossary, and edits language JSON files while preserving placeholders and formatting tags.
Turn talk scripts, slides, and concept notes into reference sheets with section navigation, definitions, shareable links, a glossary, and six to ten anticipated questions with short answers for live Q&A and attendee follow-up.
Use when building reusable Obsidian glossary notes from an existing paper source manifest, optionally with a raw-sections override, especially when a reader needs a reviewed shortlist before glossary notes and article links are changed.
The English summary is being prepared. Showing the original description.
Deprecated compatibility entry for Glossary Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Glossary Page.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", "map", "travel times", "routes", "calendar", "moons", "seasons", "naming language", "conlang names", "trade routes", "supply lines", "magic cost", "add a glossary term", "glossary", "invented word", or wants to develop any aspect of a story's world and setting. NOT for a glossary for translators (use adaptation).
The English summary is being prepared. Showing the original description.
Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.
The English summary is being prepared. Showing the original description.
Draft a pull request description from existing project records and verification results. Present the change with a compact visual, before-and-after evidence, rollback details, and its wider impact so reviewers can assess the work.
Turn a plain description of a web animation into the matching term from a curated glossary. Get a short definition and distinctions between similar effects so you can describe the motion to an AI or designer.
Refine a plan or design through an ongoing interview while creating documentation. The skill combines grilling and domain-modeling to produce architectural decision records, which capture design decisions, and a glossary of relevant terms.
Doctrine for drafting and keeping working-group docs under `docs/wg/**` — RFC/RFD specs and findings/research/glossary. A WG doc is a language-agnostic, code-agnostic study of a domain: it argues *why* and defines *what*, never *how in our code*. Use when writing or editing anything under `docs/wg/`, an RFC/RFD, a spec, a design note, a glossary, or research findings — including "write up the design", "document the spec", or "capture what we learned". Not for plans/TODOs (untracked `*.plan.md`), user docs, or SDK API refs — use `docs` to route those.
The English summary is being prepared. Showing the original description.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
The English summary is being prepared. Showing the original description.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
The English summary is being prepared. Showing the original description.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
The English summary is being prepared. Showing the original description.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
The English summary is being prepared. Showing the original description.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
The English summary is being prepared. Showing the original description.
Use this skill when a set of policies, procedures, plans and registers has grown in pieces and someone asks "check our documents for contradictions", "are our policies consistent", "the retention periods don't match", "which severity scale is right", "harmonise our ISMS documents", "cross-check the incident plan against the policy" or "clean up our documentation before the audit". Extracts the checkable facts from every document (periods, deadlines, scales, roles, labels, references), finds contradictions, naming drift and broken references, proposes which document owns each fact, and drafts a glossary and a fix list for the owners.
The English summary is being prepared. Showing the original description.
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
The English summary is being prepared. Showing the original description.