glossary
Skill896 starsChanged 31 days agoApache-2.0View on GitHub
Read when naming anything user-facing - GUI text, docs, public Python API names, arguments, docstrings, or error messages. Gives the approved LightlyStudio term for each concept and the wording to avoid, currently covering annotations, annotation classes, annotation sources, labeling, and ingestion.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use the Term for all user-facing parts: the GUI, the docs, and the public Python API (names, arguments, docstrings, and error messages).
- Very specific: line 14
Add new topics as their own ## section below.
- Very specific: line 34
Do not use "import" for data.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Glossary and Naming
Terminology for LightlyStudio.
Use the Term for all user-facing parts: the GUI, the docs, and the public Python API (names, arguments, docstrings, and error messages). Internal implementation names (database tables and columns, resolvers, REST JSON fields, and the generated frontend client) are exempt.
Add new topics as their own ## section below.
Annotations
| Concept | Term | Python identifier | Avoid |
| A classification, object-detection box, or segmentation mask attached to a sample | annotation | - | label, annotation label |
The category of an annotation, e.g. "dog", "cat" | annotation class | class_name | label, label class, annotation label |
| A group of annotations, e.g. ground truth, a model's predictions | annotation source | annotation_source | annotation collection, collection, collection name, label source |
| Creating annotations | labeling | - | the noun 'label' |
Data ingestion
| Concept | Term | Avoid |
| Images added without any annotations | raw images | image folder, unlabeled images |
| Videos added without any annotations | raw videos | video folder |
Adding samples to a dataset from any source, for example with add_images_from_path or add_samples_from_coco | ingestion (verb: ingest) | import |
Adding annotations to samples that are already in the dataset, for example with add_annotations_from_yolo | add annotations | import |
Do not use "import" for data. It reads like the Python import in nearby code blocks.
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- chattocorp/chatto★ 2.8ksame name
- genkovich/sdd★ 187same name
- intent-driven-dev/intent-driven-template★ 185same name
- aspi6246/Claude-Code-Skills-for-Academics★ 153same name
- tdimino/claude-code-minoan★ 41same name
- TakaGoto/rag-learning-academy★ 24same name
- Azure/azure-functions-agents-runtime★ 13same name
- intent-driven-dev/skills★ 9same name
- AcKeskin/contexture★ 2same name
- mkreindel/seo-toolkit-template★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- backend-guideSkill
- best-practicesSkill
- frontend-guideSkill
- pull-requestsSkill
- python-guideSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.