CLI docs should feel grown, not fabricated.

clily keeps validation, config, prompts, lifecycle hooks, help, and completion metadata close to the command you are writing.

Start softly See the surface

Breathable docs chrome

Schema-first ergonomics

Balanced light and dark

first command

import clily from '@clily/core'
import { z } from 'zod'

const run = clily({
  name: 'release',
  completion: true,
  subCommands: {
    deploy: clily.command({
      args: z.object({
        image: z.string(),
        region: z.string().default('us-east-1'),
      }),
      positionals: z.string(),
      run: ({ args, positionals }) => {
        console.log(args.image, args.region, positionals)
      },
    }),
  },
})

await run()

Forest floor rules

Deep greens hold structure. Orange and yellow only bloom where attention matters.

Soft glass, papery neutrals, and grain keep the interface warm instead of sterile.

One command tree.

Parsing, validation, config, prompts, help, and completion metadata stay in one ergonomic place.

One schema per command.

Nested commands stay local and readable without hauling generic ceremony through the full app.

Comfort under load.

The interface stays breathable in bright and dark rooms, with papery light mode and forest-dark depth.

Readable when tired.

Cormorant headings, Geist body text, and Monaspace-style code keep the docs soft without losing precision.

Documentation path

A calmer path into the command tree.

Start with the first command, skim the runtime model, then move into examples and the package surface when you need exact edges.

Browse the path Study the runtime

Breathability

Wide spacing, rounded containers, and low-noise contrast keep long reading comfortable.

Organic structure

Grain, softened gradients, and botanical accents keep the interface from feeling machine-flat.

Elegant ergonomics

Buttons, code blocks, and docs navigation stay tactile, clear, and easy to scan when tired.