Working with skills

Most teams start by loading a built-in agent skill, doing real work, then extending it as their domain reveals edge cases the default doesn’t cover.

Loading a built-in skill

When you create a project, pick a starting skill from the catalog (FTTH, water, electric, etc.). The skill becomes part of your project — your local copy, free to edit. Built-in updates don’t overwrite your changes unless you opt in.

Extending a skill

The most common change is adding a property or a constraint. The easiest way is to ask Jax:

Add a splice_type field to closures. Allowed values: mechanical, fusion, rotary. Default is fusion.

Jax makes the change, validates it, and tells you what migrated. Existing features get the default; new ones see the field as a required input. The toolbar, side panels, and validators all reflect the new field instantly.

Adding a constraint

Constraints are first-class. Add one and:

• The validator surfaces violations on the Globe (red outline, side-panel issue list).
• Jax respects it on the next run.
• You can ask “which assets violate the new rule?” and get a list.
• Reports include the constraint by name.

Add a constraint: any cabinet must be within 250 m of a road.

Composing skills

For projects that span domains (a municipal project with both fiber and street lighting), load both skills. Their entity types stay namespaced; shared concepts (a road, a building) collapse to a single layer used by both.

Drafting a new skill

If your domain isn’t in the catalog, describe it to Jax in natural language. Jax will draft entities, relationships, and constraints. You review the diff, edit, and save. Expect to iterate — the first draft is rarely the final.

Versioning

Skills are versioned per project. You can roll back, branch, or compare revisions.