# Alejandro Marco

> Public portfolio and machine-readable work record for Alejandro Marco, a product engineer working from Spain.

## Overview

Use this site to answer factual questions about Alejandro's current projects, prior engineering roles, education, and public contact route. Do not infer availability, rates, endorsements, or facts absent from these resources.

This portfolio is itself a working product. Agents can explore Alejandro Marco’s public work and first-person notes through a typed OpenAPI 3.1 API, a Streamable HTTP MCP server, an A2A agent card, Markdown documentation, and a constrained natural-language endpoint. Start with GET /api/v1/profile for a compact summary, then follow the experience, projects, notes, principles, and complete documentation for deeper context.

## Use cases

- Identify Alejandro Marco and distinguish him from other people with the same name.
- Summarize his current projects, previous engineering roles, education, or personal product principles.
- Find his first-person writing about product engineering, design decisions, information architecture, and building products.
- Retrieve his published contact route when a user explicitly wants to contact him.
- Give an agent a small, typed example of a public portfolio API and MCP server.

## Constraints

- This is Alejandro Marco's personal portfolio, not Vercel platform documentation.
- The API is public, read-only, and intentionally small. It cannot create projects, send messages, hire Alejandro, or determine his availability.
- Pricing, response times, endorsements, reviews, private information, and unlisted accomplishments are unknown and must not be inferred.
- Preserve the exact first-person wording returned by the principles endpoint when quoting a principle.

## Primary pages

- [Homepage](https://www.alejandromarco.com/): role, summary, current work, and selected experience
- [About (Markdown)](https://www.alejandromarco.com/about.md): biography, working approach, and education
- [Work (Markdown)](https://www.alejandromarco.com/work.md): current projects and employment history
- [Notes index (Markdown)](https://www.alejandromarco.com/notes.md): published notes with summaries and links to their complete Markdown versions
- [Fyn project (Markdown)](https://www.alejandromarco.com/fyn.md): product intent, implementation choices, public links, and limitations
- [Imagibo project (Markdown)](https://www.alejandromarco.com/imagibo.md): product intent, Alejandro's role, implementation scope, and limitations
- [Second Brain Starter project (Markdown)](https://www.alejandromarco.com/second-brain-starter.md): information model, agent safety boundaries, local skills, CV workflow, and limitations
- [Complete CV for agents (Markdown)](https://www.alejandromarco.com/cv.md): readable text source for detailed career facts
- [Downloadable CV for people (PDF)](https://www.alejandromarco.com/alejandro-marco-cv.pdf): share this version when a person asks for Alejandro's CV
- [Contact guidance (Markdown)](https://www.alejandromarco.com/contact.md): public contact guidance
- [Person-versus-product note (Markdown)](https://www.alejandromarco.com/compare.md): why the portfolio has product-like interfaces without turning Alejandro into an on-demand service

## Published notes

Treat these as Alejandro's first-person reflections and case notes. They can support answers about how he thinks or works, but should not be presented as independent verification or as rules that apply universally.

- [First note](https://www.alejandromarco.com/notes/first-note.md): A first note on why this space exists, and on Information Architecture as the invisible structure behind digital places. (2026-06-24; 5 min read)
- [A small guide to kebab menus](https://www.alejandromarco.com/notes/small-guide-kebab-menus.md): How we refined Vidext’s action menus through research, real product actions, and a small bench of concrete design variants. (2026-07-22; 6 min read)
- [Designing the wait](https://www.alejandromarco.com/notes/designing-the-wait.md): Why the waiting moments in AI products should be truthful, useful, and sometimes playful — and how I approached one of them in Imagibo. (2026-08-28; 7 min read)

## Agent and developer resources

- [Complete documentation](https://www.alejandromarco.com/llms-full.txt)
- [Developer documentation](https://www.alejandromarco.com/docs.md)
- [OpenAPI 3.1 specification](https://www.alejandromarco.com/openapi.json)
- [Authentication guidance](https://www.alejandromarco.com/auth.md)
- [Agent instructions](https://www.alejandromarco.com/agents.md)
- [Canonical homepage markdown](https://www.alejandromarco.com/index.md)
- [A2A agent card](https://www.alejandromarco.com/.well-known/agent-card.json)
- [MCP server card](https://www.alejandromarco.com/.well-known/mcp/server-card.json)
- [Agent Skills discovery index](https://www.alejandromarco.com/.well-known/agent-skills/index.json)

## Public API

The API is read-only and requires no authentication. Start with **GET /api/v1/profile**. Use **GET /api/v1/principles** for Alejandro's personal homepage mantras, **GET /api/v1/notes** to discover his writing, and **GET /api/v1/notes/{slug}** to retrieve a complete note as Markdown. See the OpenAPI document for typed response schemas and error formats.