conventionslisted

# Conventions This skill ships the convention rules under `rules/`. When the plugin is installed in another project, those files load on demand from here. `plain-language`, `security`, `usa-english`, and `user-questions` apply to every request. The `user-questions` rule points at the `ask` skill for the picker. The rest carry `paths:` frontmatter and load when you open a matching file. Read the file that matches what you are doing: - [`rules/code-style.md`](./rules/code-style.md) for ESM conventions, naming, imports, and exports. - [`rules/jsdoc.md`](./rules/jsdoc.md) for the JSDoc essentials. The full reference lives in the separate `jsdoc` skill. - [`rules/markdown.md`](./rules/markdown.md) for markdown structure. The `documentation` and `humanizer` skills cover writing voice and SEO. - [`rules/plain-language.md`](./rules/plain-language.md) for the ISO 24495-1 plain language standard that agent responses and other user-facing output follow. - [`rules/security.md`](./rules/security.md) for secrets, input validation at trust boundaries, and safe shell use. - [`rules/testing.md`](./rules/testing.md) for Vitest patterns and what to test. - [`rules/usa-english.md`](./rules/usa-english.md) for the USA English spelling convention used across code, comments, and docs. - [`rules/user-questions.md`](./rules/user-questions.md) to load the `ask` skill when a task is blocked on information only the user can supply. If a rule conflicts with a project-specific instruction