Besser dev

Skill BESSER-PEARL/BESSER-Skills/skills/besser-dev

Agent Skills for BESSER — deep BESSER knowledge for AI coding agents: UML class modeling, code generators, troubleshooting, and contributor workflows.

Install

npx -y skills add BESSER-PEARL/BESSER-Skills --skill besser-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Contributor guide for developing BESSER itself (https://github.com/BESSER-PEARL/BESSER). Use this skill whenever the user is working *inside* the BESSER source tree — adding a new generator (the most common contribution), adding a new metamodel or sub-DSL under `besser/BUML/metamodel/`, writing pytest tests for generators or metamodels, writing JSON↔BUML converters for the web editor, building Sphinx documentation under `docs/source/`, registering a generator in `SUPPORTED_GENERATORS`, or preparing a pull request to BESSER. Trigger on phrases like "add a new generator", "register in the web editor", "GeneratorInterface", "json_to_buml", "buml_to_json", "write tests for my generator", "build the docs", "open a PR to BESSER", or any work that touches `besser/generators/`, `besser/BUML/metamodel/`, `besser/utilities/web_modeling_editor/`, or `tests/`. Prefer this skill over besser-user when the user is contributing *to* BESSER rather than *using* BESSER to build something else.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, as published. Nobody here has run it

Contributing to BESSER

This skill covers the procedural workflows for contributing to the BESSER codebase. For architecture details and code conventions, also consult the BESSER repo's CLAUDE.md (auto-loaded in Claude Code; with other agents, read CLAUDE.md at the repo root directly).

Development Setup

git clone https://github.com/<your-username>/BESSER.git
cd BESSER
python -m venv venv
# Windows: venv\Scripts\activate
# macOS/Linux: source venv/bin/activate
pip install -r requirements.txt
pip install -r docs/requirements.txt  # for building docs
pip install -e .                       # editable install

Verify: python tests/BUML/metamodel/structural/library/library.py

Python 3.11+ is required (enforced by python_requires = >=3.11 in setup.cfg; CI tests 3.11 and 3.12).

Reference layout

This skill keeps SKILL.md short. Reach into references/ for the procedure you need:

Task	Read
Add a new generator (the most common contribution) — 6 steps + scaffold	`references/adding-a-generator.md`
Add a new metamodel / sub-DSL, plus JSON↔BUML converters	`references/adding-a-metamodel.md`
Write pytest tests (fixtures, `tmp_path`, what to assert)	`references/testing.md`
Build the Sphinx docs and cross-reference them	`references/docs-and-build.md`
Code style, commit/PR conventions, cross-repo, CI/release	`references/contributing-workflow.md`

Related skills for the using side (not contributing):

Running or customizing an existing generator → the besser-generators skill.
Diagnosing install/import/generation errors → the besser-troubleshooting skill.
The user-facing shape of a model type (doc templates) → the besser-user skill's references/.

Common Contribution Pitfalls

Don't duplicate logic — shared helpers go in besser/utilities/, not in individual generators.
Maintain determinism — generators must produce identical output for identical input.
Keep converters symmetric — if JSON → BUML supports a feature, BUML → JSON must too.
Update docs — any backend change likely needs docs/source/ updates.
Don't touch the frontend submodule unless explicitly required. UI changes go to the upstream WME repo.
Clean up resources — always use try/finally for temp directories and file handles.
Test round-trips — especially for converters (JSON → BUML → JSON should be identity).