Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evgeniiperov/ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md.
Passed 7 of 20 test cases with the skill, and 4 of 20 without it.
and 5 more in the full report
6 fixed2 passed either way12 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please inspect our discussion about the SaaS subscription and invoice lifecycle and formalize our business terminology. Create the `UBIQUITOUS_LANGUAGE.md` file in the project folder containing categorized tables of standard terms with 1-sentence definitions and bad aliases. Make sure to detail entity cardinality/relationships, write a quick multi-turn sample conversation between an engineer and a domain specialist using the key terms, and add a section calling out ambiguous words that were overloaded in our chat.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the section header '## Flagged ambiguities' | Missed | Passed |
| Limits each term definition in the table to a maximum of one sentence. | Passed | Passed |
| Formats dialogue turns using markdown blockquotes. | Passed | Passed |
The instructions your model reads when the skill loads.
Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.
UBIQUITOUS_LANGUAGE.md in the working directory using the format belowWrite a UBIQUITOUS_LANGUAGE.md file with this structure:
# Ubiquitous Language
## Order lifecycle
| Term | Definition | Aliases to avoid |
| ----------- | ------------------------------------------------------- | --------------------- |
| **Order** | A customer's request to purchase one or more items | Purchase, transaction |
| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |
## People
| Term | Definition | Aliases to avoid |
| ------------ | ------------------------------------------- | ---------------------- |
| **Customer** | A person or organization that places orders | Client, buyer, account |
| **User** | An authentication identity in the system | Login, account |
## Relationships
- An **Invoice** belongs to exactly one **Customer**
- An **Order** produces one or more **Invoices**
test cases passed, vs 4 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.