marcospassos

5 ms·

1.
Show HN: CMS-Powered UI Components(croct.com)
2 points by marcospassos 1y ago|0 comments
2.
by marcospassos 1y ago
Yep, that's something I'd have to figure out.
3.
by marcospassos 1y ago
The value is building the context itself. Using MCP, this could be a method that would get the context to take decisions. For example, here's an example of how I use it currently: ``` const context = await getContext(); const response
4.
by marcospassos 1y ago
Exactly! Something like a tag you install and then query prompt-ready contexts.
5.
by marcospassos 1y ago
Super interesting! However, it focuses on external sources rather than the user journey.
6.
by marcospassos 1y ago
That's a good approach. But what I'm looking for is a bit different, more like Segment, but for LLMs. Something that when a user lands on your website, clicks around, and interacts with your app, you get a full behavioral context
7.
by marcospassos 1y ago
It might help with context generation. But honestly, most of the work is still in tracking, processing, enriching (different services, like IP location, etc), and all the plumbing around it.
8.
by marcospassos 1y ago
Yeah, exactly. My whole point is to avoid doing all that. It adds up fast. What I really want is something that handles the heavy lifting end-to-end: tracking, interpreting, and outputting a prompt-ready summary like: "The user landed
9.
Ask HN: Building LLM apps? How are you handling user context?
31 points by marcospassos 1y ago|18 comments
10.
Show HN: Dynamic headless CMS with built-in CDP, AB testing and personalization(docs.croct.com)
22 points by marcospassos 2y ago|0 comments