Menü
Use when working with Elm projects. Requires running elm-test and elm-review for quality assurance.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | elm |
| description | Use when working with Elm projects. Requires running elm-test and elm-review for quality assurance. |
Always use these tools when working on Elm projects:
Run tests after making changes:
elm-test
Run static analysis after making changes:
elm-review
.elm fileselm-test to verify tests passelm-review to catch common issueselm make src/Main.elm # Compile
elm reactor # Development server
elm-test # Run tests
elm-review # Static analysis
elm-review --fix # Auto-fix issues
elm install <package> # Install package
Use when finishing a task that changed code, config, scripts, prompts, or documentation. Runs the final build/test/lint/review loop, fixes reasonable issues, and reports remaining findings or skipped checks before the final answer.
Use when managing project dependencies with Devbox. Devbox is the preferred dependency manager for new projects - covers package installation, environment variables, and shell configuration.
Use when checking Docker image versions or working with container registries. Skopeo is the required tool for registry queries - never parse Docker Hub web pages.
Use when working with version control. jj (Jujutsu) is the preferred VCS - never use git commands directly when jj can do the job. Covers mental model, workflows, and Nix integration.
Use when working with NixOS configurations, Home Manager setups, Nix flakes, services, or troubleshooting Nix builds. Covers creating new configurations, modifying existing ones, adding packages, setting up services, writing modules, and debugging build failures.
Consolidate multiple PR branches onto a target branch using jj multi-parent rebase with intelligent AI-powered conflict resolution