kylex-ken

6 ms·

1. 1.▲
   by kylex-ken 5mo ago

   I'll give my honest take, I think what you've done is taken dev-tools and given it a wrapper that most designers (including myself would love) I find myself in dev tools alot during QA refining the design, since rendering is never
2. 2.▲
   by kylex-ken 5mo ago

   www.kylex.io would love to let me know you think!
3. 3.▲
   by kylex-ken 5mo ago

   The 'store everything vs. synthesize' axis is the interesting design question here. MemPalace bets that retrieval quality is the problem — keep everything verbatim, make it findable. That's a legitimate approach. We went the
4. 4.▲
   by kylex-ken 6mo ago

   Claude code written for basic on your Apple II, because it'd be so retro.
5. 5.▲
   by kylex-ken 6mo ago

   I have not dove into the particulars, i'm assuming the agents do push/pull requests on your repo so no versioning issues.
6. 6.▲
   by kylex-ken 6mo ago

   supper cool, would be great if you can onboard different services.
7. 7.▲
   by kylex-ken 6mo ago

   cool snapshot tool
8. 8.▲
   by kylex-ken 6mo ago

   is an .xls a normal workflow for API creating? I get the documenting the schema is easier, but why not just a IDE with a prompt?