These rules adapt published engineering guidance; they do not claim those ideas as original work. Each mechanically enforceable idea links back to its source from the rule metadata and rule page.
| Source | Rules influenced |
|---|---|
| ESLint, Create Plugins | Portable plugin API, flat-config presets, and rule metadata |
| Sindre Sorhus and contributors, eslint-plugin-unicorn | Repository structure, per-rule documentation, testing, and release ergonomics |
| TigerBeetle, TigerStyle and full style guide | require-assertions, max-function-lines, max-function-parameters, imports-first |
| Marvin Hagemeister, The barrel file debacle | no-barrel-files, no-barrel-imports |
| TkDodo, The Vertical Codebase | enforce-module-boundaries |
| Sandro Maglione, Components take care of themselves | declarative-components |
| Fernando Rojo, Composition is all you need and Composition Pattern Guide | The three portable composition rules plus require-compound-component-api and require-consumer-owned-compound-usage in the stricter lego preset |
| Vercel, Composition | prefer-composition-over-configuration, require-composable-root-children, no-root-owned-compound-parts |
| Effect, project website and LLM standards | effect-error-handling, no-unvalidated-json-parse, no-unsafe-type-assertions |
| Paul J. Philp, Effect Patterns | effect-error-handling |
| Effect by Example | effect-error-handling, no-unvalidated-json-parse |
| Michael Arnaldi, Effect guide | Effect error, schema, and dependency-injection policies |
| Michael Arnaldi, error-tracker specification | effect-error-handling |
The originating project also references SurrealDB's schema creation best practices and sample industry schemas. Those guides require domain-aware schema review and are not represented as generic AST rules; linking them here preserves attribution without pretending a syntax check can enforce database design quality.
Evalite, Agent Skills, and Cursor Skills are project tooling references rather than sources for a lint policy, so no rule is attributed to them.
The README's combined-tooling example follows the official Biome getting-started guide, Biome domain documentation, Oxlint configuration guide, Oxlint JavaScript-plugin status, and Oxlint incremental migration guidance. These tools complement the plugin; they are not sources for its architecture policies.