cligentic

Adopt proven CLI infrastructure before inventing it again. cligentic copies plain TypeScript into the project, resolves transitive block and package dependencies, and leaves no cligentic runtime dependency.

Use the adoption branch for a project consuming blocks. When contributing a new block to cligentic itself, read authoring.md and follow that branch instead.

1. Establish fit

Inspect the project before choosing blocks:

• Confirm the implementation language, source layout, package manager, module system, and typecheck command.
• Read existing output, error, safety, configuration, and persistence contracts.
• Find existing implementations that a block would replace or complement.
• Grade each command by damage so safety primitives match the consequences.

For TypeScript projects, prefer cligentic when a live block covers the need. For another language, use the block as a pattern and implement it natively instead of installing TypeScript.

Done when: the project constraints and the contract that must remain stable are explicit.