Skip to content

Commit d181c0b

Browse files
committed
-
1 parent bd55549 commit d181c0b

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

nix/vibe.nix

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,15 @@
55
inherit (pkgs) lib;
66
inherit pkgs;
77
};
8+
gemini = pkgs.writeShellApplication {
9+
name = "gemini";
10+
text = ''
11+
${unst.gemini-cli}/bin/gemini \
12+
--model gemini-2.5-flash-lite \
13+
--yolo \
14+
"$@"
15+
'';
16+
};
817
app = pkgs.writeShellApplication {
918
name = "vibe";
1019
text = "alacritty";
@@ -25,7 +34,7 @@
2534
asciinema
2635
asciinema-agg
2736
unst.codex
28-
unst.gemini-cli
37+
gemini
2938
];
3039
};
3140
passwd = pkgs.writeTextFile {
@@ -35,7 +44,7 @@
3544
agentsMd = pkgs.writeTextFile {
3645
name = "AGENTS.md";
3746
text = ''
38-
Read the `README.md` file if available. Study the project source code. Write your code in a strictly functional style while ensuring high efficiency. Avoid mutable variables (`mut`), imperative constructs (e.g., `for`, `while`, `loop`, or `return`), and instead use functional iterators. Eliminate redundant closures and variables. Maximize method and function chaining. Avoid `.clone()`, unnecessary allocations, and extra dependencies. Prefer the standard library exclusively when possible. Follow the existing project code style. Use meaningful, context-clear identifiers with a preference for brevity, as in the original code. Do not include comments; the code must be self-explanatory.
47+
Read the `README.md` file if available. Study the project source code. Write your code in a strictly functional style while ensuring high efficiency. Avoid mutable variables (`mut`), imperative constructs (e.g., `for`, `while`, `loop`, or `return`), and instead use functional iterators. Eliminate redundant closures and variables. Maximize method and function chaining. Avoid `.clone()`, unnecessary allocations, and extra dependencies. Prefer the standard library exclusively when possible. Follow the existing project code style. Use meaningful, context-clear identifiers with a preference for brevity, as in the original code. Do not include comments; the code must be self-explanatory. To test Rust code changes you can use the command `cargo test --all-features`.
3948
'';
4049
};
4150
codexToml = pkgs.writeTextFile {

0 commit comments

Comments
 (0)