2 ms·

Here's an idea. There have been over a dozen commits in the last 2 hours. If you are actually "vibe coding" a Prolog, then post the prompts you have used in t

Here's an idea. There have been over a dozen commits in the last 2 hours. If you are actually "vibe coding" a Prolog, then post the prompts you have used in the last 2 hours here. If it helps to have a specific starting point, commit 7bbe652[0] is as good as any. 0 - https://github.com/nlothian/Vibe-Prolog/commit/7bbe652eaf0b0e634a553bc4966d7770b4ed1507 https://github.com/nlothian/Vibe-Prolog/commit/7bbe652eaf0b0...

nl 11mo ago
Wait, you think I'm coding this by hand! That is amazing. I love it! I don't remember when which part happened, but I've been gradually moving over to the tools in https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools for most of the development. Most of the coding itself there is done with kilocode. Most of the early conversations don't seem to be available in Claude code now (is there a way to see complete history?), but here's a typical session: > can this interpreter pass command line arguments to the prolog program? [no] > add these as missing to @FEATURES.md [done] > use `gh issue` to create an issue to address this. > - Explain comprehensively what needs to be done > - Note that new test cases must be created > - Note that @FEATURES.md needs updating > Do not provide estimates That raised: https://github.com/nlothian/Vibe-Prolog/issues/75 https://github.com/nlothian/Vibe-Prolog/issues/75 Here's the PR for that: https://github.com/nlothian/Vibe-Prolog/pull/92/files https://github.com/nlothian/Vibe-Prolog/pull/92/files That PR was generated using my fix-issue-with-kilocode command. The source code for that is all in here: https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools. The code reviews were done with Codex and Gemini, and responded to using my address_pr_comments command in that same directory.

nl 11mo ago

Wait, you think I'm coding this by hand! That is amazing. I love it! I don't remember when which part happened, but I've been gradually moving over to the tools in https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools for most of the development. Most of the coding itself there is done with kilocode. Most of the early conversations don't seem to be available in Claude code now (is there a way to see complete history?), but here's a typical session: > can this interpreter pass command line arguments to the prolog program? [no] > add these as missing to @FEATURES.md [done] > use `gh issue` to create an issue to address this. > - Explain comprehensively what needs to be done > - Note that new test cases must be created > - Note that @FEATURES.md needs updating > Do not provide estimates That raised: https://github.com/nlothian/Vibe-Prolog/issues/75 https://github.com/nlothian/Vibe-Prolog/issues/75 Here's the PR for that: https://github.com/nlothian/Vibe-Prolog/pull/92/files https://github.com/nlothian/Vibe-Prolog/pull/92/files That PR was generated using my fix-issue-with-kilocode command. The source code for that is all in here: https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools https://github.com/nlothian/Vibe-Prolog/tree/main/ai-tools. The code reviews were done with Codex and Gemini, and responded to using my address_pr_comments command in that same directory.