惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
Google DeepMind News
Google DeepMind News
Microsoft Security Blog
Microsoft Security Blog
Martin Fowler
Martin Fowler
MyScale Blog
MyScale Blog
The GitHub Blog
The GitHub Blog
I
InfoQ
A
About on SuperTechFans
GbyAI
GbyAI
宝玉的分享
宝玉的分享
爱范儿
爱范儿
博客园 - 【当耐特】
博客园 - 司徒正美
博客园 - 聂微东
P
Proofpoint News Feed
WordPress大学
WordPress大学
云风的 BLOG
云风的 BLOG
Last Week in AI
Last Week in AI
阮一峰的网络日志
阮一峰的网络日志
B
Blog RSS Feed
Jina AI
Jina AI
aimingoo的专栏
aimingoo的专栏
J
Java Code Geeks
博客园 - 叶小钗

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I built an AI-powered movie curator with Python and Strea...
Claudio Marcelino · 2026-06-26 · via DEV Community

I've been a movie person my whole life.
Growing up in the 80s and 90s, I'd go to the video store without knowing what I wanted and walk out with five tapes. Browsing shelves, reading back covers, picking something just because the title was weird. It was slow and it worked.
Today you open Netflix with 10,000 options and spend 40 minutes picking nothing.
The problem isn't lack of content. It's lack of curation. So I built something about it.

What I built

CineAntologia AI — a public catalog of movies and TV shows from the 80s to today, with an AI chat that works like a film curator instead of a search engine.
You describe what you want to feel while watching:

"Something like Stranger Things, that 80s atmosphere and suspense"
"Heavy crime drama like The Wire"
"Philosophical sci-fi in the style of Blade Runner"

And it gives you suggestions with actual cultural context — not just a list.
Live demo: (https://cineantologia-ai.streamlit.app)

The stack
Nothing exotic:

Python 3.11
Streamlit — for the UI and deploy
TMDb API — free, great data, covers posters, genres, ratings, where to watch
OpenAI GPT-4o-mini or Groq for the AI chat
Streamlit Community Cloud — free deploy for public repos

No database in v1. No auth. No over-engineering.

Three decisions worth talking about

  1. Ship on day one
    I pushed the repo public and deployed the moment it minimally worked. No months of polishing in private.
    When it's a drawer project you optimize for the code. When it's public you optimize for the person using it. That shift in perspective is worth the discomfort of shipping something imperfect.

  2. Users bring their own API key
    The AI Chat uses GPT-4o-mini or Groq. Instead of covering API costs for everyone — unpredictable at scale — users paste their own key in the sidebar. It lives only in their browser session, never hits my server.
    Three wins: zero cost to scale, real privacy, and the user actually learns how an AI API works.
    For anyone without a key, I point them to Groq — free, no credit card, fast as hell:

  3. Dumb pages, smart services

app/
├── pages/ # only renders, no logic
├── services/ # all data and AI logic lives here
└── utils/ # config, CSS, shared sidebar

Each page is as dumb as possible — it just calls a service and renders the result. All TMDb calls, normalization, and AI prompting stay in services/. Made the whole thing much easier to iterate on.

What was actually hard
The system prompt. Getting the AI to respond like a real curator took more iteration than I expected. The fix that worked was enforcing a strict output format:

SYSTEM_PROMPT = """You are CineAntologia AI, a film curator specialized 
in movies and TV shows from every decade.

Always end your response with suggestions in this exact format:
Title (Year) — reason in one line

Minimum 4, maximum 6 suggestions."""

That fixed format made a huge difference in consistency.
Normalizing TMDb data. Movies have title and release_date. Shows have name and first_air_date. I wrote a _normalize() function that flattens everything into the same schema before any page touches the data:

def _normalize(items: list) -> list[dict]:
    out = []
    for item in items:
        mt = item.get("media_type", "movie")
        if mt == "person":
            continue
        title = item.get("title") or item.get("name") or ""
        date = item.get("release_date") or item.get("first_air_date") or ""
        year = int(date[:4]) if date and len(date) >= 4 else None
        out.append({
            "id": item.get("id"),
            "title": title,
            "year": year,
            "type": "Movie" if mt == "movie" else "Series",
            "genres": [...],
            "synopsis": item.get("overview", ""),
            "poster": poster_url(item.get("poster_path")),
            "rating": round(item.get("vote_average", 0), 1),
        })
    return out

CSS in Streamlit. Streamlit has strong opinions about styling. Custom dark theme with Bebas Neue + Inter required injecting CSS via st.markdown() with unsafe_allow_html=True. Not pretty, but it works.

What's next

Anime and K-drama — huge audience, badly served by recommendation tools
Oscar Hall of Fame since 1929 — every category, with poster and where to watch today
Semantic search — embeddings to search by vibe, not just title
Specialized agents — horror agent, sci-fi agent, drama agent

Try it

🎬 (https://cineantologia-ai.streamlit.app)
For the AI Chat, grab a free Groq key at https://console.groq.com — no credit card, takes 2 minutes.
Feedback, suggestions, and PRs are very welcome. Still early, lots of room to grow.

Built with Python, Streamlit, TMDb API, and coffee.