Developer Tools

The developer tools are what you use to build, verify and ship on kis.ai. They are independent of the runtime blocks — you can adopt any of them without adopting the others.

The tools

Tool	What it does
Code Quality	Runs static-analysis and security scanners across your source, normalises findings, tracks quality over time
Testing	Declarative API and load testing, with assertions, data-driven cases and scripting
Automate	Distributed CI/CD — integrate, test, deploy
Spec	The YAML schema system — 128 kinds, validation, linting, scaffolding and generation
IDE	Language server for kis.ai YAML: validation, autocomplete, hover docs, go-to-definition

How they fit a workflow

   author YAML  ──▶  IDE validates as you type
        │
        ▼
   commit       ──▶  Automate runs the pipeline
                          │
                          ├──▶ Testing      does it behave correctly?
                          └──▶ Code Quality is it safe and maintainable?
                                    │
                                    ▼
                              gate the deploy

The two verification tools answer different questions and neither substitutes for the other. Testing tells you the system does what you asked. Code Quality tells you the source is free of known vulnerability classes and is not accumulating debt. A change can pass one and fail the other, which is the point of running both.

Where to start

Adding a new service? Start with Testing — declarative test definitions are cheaper to write early than to retrofit.

Inheriting a codebase? Start with Code Quality. One scan gives you a baseline and a trend line, which is more useful than an opinion about the state of the code.

Writing platform YAML? Spec is the schema system behind all of it, and the IDE language server puts the same validation in your editor. Catching a schema error while typing is worth more than catching it in CI.