worldlabs-mcp
sandraschi/worldlabs-mcp/llms-full.txt
REST backend (port 10865) serves the webapp and spatial bridge. A Vite/React frontend (port 10864) provides a full control UI including world library, prompt memory, local LLM refinement
How real projects summarise themselves for language models.
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.
sandraschi/worldlabs-mcp/llms-full.txt
REST backend (port 10865) serves the webapp and spatial bridge. A Vite/React frontend (port 10864) provides a full control UI including world library, prompt memory, local LLM refinement
wonsukchoi/domain-experts/docs/llms.txt
method to confirm it solidifies after the section it feeds, isolating whether a gas… - [Frontend Engineer](https://domainexperts.dev/roles/frontend-engineer/): diagnosing which Core Web Vital (LCP/INP/CLS) a change actually affects before
nirholas/pumpfun-claims-bot/llms-full.txt
Telegram - **skip cashback**: Cashback claims (user refunds, not creator activity) ## Web Dashboard Two React frontends are checked in, and they are not the same app: | Directory | What it is | Build
nirholas/pumpkit/llms-full.txt
Ready | | [`@pumpkit/tracker`](packages/tracker/) | Group call-tracking bot with leaderboards & PNL cards | ✅ Ready | | [`@pumpkit/web`](packages/web/) | Frontend dashboard and documentation site | 🏗️ Skeleton | > **npm:** Packages will be published to npm under the `@pumpkit
sandraschi/ocr-mcp/llms-full.txt
backend/app.py` | FastAPI web backend (scanner, upload, settings, auto-scan, book pipeline) | | `web_sota/src/` | React frontend | | `run_server.py` | PyInstaller entry point for NSIS builds | ### Ports | Service | Port | |---------|------| | Vite frontend | 10858 | | FastAPI backend
sandraschi/ocr-mcp/llms.txt
repo root - **Web UI**: `just webapp` or see README “Web Interface”; backend and frontend ports in docs ## MCP listing - **Glama.ai**: Use [glama.json](glama.json) snippet for MCP client config - **GitHub
kimyoungwopo/cafe24-smart-design/llms.txt
Design Reference > Korean reference for Cafe24 Smart Design storefront work. It is built for frontend developers and AI coding agents that need safe, verifiable Cafe24 skin/module guidance. Canonical
mimnets/OpenHRApp/public/llms-full.txt
# OpenHRApp > OpenHRApp is free, open-source HR management software for small and mid-sized
danicat/skills/llms.txt
conquer architecture for complex, multi-system, or orthogonal engineering initiatives (e.g., concurrent backend, frontend, database, QA). Manages hierarchical Lead Agents and Specialists, disjoint work allocations, and strict parent-child communication
skein-js/skein-js/llms-full.txt
activity, and graph updates as they happen. Connect with the LangGraph SDK and its frontend bindings, including React's `useStream`. [Streaming](./docs/streaming.md) · [Client integration](./docs/react-sdk.md) - **Human approvals and checkpoint history
skein-js/skein-js/llms.txt
Dated verification scope and intentional Agent Server differences. - [React SDK / useStream](https://github.com/skein-js/skein-js/blob/main/docs/react-sdk.md): Frontend compatibility — `@langchain/langgraph-sdk` and `useStream` over SSE. - [Storage](https://github.com/skein-js/skein-js/blob/main/docs/storage.md): `SkeinStore`, memory/SQLite/Postgres selection, pgvector semantic
anthony-chaudhary/dos-kernel/llms-full.txt
# DOS — the Dispatch Operating System (dos-kernel) — llms-full.txt > The one-fetch expansion of llms.txt
glincker/theauth/docs/llms-full.txt
# theAuth documentation # theAuth Source: https://docs.theauth.dev/ **Auth for AI agents and for the humans
doanbactam/agent-skills-directory/public/llms.txt
machine learning tools - **Data & Analytics** — Data processing, analytics, and database tools - **Coding & Development** — Frontend, backend, and fullstack development - **Mobile** — iOS, Android, and cross-platform mobile development - **Automation & Agents** — CI/CD, workflows
jigarbhoye04/MatlabMCP/llms-full.txt
# Example Clients Source: https://modelcontextprotocol.io/clients A list of applications that support MCP integrations
me-public/nemus/docs/llms-full.txt
Nemus? Your product's code is probably split across **many separate Git repos** — frontend, backend, auth, payments, shared libraries. Working on one feature means cloning, pulling, branching, and testing each
me-public/nemus/docs/llms.txt
they were one project. Your product's code is split across many repos > (frontend, backend, auth, payments, shared libraries); Nemus pulls the repos you're > working on into a single
respeak-io/episko/site/llms.txt
third party. Built with Tauri v2 — a Rust backend with a vanilla-TypeScript frontend. ## Requirements - The `claude` CLI (Claude Code) installed and on your PATH, with your own Anthropic access
sandraschi/advanced-memory-mcp/llms-full.txt
FTS5) │ │ LanceDB (vector embeddings) │ │ Markdown files (human-readable) │ └──────────────────────────────────────┘ ↓ Webapp (port 10704/10705) ``` ## Ports | Service | Port | |---------|------| | Frontend (Vite React) | 10704 | | Backend (FastAPI + MCP HTTP) | 10705 | | MCP SSE transport | 10732 | ## MCP Tools
CLOUDWERX-DEV/gpt-image-1-mcp/.docs/llms-full.txt
# Example Clients Source: https://modelcontextprotocol.io/clients A list of applications that support MCP integrations
A markdown file at a website's root that gives language models a short guide to the site and links to the pages worth reading.
The same idea with the content included, so an agent can read the documentation in one request.
Agents and tools that fetch documentation on someone's behalf. It's a proposal, not a standard, and support varies.
Start with a one-line summary, then sections of links with a sentence each. The examples here show what real projects do.