Menu
Formats section separator comments in source files. Use when writing or editing comments that function as section separators.
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
Ensures markdown files conform to rumdl linting rules and personal formatting preferences. Use when creating or editing .md files, or when user mentions formatting, linting, or rumdl.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Reference for writing and editing skills well - the vocabulary and principles that make a skill predictable.
Implement a piece of work based on a PRD or set of issues.
Ensures issue titles conform with a specific style. Use when creating or editing an issue.
| description | Formats section separator comments in source files. Use when writing or editing comments that function as section separators. |
| name | section-separator |
Ensure section separator comments follow a consistent three-line format with dashes aligned to the label length.
Each section separator consists of three commented lines:
The dashes must be vertically aligned - the top and bottom lines have the same number of dashes as the length of the label on the middle line.
// --------------------- //
// test_xxx - happy path
// --------------------- //
# ---------------- #
# dev-dependencies
# ---------------- #
# ---------------- #
# helper functions
# ---------------- #
// --------- //
// main loop
// --------- //
When writing or encountering a section separator comment: