القائمة
Instructions for running code quality checks and maintaining standards in the Secret-Hitler-Evals project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | code-quality |
| description | Instructions for running code quality checks and maintaining standards in the Secret-Hitler-Evals project. |
This skill provides instructions for running code quality checks and maintaining standards in the Secret-Hitler-Evals project.
Use the following make targets to ensure code quality:
make fmt: Formats code with Biome and rustfmt.make lint: Lints code with Biome and Clippy.make knip: Finds unused files, dependencies, and exports.make ci: Runs all CI checks (fmt, lint, knip, audit, link-check, test).make fmt and make lint.make ci to ensure no regressions in types or dead code.Produce a Secret Hitler game preview as an Artifact by running the native game-report generator (never a hand-built mock). Trigger whenever the user asks to preview/show/screenshot/visualize a game, run, match, replay, transcript, report, or the UI (e.g. "show me a preview", "preview of the run", "make an artifact of my last game", "artifact of that match") — default to the fixed sample fixture, or use recent/stored/live results when asked. A "run" or "match" holds many games: list its games and pick the decisive one (or ask) rather than treating it as a single game.
The Secret Hitler visual brand (colors, fonts, design language) shared by every frontend in this repo — the Vite eval console and the Next.js/Fumadocs docs. Use whenever building or restyling any UI, adding a new frontend, choosing colors/typography, or generating screenshots/marketing so the look stays consistent with the board game.
Instructions for using prek as a replacement for pre-commit.
Guide for making changes to the Rust backend of the server template, covering the engine crate, the CLI + HTTP API transports, and testing patterns.