daily.dev Hackathon MVP Reading signals into buildable software

Content to Project Compiler

Import what you actually read, save, and build around, then turn that signal into a sharper project direction, system shape, and execution plan.

Pipeline

01 Import

Profile, bookmarks, feed, and stack stream in immediately.

02 Analyze

Clusters, project framing, and planning run as smaller debuggable LLM stages.

03 Ship

The output should feel close enough to start building, not just interesting enough to read.

Connect your daily.dev account

Bring your own profile signal.

The best results come from your own bookmarks, feed, and stack. Without a token, the app stays in demo mode. No data will be persisted on the server, and the default inference is local ollama - if you bring a new provider it will process your info though.

Personal access token Optional build steer

This nudges the recommendation. Imported profile activity still supplies the main signal.

Default model route

Provider: ollama

Model: ministral-3:14b

Base URL: http://ollama:11434/api

Auth: not configured

Server-side Ollama is the default cost-control path. Bring your own model route when you want speed or stronger outputs.

Choose a different model route

Use request-level model access instead of the default route

Generated Projects

Build Direction

waiting ollama

Ready

Import a signal set to generate a project.

Use your own daily.dev token for a personalized build direction, or stay in demo mode to inspect the product flow.

Execution

Roadmap

Architecture

System Shape

Growth

Learning Goals

Narrative

Implementation Brief

Compiler Trace

Import Status

Inference

Interest Clusters

Input