site system

Command layer for this site

Search, ask, and route from one quiet surface.

role: design engineer
time: ongoing
team: Solo Project
public: GitHubit's this website 😛

/work/atlascase study /work/portfolio-aicommand demo /portfolio.mdsite brief /resume.jsonresume data

case study

A portfolio should be inspectable

Why

This site treats the portfolio as an interface: readable pages first, command shortcuts second, and AI only when it can point back to proof.

One source, three readable surfaces

System

The same project record renders as a page, Markdown, and JSON, so people and AI inspect one public source.

/work/portfolio-ai

Portfolio OS

A quiet command surface with search, bounded answers, and public routes.

role: design engineer
public: /portfolio.md · /resume.json

The page selects the evidence

Proof

A validated pathname resolves a small set of public sources before Gemini writes a short, linked answer.

current page/work/atlas

project brief/work/atlas.md

portfolio index/portfolio.md

resolved answer

A Team Atlas capstone where my contribution was the first structure, an early monochrome iteration, and the working FR/IC/ER app prototypes tied together by a local real-time server.

/work/atlas

const pageContext = resolvePortfolioContext(pathname); const systemInstruction = [  SYSTEM_PROMPT,  formatPortfolioContext(pageContext),].join('\n\n');