We just launched Croct Templates, a way to drop CMS-powered components into your app with a single command.It's like Shadcn, but for CMS, AB testing and personalization:* Built-in support for A/B testing, content editing, and dynamic logic * Works with existing projects (Next.js, React, etc.) * Supports community libraries via `npm://`, `shadcn-ui://`, etc.Example:```bash npx croct@latest use...
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 = await generateText({ system: `Here's the user context: ${context}`, messages: [...] });
console.log(context);
// "First-time visitor using Google Chrome on a MacBook, browsing from San Francisco.
// Landed on the pricing page from a Google ad, clicked to compare plans,
// then visited the enterprise section before initiating a support chat."
```
It's like a session recorder for LLMs that captures rich user behavior and traits (like device, browser, location, and journey) and turns them into LLM context. Your agent or app instantly becomes more helpful, relevant, and aware without wiring up your own tracking and enrichment pipeline.
"The user landed on the pricing page from a Google ad, clicked to compare plans, then visited the enterprise section before initiating a support chat."
I've been building stuff with LLMs, and every time I need user context, I end up manually wiring up a context pipeline.Sure, the model can reason and answer questions well, but it has zero idea who the user is, where they came from, or what they've been doing in the app. Without that, I either have to make the model ask awkward initial questions to figure it out or let it guess, which is...
https://docs.croct.com/introduction/getting-started
Hey HN,I'm a developer and long-time OSS contributor. Over the years, I've implemented tons of headless CMSs to give product and marketing teams more autonomy. But there's always been a gap with CMSs when it comes to user interfaces.I kept running into the same issues: poor developer experience, bad performance, no support for dynamic content, and needing vendors for AB testing or...