the signals and their derived score are provisional and subject to change.
validate manually before sharing.
3ef67af7dfed776cb03012563942cdf3a97f1b59e2a8692e64e42 months agoCo-authored-by: Claude Sonnet 5 <noreply@anthropic.com>8848970d8e4d2 months ago🤖 Generated with [Claude Code](https://claude.com/claude-code)c350cf6e4d5b2 months agoCo-authored-by: Cursor <cursoragent@cursor.com># AGENTS.md
ZLint is anopinionated linter for the Zig programming language, written in Zig.
## Output Principles
- All code must be correct and memory safe. No undefined behavior or sloppy work.
- We care heavily about performance. Every cache miss and allocation matters.
- Test everything extensively. Leave nothing unverified.
- Avoid wasting tokens. Don't summarize what you will do before doing it; just do it.
- Ask yourself: "Would a staff engineer do this?" If the answer is no, don't do it.
## Rules---
name: zlint-new-rule
description: Author a new zlint lint rule end-to-end - scaffold the rule file, implement the runOnNode/runOnSymbol/runOnce hooks, write RuleTester pass/fail/fix cases with snapshot output, and regenerate docs and schema. Use when adding a lint rule, implementing a rule listed on the rule ideas board, renaming or recategorizing an existing rule, or when the user mentions creating, adding, or scaffolding a rule in this repo.
---
# Authoring a zlint Lint Rule
Use this skill when addinone