kjanat.dev valid
@kjanat/dreamcli
Fully typed TypeScript CLIs with a lean install. Define once, infer everywhere.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:55:22.290Z. Cached copy · Source on kjanat.dev
# @kjanat/dreamcli
> Fully typed TypeScript CLIs with a lean install. Define once, infer everywhere.
Every documentation page is available as authored markdown under `/raw/`
(or send `Accept: text/markdown` to any page URL).
## Guide
- [Arguments](https://dreamcli.kjanat.dev/raw/guide/arguments): Positional arguments are declared with arg and appear after the command name.
- [Commands](https://dreamcli.kjanat.dev/raw/guide/commands): Commands are the primary building block in dreamcli.
- [Shell Completions](https://dreamcli.kjanat.dev/raw/guide/completions): dreamcli generates completion scripts from the command schema —
- [Config Files](https://dreamcli.kjanat.dev/raw/guide/config): dreamcli discovers and loads configuration files from standard locations.
- [Errors](https://dreamcli.kjanat.dev/raw/guide/errors): dreamcli provides structured errors with codes, suggestions, and JSON serialization.
- [Flags](https://dreamcli.kjanat.dev/raw/guide/flags): Flags are the richest primitive in dreamcli.
- [Getting Started](https://dreamcli.kjanat.dev/raw/guide/getting-started): npm install @kjanat/dreamcli
- [Help](https://dreamcli.kjanat.dev/raw/guide/help): Help text is generated from your schemas — usage line, arguments, flags,
- [Limitations And Workarounds](https://dreamcli.kjanat.dev/raw/guide/limitations): This page consolidates the most important current edges in DreamCLI's shipped surface.
- [Middleware](https://dreamcli.kjanat.dev/raw/guide/middleware): Middleware wraps downstream execution and can add typed context to the command handler chain.
- [Migration And Adoption](https://dreamcli.kjanat.dev/raw/guide/migration): This page is for serious evaluators and adopters deciding whether to move an existing CLI onto
- [Output](https://dreamcli.kjanat.dev/raw/guide/output): Handlers receive out instead of console.
- [Interactive Prompts](https://dreamcli.kjanat.dev/raw/guide/prompts): dreamcli integrates interactive prompts into the flag resolution chain.
- [Architecture Rationale](https://dreamcli.kjanat.dev/raw/guide/rationale): This page explains why dreamcli is shaped the way it is.
- [Standalone Flag Evaluation](https://dreamcli.kjanat.dev/raw/guide/read-flags): readFlags() takes a record of flag builders, evaluates it, and returns the
- [Runtime Support](https://dreamcli.kjanat.dev/raw/guide/runtime): dreamcli runs on Node.js, Bun, and Deno without code changes.
- [Schema Export](https://dreamcli.kjanat.dev/raw/guide/schema-export): dreamcli can export the complete CLI schema as JSON — for tooling,
- [CLI Semantics](https://dreamcli.kjanat.dev/raw/guide/semantics): This page is the canonical source of truth for dreamcli's edge-case behavior.
- [Testing](https://dreamcli.kjanat.dev/raw/guide/testing): dreamcli's test harness runs commands in-process with full control over inputs and outputs.
- [Troubleshooting](https://dreamcli.kjanat.dev/raw/guide/troubleshooting): This page covers the most likely real failure modes when building or eval
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| taskfile.dev | Task | documentation Developer tools Documentation and reference | DE | 60 | ✓ | ✓ | |
| optique.dev | Optique: type-safe combinatorial CLI parser for TypeScript | documentation Developer tools APIs and SDKs | US | 48 | ✓ | ✓ | |
| deno.com | Deno | documentation Developer tools | US | 66 | ✓ | ✓ | |
| llm-exe.com | llm-exe | documentation AI and machine learning Developer tools +1 | — | 50 | ✓ | ✓ | |
| geminicli.com | Gemini CLI Documentation | documentation AI and machine learning Developer tools | US | 57 | ✓ | ||
| gunshi.dev | Gunshi | documentation | — | 45 | ✓ | ✓ | |
| jdx.dev | mise-en-place | documentation Developer tools | — | 59 | ✓ | ||
| dotenvx.com | run every day at 8am | documentation Developer tools | — | 56 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=kjanat.dev · GET /v1/domain/kjanat.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.
Own or manage this website?
If you own or manage kjanat.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for kjanat.dev:
1. POST https://agentwebmap.com/v1/sites/kjanat.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kjanat.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/kjanat.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/kjanat.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.