AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Additional linting rules for Rust projects
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Additional linting rules for Rust projects.
See the homepage or the rules/ directory for all the rules implemented so far.
See planned-rules/ for all the rules not yet implemented.
Install Dylint, then add perfectionist to your workspace's dylint.toml:
Each lint registers under the perfectionist tool namespace. See CONTROLLING_RULES.md for how to change a rule's level per call site or project-wide, and how to enable or disable rules globally.
dylint.toml accepts a crate-wide [perfectionist] table and per-rule ["perfectionist:: "] tables. See CONFIGURATION.md for the full schema.README 전문 보기 ↗Additional linting rules for Rust projects.
See the homepage or the rules/ directory for all the rules implemented so far.
See planned-rules/ for all the rules not yet implemented.
Install Dylint, then add perfectionist to your workspace's dylint.toml:
[workspace.metadata.dylint]
libraries = [
{ git = "https://github.com/KSXGitHub/perfectionist" },
]
Run the lints:
cargo dylint --all -- --all-targets
Each lint registers under the perfectionist tool namespace. See CONTROLLING_RULES.md for how to change a rule's level per call site or project-wide, and how to enable or disable rules globally.
dylint.toml accepts a crate-wide [perfectionist] table and per-rule ["perfectionist::<rule>"] tables. See CONFIGURATION.md for the full schema.
Prerequisites:
cargo-dylint and dylint-link are not part of the cargo dependency graph but their ABI is coupled to it. They're installed into a workspace-local .dev-tools/ directory (pinned to the dylint_linting version in Cargo.lock) by:
just install-dev-tools
Run this once after cloning, and again whenever dylint_linting is bumped. Every other just recipe prepends .dev-tools/bin to PATH, so subsequent commands use the pinned binaries automatically.
Run the following command to check everything:
just all
This code base is almost entirely AI-generated. Or in other words, vibe-coded.
I needed a way to automatically force the AI agents I use to comply with a certain code style, reducing the time I'll have to spend micro-managing and reviewing AI-generated code. I cannot rely on them interpreting the rules in the Markdown guides correctly, and they often don't comply with the rules completely. Hence, I looked at the code style guides and thought: "Hmm, some of these rules can be coded into a program!" and so this program was born.
I needed encode these rules quick, so I chose vibe-coding.
The code quality of this code base is not as important as the code quality this code base will enforce upon others. This code base is, after all, scaffholding.