vict00r99

4 ms·

1. 1.▲
   by vict00r99 8mo ago

   You don't map the types, you map the behavior. Define a behavioral contract (inputs, outputs, edge cases) with test cases, and let each language handle types idiomatically. `dict[str, Any]` becomes `Record<string, unknown>` in TS
2. 2.▲
   Rune – Open spec pattern for consistent AI code generation(github.com)

   2 points by vict00r99 8mo ago|3 comments
3. 3.▲
   by vict00r99 8mo ago

   AI coding tools generate different code every time for the same requirement. RUNE is a specification pattern that fixes this: define a function's signature, WHEN/THEN behavior rules, and test cases upfront. Give the same spec to a
4. 4.▲
   by vict00r99 8mo ago

   Hey!Really interesting approach I’m going to try it in one of my CI pipelines Quick question: how granular is the allowlist matching, is it exact domain only or do you support wildcards and subdomain patterns
5. 5.▲
   by vict00r99 8mo ago

   Sure. I ran a direct comparison during development. Without RUNE: I asked Claude to write a "validate_password" function twice in separate sessions. First time it required 1 special character and returned a bool. Second time it re
6. 6.▲
   by vict00r99 8mo ago

   I’d really love your feedback. If you’re building with AI, try defining one real function using RUNE and compare the output across tools.
7. 7.▲
   Show HN: Rune | A spec pattern for consistent AI code generation(github.com)

   1 points by vict00r99 8mo ago|3 comments