Hey, everyone. This is my first post here and I'm introducing a project I've been working on for a little over a year called lintp. It's a tool for linting filesystems and enforcing structure and conventions. You write rules for your file tree in YAML, and it checks the tree against them.
lintp:
custom-matchers:
kebab-case: "matches($BASENAME, /^[a-z0-9]+(?:-[a-z0-9]+)*$/)"
PascalCase: "matches($BASENAME, /^[A-Z][a-zA-Z0-9]*$/)"
config:
.js: "kebab-case"
.ts: "PascalCase"
.dir: "kebab-case || PascalCase"
When a file breaks a rule, the output tells you which clause failed:
โ ./src/badFile.js - .js - Does not match rule: kebab-case && js-file (failed: kebab-case)
Rules can also look at other files. That's the part I use most and my main motivation for creating lintp. I wanted to express relational rules. For example, you can require that a component has a test sitting next to it:
any(siblings("*.test.*"), ...)
or that a directory has a README:
exists("README.md")
siblings(), children() and find() hand you the surrounding tree, and you glue them together with your matchers using && and ||.
There are other libraries for this. ls-lint is the closest and I love that project. I've used it in many projects. But its rules top out at name casing, regex, and file counts per directory. You can't say "this file is only valid if a sibling matching X exists, and X's name has to line up with this one." That rule is the whole reason lintp exists.
eslint-plugin-project-structure goes further than ls-lint. It does folder structure, conditional existence, any extension. But you're forced to use ESLint and Node and you must pick from a fixed menu of rule types instead of writing the predicate yourself. lintp is one binary with a small language and it doesn't care what your stack is.
Under the hood it's Rust. pest parses the DSL. any and all short-circuit and filesystem lookups get cached for the run so a rule that walks the tree doesn't re-walk it for every file. A 400-file tree lints in a few milliseconds on my laptop. More precise benchmarks will be coming.
Install is cargo install lintp, or npx lintp-cli if you're on the npm side. (The npm package is lintp-cli, because npm won't hand over the bare name. The command is still lintp.)
It's early, so there are rough edges and things will probably change as it's a young project but I'm excited to share it and get feedback.
Also, to be upfront: I built a lot of this with Claude Code. Happy to get into how I used it if anyone's curious.
Thank you!