Making d actually usable by ai

[Kapendev]

On Friday, 7 August 2026 at 16:21:03 UTC, Mindy Batek (0xEAB) 
wrote:
> On Friday, 7 August 2026 at 08:33:51 UTC, monkyyy wrote:
>> On Thursday, 6 August 2026 at 18:44:56 UTC, Steven 
>> Schveighoffer wrote:
>>> You are comparing apples to oranges.
>>
>> Its a one word difference in the prompt.
>
> «Apples» and «oranges» are both just one single word as well.
> Little things can make big differences. Especially when they 
> are used to commission a huge probability software apparatus.

I added two words and it changed my life.

```
Grok: I want to make a raylib project in dlang WITHOUT DUB write 
the first 5 steps and a style guide

my_raylib_project/
├── source/
│   └── main.d
├── vendor/
│   └── raylib/          ← contents of raylib-d/source/raylib/
├── lib/                 ← raylib.dll / libraylib.so / .dylib + 
import libs (if not system-installed)
└── (optional Makefile or build script)

dmd -Ivendor source/main.d -L-Llib -L-lraylib 
-L-rpath=\$ORIGIN/lib -of=game
./game
```

The vendor folder can be removed, but not that bad.
For fun, I asked it to do the same with Parin.

```
Grok: I want to make a Parin project in dlang WITHOUT DUB write 
the first 5 steps and a style guide

Your project root now contains app.d, parin/, assets/, and the 
parin_package/ folder (keep it for the scripts).

./parin_package/scripts/run
# Windows: .\parin_package\scripts\run.bat
```

I didn't include the style guide because it basically copy-pasted 
my `STYLE_GUIDE_D.md`. It really likes my markdown files.