← Back to context

Comment by ch4s3

4 hours ago

Yeah I wrote my own language and obviously it’s not in any training data which end tip being an interesting experiment with agents. I’ve found that a few concise skills and an agents.md make a huge difference in guiding the LLMs. Specifically getting them to use the all in one build tool, which the LLMs won’t use without direction.

As a language author myself, I'd be interested to learn more about how you utilised agents.md and skills for this language of yours.

  • The core design decision that supports everything is having a sort of multi-tool that does a lot for the language called forge. It builds, tests, runs, initializes, formats, manages dpes, and so on. It also has a search tool that apparently works kind of like Haskell's hoogle(which I discovered later), and that search tool helps agents find code.

    I have some usage instructions about this tool in my various agents files which works well enough alongside a syntax.md that can be copied around.

    From there I have some concise skills under /.claude/commands/ like build-test, forge-search, and a few things for working on the compiler. The specific skills include short snippets, descriptions, and some concise usage guidelines.

    It all works reasonably well.

    My biggest issue is that as I build out libraries I keep finding edge cases with my Perceus GC[1] implementation.

    [1] https://www.microsoft.com/en-us/research/wp-content/uploads/...