# Tessli

> Tessli is a human-curated, AI-native design-source router.

Tessli helps people and coding agents describe a design or frontend task, find a small relevant set of sources, understand why each source fits, and choose an appropriate access route. It is research guidance, not a provider mirror or an autonomous taste engine.

## Canonical human routes

- /resources — task-first source browser.
- /resources/[slug] — source guide.
- /collections — guided research paths.
- /collections/[slug] — ordered research checklist.
- /for-ai — current human-to-agent workflow and local setup.

## Public machine-readable forms

Source guides have compact JSON and Markdown representations:

- /resources/[slug]/profile.json
- /resources/[slug]/profile.md

Published Collections have compact JSON and Markdown representations:

- /collections/[slug]/collection.json
- /collections/[slug]/collection.md

Existing examples:

- /resources/landingfolio/profile.json
- /resources/landingfolio/profile.md
- /collections/saas-landing-pages/collection.json
- /collections/saas-landing-pages/collection.md

## Local MCP only

Tessli's MCP server is a local, read-only, repository-backed stdio process. There is no hosted or remote MCP endpoint. It uses public repository data and does not write Tessli state.

## Boundaries

- No Board or Saved data is public: both stay browser-local and private.
- Tessli has no bulk catalogue API or bulk public-data endpoint.
- No provider crawl, proxy, or credential handling: Tessli does not bypass provider access controls.
- Recheck provider access, pricing, licensing, terms, availability, and other time-sensitive details at the provider.
- No universal rankings or universal design-taste claims.