Skip to content

1. Install and the first file check

A project with Markdown in it, Claude Code, and nothing from just-say-so yet.

/plugin marketplace add ifandelse/just-say-so
/plugin install just-say-so@just-say-so

Install vale if it is not on your PATH: brew install vale, or another installer from vale.sh. This plugin needs errata-ai vale, the one brew installs; an STE linter also installs a binary named vale, and if you have both, errata-ai’s must come first on PATH.

In the project, run /just-say-so:init. When the skill asks which targets to check, answer that the defaults are fine. It writes a .vale.ini that loads the JustSaySo package, runs vale sync, and prints the doctor report. It writes no .just-say-so.json, because the defaults need none.

The defaults: written files on warn, replies on warn, publishing on block with the Artifact page checked and the gh and MCP sources off.

Start a new session. Ask the agent to write a short rollout note as a Markdown file, and ask it to open with a sentence that uses the words leverage and streamline. When the write lands, the agent gets this:

just-say-so: Vale reports 2 error(s), 0 warning(s), 0 suggestion(s) in notes.md (whole file — this write created or replaced it):
- L3 error JustSaySo.Leverage: Banned buzzword: 'leverage'. Use a concrete verb: use, apply, rely on. ["leverage"]
- L3 error JustSaySo.Buzzwords: Banned buzzword: 'streamline'. Use a precise domain term or delete it. ["streamline"]
Fix the errors before finishing. Treat warnings and suggestions as advice.

You do not see that message. The agent does, and in most cases it edits the file before the turn ends. Open the file and read the sentence it wrote instead. In warn mode the write stands and the turn can end with an error still in the file; chapter 4 changes that.

/just-say-so:doctor

The targets line reads files warn (show suggestion) · publish block, artifact · reply warn, and the files .md target shows JustSaySo 6 of 6 rules on. No warnings.

What the agent sees: the rules in the agent’s context, and the report that follows a reply.