How real projects summarise themselves for language models.
xu-xiangllms.txtxu-xiang/awesome-top-skills/llms.txt
test. Expects the full ticket context (title, description, comments) to be provided as input. frontend-design;anthropics/skills;main/skills/frontend-design;Create high-quality, production-ready frontend interfaces with distinct designs using React
racciolyllms.txtraccioly/docguard/llms-full.txt
Project file scanners for test discovery, route detection, schema mapping, CDK/IaC, doc-tools, integrations, frontend surface, spec-kit, memory-plan, semantic claims, agent readability | `cli/scanners/` | `*.mjs` | | **Writers** | Deterministic doc-mutation
AnastasiyaWllms.txtAnastasiyaW/knowledge-space/docs/llms.txt
processes at own pace). - [Microfrontends](https://happyin.space/architecture/microfrontends/): Microfrontends extend microservices principles to the frontend. Each micro-frontend is independently developed, tested, and deployed, aligned with a business domain. - [Microservices
tcsenpaillms.txttcsenpai/specification-website-skill/references/llms-full.txt
# The Website Specification > A platform-agnostic, full specification of the technical features a good
wundercorpllms.txtwundercorp/loki/llms-full.txt
# @wundercorp/loki > Loki Agent — a self-improving AI agent by WunderCorp, Inc. This Doku context
zircotellms.txtzircote/.claude/llms.txt
body #### Categories: - `01-core-development/` - Full-stack development (11 agents) - api-designer, backend-developer, frontend-developer, fullstack-developer - graphql-architect, microservices-architect, mobile-developer, ui-designer - electron-pro, websocket-engineer
sandraschillms.txtsandraschi/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
sandraschillms.txtsandraschi/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
sandraschillms.txtsandraschi/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
backenlyllms.txtbackenly/backenly/public/llms.txt
outcome to `backend_chat`. 4. Read it back, then `generate_types` for the frontend. ## Tools Exactly **23** tools are advertised; `tools/list` is the authority. Every tool except `backend_chat
CorpusIQllms.txtCorpusIQ/corpusiq-docs/llms-full.txt
# CorpusIQ Documentation — Full Content > Complete page content for LLM ingestion. Read-only access and
heymegabytellms.txtheymegabyte/claude-skills/llms-full.txt
skill set (category map · task routing · file hints) - [Skill Packs](_packs/README.md) — grouped bundles (core / frontend / backend / testing / design / …); one pack loads its whole graph - [Kernel](_kernel/index.md) — canonical shared definitions (WCAG
heymegabytellms.txtheymegabyte/claude-skills/llms.txt
skill set (category map · task routing · file hints) - [Skill Packs](_packs/README.md) — grouped bundles (core / frontend / backend / testing / design / …); one pack loads its whole graph - [Kernel](_kernel/index.md) — canonical shared definitions (WCAG
anthony-chaudharyllms.txtanthony-chaudhary/dos-kernel/llms-full.txt
# DOS — the Dispatch Operating System (dos-kernel) — llms-full.txt > The one-fetch expansion of llms.txt
kimyoungwopollms.txtkimyoungwopo/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
doanbactamllms.txtdoanbactam/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
jigarbhoye04llms.txtjigarbhoye04/MatlabMCP/llms-full.txt
# Example Clients Source: https://modelcontextprotocol.io/clients A list of applications that support MCP integrations
me-publicllms.txtme-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-publicllms.txtme-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
sandraschillms.txtsandraschi/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
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.
