Menu
Devenv-based dev environments — devenv.nix layout, process model gotchas, when to pick devenv vs a plain flake devShell
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Set up DeepWork Reviews — automated code review rules using .deepreview config files
Start structured planning — explores, designs, and produces an executable plan
Reference documentation for DeepWork Reviews — automated code review rules using .deepreview configs and DeepSchema-generated rules
Create and manage DeepSchemas — rich file-level schemas with automatic validation and review generation
Start or continue DeepWork workflows using MCP tools
Agent profile/skill maintenance — quickly edit ks-config/agents and commit + push successful changes
| name | platform-devenv |
| description | Devenv-based dev environments — devenv.nix layout, process model gotchas, when to pick devenv vs a plain flake devShell |
Use this when:
.envrc is use devenv (or you're migrating one to it).devenv.nix / devenv.yaml and need to know what defaults bite (notably process.manager.implementation = "native" with broken --detach in 2.0.3).flake.nix (consumed by ks-config), dev shell via devenv. Both conventions apply.Skip this when the repo only has flake.nix with devShells.default — use tool.nix-devshell.md directly.
.gitignore entries, process vs task distinction, the native-manager --detach bug, minimal correct snippet.nixosModules.default output, untouched by the devenv migration.process.managers.process-compose.settings, but only as overrides on processes.<name> entries devenv generates.