spotless: Instructions file for Codex

Spotless, root agent rules

Read this before changing anything. The conventions below are carried over from ~/code/v2 and adapted: that repo is a TypeScript monorepo, this is a Native SDK app, so the discipline transfers and the specifics do not. Copying v2's stack rules verbatim here would be the exact slop they exist to prevent.

Mission

Spotless files new downloads into subfolders, by extension and by where the file was downloaded from. It is a single-folder tool: it reads one directory, moves files within it, and never deletes anything.

The dependency arrows (enforced by the compiler, not a script)

src/shared.ts      ← core + services   (boundary records only; imports nothing)
src/bytes.ts       ← core              (byte primitives)
src/rules.ts       ← core              (the rule table + pure helpers)
src/editing.ts     ← core              (the text-field reducer)
src/core.ts        ← the views          (Model, Msg, update, derived bindings)
src/services/*.ts  ← NOBODY            (reached only through @native-sdk/services)

The core never imports a service, even import type. That is NS1065 and the checker stops the build. Services may import subset-legal declarations from the core class; every record that crosses the boundary is declared once in src/shared.ts and nowhere else.

update is pure and synchronous. It never touches the filesystem: it returns a Cmd and the runtime dispatches the result back as a Msg.

Naming

• .ts files kebab-case; .native view files named for their window label (src/windows/settings.native is the window whose label is settings).
• Model fields and Msg kinds keep their TypeScript spellings, because markup binds them verbatim. A rename is a two-file change.
• Msg kinds are snake_case verbs (toggle_rule, pick_folder); model fields are camelCase nouns.
• Derived state is a helper, never a field. If markup needs it, export a single-Model function.

Comments policy