Defame1297
b07d54ad7a
Each of these would send a user down a path Vale does not support: Core options placed under a glob header are not scoped to that glob — Vale rejects them with E201, so the guidance to nest them produced a config that will not load. The built-in `Vale` style is compiled in, but Vale still requires StylesPath to exist on disk before it will run, so the "no StylesPath needed" shortcut fails. The MDX guidance was inverted: under `[formats] mdx = md` the mapping is what makes MDX lint at all, and it needs the mdx2vast prerequisite that was never mentioned. And a spelling rule's `ignore` paths resolve against StylesPath, not against the rule file's own directory, so the documented relative paths silently matched nothing.
vale-config
Install and configure Vale, the prose/style linter — .vale.ini, StylesPath, built-in/third-party/custom styles, and activation via BasedOnStyles.
What it does
Covers the setup side of Vale: getting a project from no config to a working .vale.ini where vale sync runs clean and every declared style is actually activated for the right files. Does not run Vale or interpret its output — see vale-run for that.
Usage
/vale-config
Describe what you want configured: initial setup, adding a third-party style package, or a custom rule. The skill covers install, StylesPath layout, .vale.ini structure, and BasedOnStyles activation.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/configuration-reference.md |
Full .vale.ini fields, rule-header fields, and frontmatter-scope behaviour |
references/sources.md |
Research sources backing the Vale configuration guidance |