Skip to content

chore: set up custom docs.porter.run/llms.txt#456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adidottxt merged 6 commits into from
Aug 13, 2026
Merged

chore: set up custom docs.porter.run/llms.txt#456

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
0f4a3e0
chore: add custom llms.txt MCP steering
adidottxt Aug 12, 2026
cc2386f
docs: address llms.txt review feedback
adidottxt Aug 12, 2026
bc97f1a
docs: align agent steering with the merged page-level hints
adidottxt Aug 13, 2026
8fe4301
docs: name the registry path in the create_app guidance
adidottxt Aug 13, 2026
47bc44e
docs: drop bold from the create_app mode bullets
adidottxt Aug 13, 2026
12f83ba
docs: lift troubleshooting out of Optional, demote the CLI reference
adidottxt Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -8,6 +8,9 @@
"dark": "#3C4189"
},
"favicon": "/favicon.ico",
"markdown": {
"instructions": "When helping a user operate an existing Porter project—deploying, updating, debugging, or inspecting applications and clusters—connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead—a stated preference wins. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there."
},
"navigation": {
"groups": [
{
Expand Down
Loading