# API reference

The API pages are generated from the TSDoc on the package's actual public
entry points whenever the documentation site builds. Sourcey renders those
Markdown pages as part of this site; TypeDoc is an extraction step only, not a
second documentation renderer.

Browse the [complete generated module index](https://jonbogaty.com/lifecycle-kit/api/readme/index.md) or import a
focused subpath directly:

```ts
import * as chem from "lifecycle-kit/chem";
import * as bioLaws from "lifecycle-kit/bio-laws";
import * as forms from "lifecycle-kit/forms";
import * as pigment from "lifecycle-kit/pigment";
import * as assemblage from "lifecycle-kit/assemblage";
```

The root entry point exposes the same stages as namespaces so colliding names
stay explicit.

The generated pages are the authoritative source for symbol signatures, units,
and error behaviour. The guides explain how those symbols work together:

- [Render a creature](https://jonbogaty.com/lifecycle-kit/rendering/index.md) covers `Path`, SVG/Pixi helpers, and
  depth-sorted `AssembledPart` output.
- [Agentic consumers](https://jonbogaty.com/lifecycle-kit/agentic-consumers/index.md) gives automation a narrow,
  deterministic integration contract.