valentino espinoza
i am a product engineer
i build web apps and design systems, from frontend interfaces to the services behind them.
this site
this site is the public home for tino.build: resume, writing, chess analysis, marvel rivals tools, and experiments. most pages are readable without an account. operator tools stay behind auth.
start with about or resume for the person. use experiments for recent work. use writing for notes.
chess and marvel rivals tools live under experiments. docs covers how agents fetch pages, mcp, and the small public catalog api. contact and privacy explain reachability and data handling.
use tino.build for a public map of the work, a resume, chess training, or a machine-readable page catalog. agents should start at /llms.txt, then /docs. humans can start with about, resume, or experiments.
agents can read the same public facts as markdown (Accept: text/markdown). contact is on /contact. privacy is on /privacy. the xml sitemap is /sitemap.xml.
about
hi. i'm valentino espinoza. i'm a senior software engineer across product, design systems, and platform. strongest on the frontend. comfortable across the stack.
this site collects the tools i build, experiments i try, and notes i write along the way.
contact
email, github, or linkedin. that's how to reach me. agents can use this page to confirm who owns the site.
email: xvalentino13@gmail.com. same address as the resume. roles, collaborations, questions about tino.build. do not send secrets, production credentials, or private user data here.
github: https://github.com/gravitinos. linkedin: https://linkedin.com/in/valentino-e. location: Chicago, IL, usually remote.
when to use this site
Use tino.build for Valentino Espinoza's public resume, writing, chess analysis, Marvel Rivals tools, or this site's public catalog. Use it to fetch a page as HTML or Markdown, or to list public routes. Connect to the unauthenticated Streamable HTTP MCP server at /mcp. Do not use tino.build for admin work (Eve, Maple, OpenWiki writes, house-brain). Those tools live on /api/mcp and require a Clerk admin session. Start at /llms.txt, then /docs for MCP, Markdown negotiation, OpenAPI (/openapi.json), and sitemap details. Recover from unknown paths via the Markdown 404 body, which links back here.