Set up and work in the mflux dev environment (arm64 expectation, uv, justfile recipes, lint/format/test).
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.cursor/skills/mflux-dev-env/SKILL.mdThis repo expects macOS arm64 and prefers uv + justfile recipes.
just ≥ 1.50 (brew install just). CI lints the justfile with just --fmt --check; run just fmt-justfile to auto-fix formatting.just installjust lintjust formatjust checkjust builduv run ... for running Python commands to ensure the correct environment.MFLUX_PRESERVE_TEST_OUTPUT=1 enabled (the justfile test recipes already do this).ty, pinned exactly in pyproject.toml dev deps (mirrored in .pre-commit-config.yaml and run in CI). Run it with just typecheck (or uv run ty check).[tool.ty.rules] in pyproject.toml carries a one-time migration baseline (mypy → ty): every rule listed there had pre-existing violations and is set to "ignore", with violation counts in comments.ty check errors, commit, repeat. Prefer starting with low-count rules. Do not add new ignore lines; new code must pass all rules not in the baseline.1430b27
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.