// Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Create a git commit following project conventions.
Create a pull request following project conventions.
**Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.
Review the current conversation and propose structured improvements to skills, documentation, and agent rules.
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
Architecture and agent rules for kurtosis-cdk E2E tests. Load when working on or debugging E2E tests, CI failures in the e2e job, or any task involving bridge testing or kurtosis.
| name | style-prose |
| description | Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/. |
| user-invocable | false |
When writing or editing text files (markdown, plain text, etc.), use Semantic Line Breaks (sembr.org).
., !, or ?).Semantic line breaks make diffs cleaner: editing one clause changes only one line, not the entire paragraph. The rendered output is unaffected.
Apply to all prose in markup files (markdown, rst, adoc, plain text). Do not apply to code blocks, YAML frontmatter, or structured data inside these files.