Nexload SDK

Production TypeScript packages for service health and Payload CMS.

This repository currently documents and supports eleven released packages. Install only the package that owns your task. Package versions, peer dependencies, and runtime compatibility are listed in the documentation.

Packages

Healthcheck

Start with @nexload-sdk/healthcheck, then add the runtime, framework, CMS, or monitoring integration your service needs.

Package	Use it for
@nexload-sdk/healthcheck	Defining checks, collectors, scopes, health reports, timeouts, status aggregation, and serialization without coupling the core to a framework.
@nexload-sdk/healthcheck-node	Reading Node.js process data, Linux cgroup limits, TCP reachability, and DNS resolution.
@nexload-sdk/healthcheck-bun	Adapting the health manager to Bun and observing Bun.serve server metrics.
@nexload-sdk/healthcheck-next	Creating no-store health and metrics route handlers for the Next.js App Router.
@nexload-sdk/healthcheck-prometheus	Serializing health reports as Prometheus or OpenMetrics text.
@nexload-sdk/healthcheck-otel	Converting health reports into OpenTelemetry-friendly resource attributes and metric records without requiring an OpenTelemetry SDK.
@nexload-sdk/healthcheck-payload	Checking Payload CMS readiness through a small, controlled Local API query.

The runtime adapters do not create HTTP endpoints. Route ownership stays with your application or framework integration. Monitoring serializers only convert reports; they do not start exporters or register SDK providers.

Payload CMS

These packages solve separate problems and can be used independently.

Package	Use it for
@nexload-sdk/payload-fields	Adding managed Unicode slugs, Jalali date inputs, and integer minor-unit money fields to Payload collections.
@nexload-sdk/payload-editor	Building deterministic Payload Lexical editor configurations from explicit presets and feature options.
@nexload-sdk/payload-operations	Exposing typed custom Payload operations through shared Zod contracts, secure endpoints, and the native SDK.
@nexload-sdk/payload-schema	Defining canonical field validation and normalization once, then reusing it as Payload fields and Zod schemas.

payload-fields owns specific field behavior and Admin UI integrations. payload-editor owns Lexical configuration. payload-schema owns canonical data contracts shared by Payload and Zod. payload-operations owns custom operation transport, endpoint, access, and error boundaries; it does not replace Payload CRUD or the other packages.

Agent Skills (6+1 Cognitive Graph & Engineering Standards)

This repository distributes production-grade, progressively disclosed Agent Skills compliant with the Agent Skills Specification v1.0.

• The 6+1 Cognitive Graph (nexload-reasoning-*): Kernel router, depth controller, and 6 standalone-capable specialists (Discovery, Investigation, Ideation, Design, Evaluation, Execution) enforcing evidence-first reasoning and the Divergence Firewall.
• Engineering Standards (nexload-*): Core standards for TypeScript precision (nexload-code), package boundaries (nexload-package), React render safety (nexload-react), visual systems (nexload-design), pre-design context compilation (nexload-design-context), and principal architecture reviews (nexload-cto-review).
• Domain Specialists: Operational skills for Healthcheck reliability and Payload CMS enterprise development.

Install skills directly into any project using the official CLI:

# Install the Cognitive Reasoning Kernel
npx skills add gecut/nexload-sdk --skill nexload-reasoning

# View all available skills
npx skills add gecut/nexload-sdk --list

See the Agent Skills Documentation for the complete catalog and the One-Shot Project Adoption Prompt.

Documentation

The package catalog is the starting point for installation, quick starts, concepts, guides, API references, examples, troubleshooting, migration, and compatibility.

The site documents the current released version of each package. Historical versioned pages are not hosted; use the package changelog and migration guide when upgrading.

Repository development

The workspace uses pnpm and Turbo. Node.js 20 or newer and pnpm 10 are recommended for repository development.

pnpm install
pnpm build
pnpm lint

Package source lives under packages/. Build output is generated in dist/ and should not be edited directly. Releases are managed with Changesets.

See AGENTS.md for repository-specific contribution guidance.