Skip to main content
This knowledge base documents a single developer’s working world: multiple ventures (GreekCore, Relic, Mavri Studio), a set of research and hackathon labs, and the agent-first workflow that ties them together.

The one-liner

A meticulously reproducible, agent-first macOS development environment running multiple ventures plus personal work, built around Claude Code, a Linear-driven process, and a shared team-memory layer (Hyper).

Infrastructure as config

The whole machine — shell, editor, git, Claude Code — bootstraps from version-controlled dotfiles in one command.

Agent-first development

Parallel git worktrees, variant forks for design exploration, and vendored, content-pinned agent skills.

Linear-centered process

Linear is the unit of work; branches, Conventional Commits, and PRs all link back to issues.

Two-pole stack

Next.js (App Router, canary) for every web surface; Python (pyproject) for every AI backend.

The two-pole stack

Almost everything resolves to one of two technology poles. Knowing which pole a project sits on tells you most of what you need about its toolchain and conventions.
The Next.js repos run bleeding-edge canary builds. Each carries a standard nextjs-agent-rules block reminding agents: “This is NOT the Next.js you know — read node_modules/next/dist/docs/ first.”

The portfolio at a glance

Work is organized into venture groupings, each holding one or more repositories.

GreekCore

Multi-tenant SaaS for Greek-life organizations. The primary daily driver, spanning a workspace orchestrator and api / web / mobile / infra / docs child repos.

Relic

An AI-native team-memory layer that turns engineering history into a temporal knowledge graph and serves it to coding agents over MCP.

Mavri Studio

A backend that turns brand source material into a versioned Brand Kit and generates on-brand copy and imagery from it.

Labs

The agent-simulator and a run of hackathon and course projects — including a HooHacks first-place winner.

Personal & tooling

personal-site, dotfiles, LaTeX-Resume, and the configuration that reproduces the whole environment.

How a venture is structured

The most sophisticated ventures share a common shape, modeled most fully by GreekCore v2:
1

A workspace orchestrator

A parent repo owns only cross-cutting tooling. A single front door (mise.toml) pins the toolchain and defines every dev task.
2

Independent child repos

A repos.manifest clones the real repos (api, web, infra, docs) — gitignored, not submodules. The workspace stays thin.
3

One-command local stack

mise run setup clones, installs, and fans out secrets; mise run dev boots Postgres, migrations, seeds, and every app process under process-compose.
4

Agent-agnostic rules

A one-line CLAUDE.md imports a shared AGENTS.md — a single source of truth carried identically across every repo in the venture.
See Engineering for the full breakdown of the workstation, Claude Code configuration, conventions, and the workspace pattern.

Who builds this

Paris Phan — sole developer and founder across these projects (with collaborators on Relic). Apple Silicon M4 Mac Mini, fish shell, Claude Code as the primary development interface.

Browse the repository directory

See every repository across the GreekCore, Relic, Mavri, and personal accounts.
Last modified on June 22, 2026