agentleFS
Sign inStart free
ThinkEx-OSSThinkEx-OSS/thinkex/public/llms.txt

thinkex

llms.txt55 starsChanged 3 months agoMITView on GitHub

ThinkEx is a workspace for source-heavy study, research, and creation. Use the product documentation for supported behavior. ThinkEx currently exposes an MCP server for agent integrations; it does not publish a general-purpose REST API, OpenAPI specification, or webhooks.

  • In this repositoryOne other file it gives its agents.

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the product documentation for supported behavior.

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# ThinkEx

> ThinkEx is a workspace for source-heavy study, research, and creation.

Use the product documentation for supported behavior. ThinkEx currently exposes an MCP server for agent integrations; it does not publish a general-purpose REST API, OpenAPI specification, or webhooks.

## Product

- [ThinkEx home](https://thinkex.app/): Product overview, features, and pricing.
- [ThinkEx documentation](https://docs.thinkex.app/index.md): Documentation index.
- [ThinkEx quickstart](https://docs.thinkex.app/quickstart.md): Create a workspace and begin working with sources.

## Developers and agents

- [ThinkEx developer resources](https://thinkex.app/developers): Supported integration surfaces and source code.
- [ThinkEx MCP server](https://docs.thinkex.app/guides/mcp.md): MCP endpoint, OAuth flow, permissions, clients, and available actions.
- [ThinkEx architecture](https://docs.thinkex.app/configuration/architecture.md): Application architecture and service boundaries.
- [ThinkEx local development](https://docs.thinkex.app/configuration/local-development.md): Run the open-source project locally.
- [ThinkEx deployments](https://docs.thinkex.app/configuration/deployments.md): Deployment configuration.
- [ThinkEx source code](https://github.com/ThinkEx-OSS/thinkex): Open-source repository.

## Optional

- [Sitemap](https://thinkex.app/sitemap.xml): Index of public pages.
- [ThinkEx blog](https://thinkex.app/blog): Product updates and articles.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free