Menu
Conventions for Markdown files in this repository.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guidelines for Michael Vorburger's personal Git commit style.
Guidelines for Michael Vorburger's preferred Git workflow.
Java coding, testing, and logging conventions.
Guidelines for determining how to test a project based on its contents.
Enforces TypeScript and project-specific coding standards, including Bun usage and the zero-warning policy. Use this skill when creating or modifying any TypeScript or configuration files.
Update Nix flake inputs.
| name | markdown-conventions |
| description | Conventions for Markdown files in this repository. |
Whenever possible, use relative instead of absolute links to *.md Markdown files within the same Git repository.
Directory paths in Markdown files should be formatted as clickable relative file links, e.g., [dir](path/to/dir/).
Link texts ("dir", here) should be surrounded by single backticks (so dir).
