Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 2 additions & 0 deletions _quarto.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ project:
type: posit-docs
render:
- "*.qmd"
resources:
- "llms.txt"

execute:
freeze: auto
Expand Down
56 changes: 56 additions & 0 deletions llms.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
# Positron
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AshleyHenry15 do you have any suggestions on best practices for this?

Copy link
Collaborator

@AshleyHenry15 AshleyHenry15 Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have one on the docs site that we are using already, and I was running it through evaluations to see if it was actually helping/successful or if it was actually making things worse.

This is something that I spoke with Joe C about a while back and since this type of thing is so new, it is hard to gauge the "right way" to write the txt file and measure its success. For example, I read that you actually have to tell the LLMs to look for the file for it it utilize the file. IDK if that is still the case but if it is, it is basically "useless" unless a user knows that it exists on the site.

I would recommend pausing this PR and look into running it through evals first.

Here is a link to our file: https://docs.posit.co/llms.txt

Do you want to have a quick meeting to chat about the evals?

(I actually have it on my backlog to test out what Stripe is doing with the button for "llm" and the markdown link to add on the docs site to see if it is beneficial enough to explore for product docs)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TY for the reply I'll add this as the agenda for our next sync! Will put this back into draft for now


Positron is developed by Posit PBC, the creators of RStudio. It provides a modern, extensible IDE built on Code OSS with features specifically designed for data science workflows, including notebooks, scripts, consoles, plotting, and data exploration tools.

## Key Features

- [Data Explorer](https://positron.posit.co/data-explorer): Interactive data exploration and visualization
- [Variables Pane](https://positron.posit.co/variables-pane): Inspect and debug variables in your session
- [Quarto Support](https://positron.posit.co/quarto): Easily create and publish Quarto documents from Positron
- [Jupyter Notebooks](https://positron.posit.co/jupyter-notebooks): Native notebook support
- [AI Assistant](https://positron.posit.co/assistant): Built-in AI Assistant for inline and chat assistance to streamline your data science workflows
- [Databot](https://positron.posit.co/databot): Databot is an experimental AI assistant designed to accelerate exploratory data analysis
- [Database Connections](https://positron.posit.co/connections-pane): Connect and explore databases
- [Remote Development](https://positron.posit.co/remote-ssh): Work on remote machines via SSH

## Getting Started

- [Download Positron](https://positron.posit.co/download): Get the latest version for macOS, Windows, or Linux
- [Installation Guide](https://positron.posit.co/install): Step-by-step installation instructions
- [Welcome Guide](https://positron.posit.co/welcome): First steps with Positron
- [Managing Interpreters](https://positron.posit.co/managing-interpreters): Set up Python and R interpreters
- [Python Setup](https://positron.posit.co/python-installations): Configure Python environments
- [R Setup](https://positron.posit.co/r-installations): Configure R installations

## Documentation

- [Features Overview](https://positron.posit.co/features): Complete feature list
- [Keyboard Shortcuts](https://positron.posit.co/keyboard-shortcuts): Essential keyboard commands
- [Extensions](https://positron.posit.co/extensions): Extend functionality with VSIX extensions
- [Extension Development](https://positron.posit.co/extension-development): Build custom extensions
- [Layout](https://positron.posit.co/layout): Customize the user interface
- [Command Palette](https://positron.posit.co/command-palette): Quick access to commands
- [Git Integration](https://positron.posit.co/git): Version control workflows

## Migration Guides

- [Migrate from VS Code](https://positron.posit.co/migrate-vscode): Transitioning from Visual Studio Code
- [Migrate from RStudio](https://positron.posit.co/migrate-rstudio): Comprehensive RStudio migration guide
- [RStudio Keybindings](https://positron.posit.co/migrate-rstudio-keybindings): Match your RStudio shortcuts
- [RStudio Settings & Extensions](https://positron.posit.co/migrate-rstudio-settings-and-extensions): Configure Positron like RStudio
- [R Projects](https://positron.posit.co/migrate-rstudio-rproj): Working with .Rproj files

## Support

- [Troubleshooting](https://positron.posit.co/troubleshooting): Common issues and solutions
- [FAQs](https://positron.posit.co/faqs): Frequently asked questions
- [Feedback](https://positron.posit.co/feedback): Report issues and request features
- [Privacy Policy](https://positron.posit.co/privacy): Data collection and privacy information
- [GitHub Repository](https://github.com/posit-dev/positron): View source code and contribute
- [Issue Tracker](https://github.com/posit-dev/positron/issues): Report bugs and request features

## About

- [About Positron](https://positron.posit.co/about): Project goals and philosophy
- [Licensing](https://positron.posit.co/licensing): Elastic License 2.0 information
- [Release Notes](https://positron.posit.co/release-notes): Latest updates and changes