Agent skills

An agent skill turns Nexma into a domain-aware platform. Load the FTTH skill and Nexma becomes a fiber-network planner. Load the water skill and the same product becomes a water-utility designer. The toolbar, the layers, the chat, the validations — all reconfigure for the active domain.

Why skills exist

Most spatial products are vertical applications: one tool for fiber, another for water, another for substations. Each ships a different UI, a different data model, a different domain-aware AI. They don’t share anything. If your team works across domains, you’re stuck assembling a stack of disconnected tools.

Nexma is horizontal. The same engine runs every domain; the skill is what makes it domain-aware. That changes the economics: a new vertical is a configuration, not a new product.

What a skill gives you

When you load a skill, your project immediately gets:

• Domain-correct entities and rules. Cabinets, splitters, drops, splices for FTTH;

pumps, pipes, reservoirs for water. Each with the right properties and validations.

• Standards-aware constants. Industry color codes, standard catalogs, regulatory

defaults — already wired in.

• A toolbar shaped to the domain. Tools that make sense for fiber don’t clutter

a water project, and vice versa.

• Map styling that reads correctly. Cabinets render as cabinets, pipes as pipes —

not as generic points and lines.

• AI that knows the rules. Jax respects the skill’s constraints automatically.

You don’t restate them in every prompt.

Working with skills

Most teams start by loading a built-in skill (FTTH, water, electric, gas, 5G, logistics, construction). From there:

• Use it as-is for the standard domain.
• Extend it when your domain has a wrinkle the default doesn’t cover —

“add a splice-type field to closures.” Every view reacts.

• Compose two skills for hybrid projects (a municipal project with both fiber and

street lighting).

If your domain isn’t in the catalog, you can describe it in natural language and Jax will draft a skill. You review, edit, and save.

Why this is the central abstraction

Spatial work is fundamentally about what kind of thing exists and what rules govern it. Skills make that explicit and editable. The platform stays simple; the domain expertise lives where it belongs — at the edge, near the people who actually know the domain.