Join the Agent Deck Discord Server!
Discord에서 Agent Deck 커뮤니티 확인, 357명과 자유 음성·텍스트 채팅 이용
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Trove is a social media app for books, films, and TV shows. Users build a ranked personal library (their "Trove"), maintain an "Up Next" list of things they want to consume, and connect with friends to compare taste, send recommendations, and chat about specific titles. An AI layer powered by the Claude API generates personalised recommendations based on each user's ranked list, as well as taste-match analyses between pairs of friends.README 전문 보기 ↗Trove is a social media app for books, films, and TV shows. Users build a ranked personal library (their "Trove"), maintain an "Up Next" list of things they want to consume, and connect with friends to compare taste, send recommendations, and chat about specific titles. An AI layer powered by the Claude API generates personalised recommendations based on each user's ranked list, as well as taste-match analyses between pairs of friends.
@supabase/ssr)next/fontnpm install
Create a .env.local file at the project root with the following variables:
NEXT_PUBLIC_SUPABASE_URL=<your Supabase project URL>
NEXT_PUBLIC_SUPABASE_ANON_KEY=<your Supabase anon/public key>
TMDB_API_KEY=<your TMDB API key>
ANTHROPIC_API_KEY=<your Anthropic API key>
Set up the database by running the contents of supabase-schema.sql in the Supabase SQL Editor. This creates all tables, indexes, RLS policies, and the auto-profile trigger.
Then start the dev server:
npx next dev
The app will be available at http://localhost:3000. Authenticated users are redirected to /trove; unauthenticated users see a landing page with links to sign up or log in.
src/
app/ # Next.js App Router pages and API routes
api/ # Server-side API routes (see src/app/api/README.md)
trove/ # "My Trove" section: ranked library + Up Next list
explore/ # "Explore" section: incoming nudges + AI discovery
social/ # "Friends" section: people list, compare, groups
messages/ # Conversations inbox
media/[category]/ # External media detail pages (TMDB/Open Library)
item/[itemId]/ # Individual item detail + message thread
login/ # Login page
signup/ # Signup page
components/ # Shared React components (see src/components/README.md)
hooks/ # Custom React hooks (see src/hooks/README.md)
lib/ # Supabase client factories (browser + server)
types/ # Shared TypeScript types (see src/types/README.md)
supabase-schema.sql # Full database schema: tables, indexes, RLS, triggers
Trove is a user's ranked collection of books, films, and TV shows they have already consumed. Items are ordered by rank within each category, and users can drag to reorder.
Up Next is a to-consume list that aggregates items from three sources: things the user adds manually, AI-generated picks, and recommendations sent by friends.
Explore surfaces new content through two channels. "Incoming" shows nudges based on what friends with overlapping taste have in their Troves. "Discover" generates AI-powered personal recommendations using the Claude API.
Social lets users manage friendships, compare Troves with individual friends (seeing shared items, unique items on each side, and a "closeness" score), and request AI-generated taste-match analyses.
Messages are item-anchored conversations. Every message is attached to a specific Trove item and directed at one or more friends, so discussions stay contextual rather than free-floating.
See supabase-schema.sql for the full schema. The main tables are:
| Table | Purpose |
|---|---|
profiles | User profiles, auto-created on signup via trigger |
items | Ranked Trove entries (books, films, TV) |
recommended | User's Up Next list (self-added and AI picks) |
friend_recommendations | Recommendations sent between friends |
friendships | Friend requests and accepted connections |
messages | Item-anchored messages |
message_recipients | Per-message recipient list |
match_recommendations | Cached AI taste-match results per friend pair |
personal_recommendations | Cached AI personal recommendation results per user |
All tables have Row Level Security enabled. Users can only read and modify their own data, with appropriate exceptions for social features (e.g. anyone can view profiles and items, friends can see shared messages).