nucleusframework.dev valid

Nucleus

Nucleus is a Kotlin framework for building native cross-platform desktop apps on top of Compose Multiplatform. It combines a Gradle plugin, runtime libraries, and GitHub Actions to handle OS integration (30+ runtime modules), packaging (18 distribution formats), performance (GraalVM Native Image and JVM AOT cache), and native window decorations (Tao backend).

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:57:16.983Z. Cached copy · Source on nucleusframework.dev

# Nucleus

> Nucleus is a Kotlin framework for building native cross-platform desktop apps on top of Compose Multiplatform. It combines a Gradle plugin, runtime libraries, and GitHub Actions to handle OS integration (30+ runtime modules), packaging (18 distribution formats), performance (GraalVM Native Image and JVM AOT cache), and native window decorations (Tao backend).

- Docs: https://nucleusframework.dev/en/docs
- GitHub: https://github.com/NucleusFramework/Nucleus
- Gradle Plugin Portal: https://plugins.gradle.org/plugin/dev.nucleusframework
- Maven Central: https://central.sonatype.com/search?q=dev.nucleusframework
- License: Apache 2.0 / MIT

## Documentation
- [Welcome to Nucleus 2.5](https://nucleusframework.dev/en/docs): Nucleus is the production desktop layer for Compose Multiplatform — native OS integration and packaging for Kotlin teams.
- [Why Nucleus](https://nucleusframework.dev/en/docs/why-nucleus): What Nucleus adds on top of Compose Multiplatform for Kotlin teams shipping real desktop apps.

### Get started

  - [Install](https://nucleusframework.dev/en/docs/start/install): Add the Nucleus Gradle plugin to a Kotlin project to build for macOS, Linux, and Windows from a single build.
  - [Quickstart](https://nucleusframework.dev/en/docs/start/quickstart): Build and run your first Nucleus desktop app, then package it as a native installer.
  - [Project setup](https://nucleusframework.dev/en/docs/start/project-setup): Configure repositories, the Nucleus plugin, runtime modules, a JDK toolchain, and a multi-module Gradle layout.
  - [Configuration](https://nucleusframework.dev/en/docs/start/configuration): Configure the nucleus { } Gradle DSL — application metadata, packaging formats, per-OS options, GraalVM native image, AOT cache, deep links, file associations, and trusted CA injection.

### Concepts

  - [Architecture](https://nucleusframework.dev/en/docs/concepts/architecture): The four layers that make up a Nucleus application and how they fit together.
  - [Runtimes](https://nucleusframework.dev/en/docs/concepts/runtimes): Nucleus can run your packaged app as a GraalVM native image or on the JVM with an AOT cache, selected from the Gradle build.
  - [Backends](https://nucleusframework.dev/en/docs/concepts/backends): Nucleus draws every window through the Tao backend behind the DecoratedWindow API. The legacy AWT backend is deprecated.
  - [Modules](https://nucleusframework.dev/en/docs/concepts/modules): How Nucleus splits its runtime into independently versioned Gradle modules and how to add the ones you need.

### Tao backend

  - [The Tao backend](https://nucleusframework.dev/en/docs/tao): Tao is a Rust-native window backend that runs Compose Desktop without AWT and adds native Wayland, multi-touch, and pen input.
  - [DecoratedWindow on Tao](https://nucleusframework.dev/en/docs/tao/decorated-window): Open a Compose Desktop window on the Tao backend with a custom title bar slot and native window controls, without AWT.
  - [
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=nucleusframework.dev · GET /v1/domain/nucleusframework.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for nucleusframework.dev:
1. POST https://agentwebmap.com/v1/sites/nucleusframework.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://nucleusframework.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/nucleusframework.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nucleusframework.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.