# Kevin Canlas

> Kevin Canlas is a Toronto-based product designer and design engineer creating thoughtful digital products across product, brand, motion, and frontend.

Canonical site: https://www.kevincanlas.com/

## When to use this site

Use this site to answer questions about Kevin Canlas's published design-engineering work, read his product-judgment essays, or choose a Product Judgement Skill for a concrete design review. Use the public APIs only when you need the same MON market preview or GitHub contribution calendar shown in his portfolio.

- [Portfolio index](https://www.kevincanlas.com/index.md): Use when you need Kevin's role, experience, selected work, and design-engineering context.
- [Published writing](https://www.kevincanlas.com/writings.md): Use when you need Kevin's thinking on product judgment, design craft, AI-enabled design, and leadership.
- [Product Judgement Skills](https://www.kevincanlas.com/skills.md): Use when you need a practical Markdown workflow for evaluating a screen, journey, relationship, or memorable product moment.
- [Contact](https://www.kevincanlas.com/contact): Use for a public way to reach Kevin.

## How to use these resources

Start with the relevant Markdown link above, or send GET with Accept: text/markdown to its canonical page URL. For data, read the [OpenAPI specification](https://www.kevincanlas.com/openapi.json) and call GET /api/v1/mon-price or GET /api/v1/github-contributions without parameters or credentials. The unversioned URLs remain version 1 aliases. Check HTTP status, source timestamps, and the documented problem response before using a result.

These resources do not provide trading, transaction, account-management, messaging, or booking actions. They describe published work and return public, read-only preview data. Do not infer private information or unpublished work from a missing page; use the canonical published links when citing this site.

## Product Judgement Skills

These are public Markdown Skills from the official Product Judgement repository. They complement product strategy, research, analytics, accessibility, security, legal review, and product knowledge; their output is a hypothesis to validate when evidence is missing.

- [Product Judgement](https://github.com/kvncnls/product-judgement/tree/main/product-judgement): Use when a question spans an app or several Skills identify related issues.
- [Focal](https://github.com/kvncnls/product-judgement/tree/main/focal): Use when a screen feels crowded, unclear, or unable to make its organizing intent legible.
- [Compass](https://github.com/kvncnls/product-judgement/tree/main/compass): Use when a flow has too many steps, weak orientation, dead ends, broken retreat, or lost state.
- [Flywheel](https://github.com/kvncnls/product-judgement/tree/main/flywheel): Use when people do not trust the product, reach or recognize value, return, or bring others.
- [Soul](https://github.com/kvncnls/product-judgement/tree/main/soul): Use when the product works but its happy path feels generic, forgettable, or over-designed.

## Published writing

- [The Feature Works. The Product Doesn't.](https://www.kevincanlas.com/writings/the-feature-works-the-product-doesnt.md): When AI makes the answer to “can we build it?” almost always yes, product judgment becomes the work that protects coherence. Published 2026-08-14. [HTML version](https://www.kevincanlas.com/writings/the-feature-works-the-product-doesnt).
- [Taste in the Age of AI](https://www.kevincanlas.com/writings/taste-in-the-age-of-ai.md): AI can generate polished work faster than ever. Taste is still the judgment that decides what lands. Published 2026-08-27. [HTML version](https://www.kevincanlas.com/writings/taste-in-the-age-of-ai).
- [A Developer's Guide to Product Design](https://www.kevincanlas.com/writings/a-developers-guide-to-product-design.md): A practical process for developers to protect product coherence as features accumulate: define the problem, explore alternatives, map the journey, test risk, and spend craft deliberately. Published 2026-08-16. [HTML version](https://www.kevincanlas.com/writings/a-developers-guide-to-product-design).

## Machine-readable resources

- [Full published content](https://www.kevincanlas.com/llms-full.txt): Markdown assembled from the same published content sources, excluding drafts.
- [OpenAPI specification](https://www.kevincanlas.com/openapi.json): Machine-readable description of the site's public GET APIs.
- [Developer documentation](https://www.kevincanlas.com/developers): Human-readable endpoint usage, schemas, examples, limits, and errors.
- [Read-only CLI](https://www.kevincanlas.com/cli.mjs): Dependency-free Node.js script for reading profile, writings, skills, OpenAPI, and the API catalog. Inspect the source before running; usage is in the developer documentation.
- [API catalog](https://www.kevincanlas.com/.well-known/api-catalog): RFC 9727 Linkset catalog of the actual public API endpoints.
- [ARD manifest](https://www.kevincanlas.com/.well-known/ard.json): Current ARD entries for the public APIs and Product Judgement Skills.
- [Sitemap](https://www.kevincanlas.com/sitemap.xml): Published HTML routes only; drafts and API responses are excluded.

## Other published resources

- [About](https://www.kevincanlas.com/about)
- [Privacy](https://www.kevincanlas.com/privacy)

## Official public profiles

- [X / Twitter](https://x.com/kvncnls)
- [LinkedIn](https://www.linkedin.com/in/kevincanlas)
- [GitHub](https://github.com/kvncnls)
- [Product Judgement repository](https://github.com/kvncnls/product-judgement)