Chukke documentation

Model-ready

Use Chukke’s deterministic local analysis to review and prepare prompts and documentation.

Model-ready is Chukke’s local preparation workflow. It uses deterministic checks and does not call a model provider or send the document to one.

What the score means

Model-ready provides an advisory score from 0 to 100 across structure, clarity, completeness, and efficiency. Findings can cover Markdown cleanup, headings and lists, US and UK spelling, readability, placeholders, duplicate content, and token budgets.

For documents classified as prompts, additional checks can cover Goal, Constraints, Output, Validation, contradictions, and JSON contracts.

The score does not measure factual correctness and never blocks Apply, Copy, or optional provider assistance.

Prompt or documentation

Chukke classifies the active file locally. Explicit frontmatter is checked first, followed by known documentation filenames, prompt-directory paths, and strong content signals. Uncertain files default to Documentation.

Use frontmatter to override the local classification:

---
type: prompt
---

Use type: documentation for an explicit documentation override.

Review a document

  1. Open Model-ready for the active document.
  2. Review the score, detected type, dimensions, and findings.
  3. Inspect the eligible deterministic edits selected by default. Semantic additions and rewrites require an explicit choice.
  4. Compare the line-numbered Source and Prepared views, or use Diff to isolate selected changes.
  5. Choose Apply selected to place the prepared candidate into the open tab as an unsaved edit, or Copy prepared without changing the source.

The source file does not change until you apply and then save the edit.

When the document changes

Normal editing marks the current analysis as out of date. Refresh Model-ready before applying, copying, or passing the prepared candidate to optional provider assistance.

Optional intent improvement

The Improve intent action appears only when Assist is enabled. It is a separate model-provider request and uses the same exact-payload confirmation and diff-review safeguards as other Assist requests.