chore: generate initial coder-docs skill snapshot

Snapshot from coder/coder@342d2e4bedf6 (2026-02-10).
Text-only docs (~4.5MB), 415 routes in the docs tree.

Author: ThomasK33

.mux/skills/coder-docs/SKILL.md

@@ -0,0 +1,146 @@
+# About
+
+<!-- Warning for docs contributors: The first route in manifest.json must be titled "About" for the static landing page to work correctly. -->
+
+Coder is a self-hosted, open source, cloud development environment that works
+with any cloud, IDE, OS, Git provider, and IDP.
+
+![Screenshots of Coder workspaces and connections](./images/hero-image.png)_Screenshots of Coder workspaces and connections_
+
+Coder is built on common development interfaces and infrastructure tools to
+make the process of provisioning and accessing remote workspaces approachable
+for organizations of various sizes and stages of cloud-native maturity.
+
+## IDE support
+
+![IDE icons](./images/ide-icons.svg)
+
+You can use:
+
+- Any Web IDE, such as
+
+  - [code-server](https://github.com/coder/code-server)
+  - [JetBrains Projector](https://github.com/JetBrains/projector-server)
+  - [Jupyter](https://jupyter.org/)
+  - And others
+
+- Your existing remote development environment:
+
+  - [JetBrains Gateway](https://www.jetbrains.com/remote-development/gateway/)
+  - [VS Code Remote](https://code.visualstudio.com/docs/remote/ssh-tutorial)
+  - [Emacs](./user-guides/workspace-access/emacs-tramp.md)
+
+- A file sync such as [Mutagen](https://mutagen.io/)
+
+## Why remote development
+
+Remote development offers several benefits for users and administrators, including:
+
+- **Increased speed**
+
+  - Server-grade cloud hardware speeds up operations in software development, from
+    loading the IDE to compiling and building code, and running large workloads
+    such as those for monolith or microservice applications.
+
+- **Easier environment management**
+
+  - Built-in infrastructure tools such as Terraform, nix, Docker, Dev Containers, and others make it easier to onboard developers with consistent environments.
+
+- **Increased security**
+
+  - Centralize source code and other data onto private servers or cloud services instead of local developers' machines.
+  - Manage users and groups with [SSO](./admin/users/oidc-auth/index.md) and [Role-based access controlled (RBAC)](./admin/users/groups-roles.md#roles).
+
+- **Improved compatibility**
+
+  - Remote workspaces can share infrastructure configurations with other
+    development, staging, and production environments, reducing configuration
+    drift.
+
+- **Improved accessibility**
+  - Connect to remote workspaces via browser-based IDEs or remote IDE
+    extensions to enable developers regardless of the device they use, whether
+    it's their main device, a lightweight laptop, Chromebook, or iPad.
+
+Read more about why organizations and engineers are moving to remote
+development on [our blog](https://coder.com/blog), the
+[Slack engineering blog](https://slack.engineering/development-environments-at-slack),
+or from [OpenFaaS's Alex Ellis](https://blog.alexellis.io/the-internet-is-my-computer/).
+
+## Why Coder
+
+The key difference between Coder and other remote IDE platforms is the added
+layer of infrastructure control.
+This additional layer allows admins to:
+
+- Simultaneously support ARM, Windows, Linux, and macOS workspaces.
+- Modify pod/container specs, such as adding disks, managing network policies, or
+  setting/updating environment variables.
+- Use VM or dedicated workspaces, developing with Kernel features (no container
+  knowledge required).
+- Enable persistent workspaces, which are like local machines, but faster and
+  hosted by a cloud service.
+
+## How much does it cost?
+
+Coder is free and open source under
+[GNU Affero General Public License v3.0](https://github.com/coder/coder/blob/main/LICENSE).
+All developer productivity features are included in the Open Source version of
+Coder.
+A [Premium license is available](https://coder.com/pricing#compare-plans) for enhanced
+support options and custom deployments.
+
+## How does Coder work
+
+Coder workspaces are represented with Terraform, but you don't need to know
+Terraform to get started.
+We have a [database of production-ready templates](https://registry.coder.com/templates)
+for use with AWS EC2, Azure, Google Cloud, Kubernetes, and more.
+
+![Providers and compute environments](./images/providers-compute.png)_Providers and compute environments_
+
+Coder workspaces can be used for more than just compute.
+You can use Terraform to add storage buckets, secrets, sidecars,
+[and more](https://developer.hashicorp.com/terraform/tutorials).
+
+Visit the [templates documentation](./admin/templates/index.md) to learn more.
+
+## What Coder is not
+
+- Coder is not an infrastructure as code (IaC) platform.
+
+  - Terraform is the first IaC _provisioner_ in Coder, allowing Coder admins to
+    define Terraform resources as Coder workspaces.
+
+- Coder is not a DevOps/CI platform.
+
+  - Coder workspaces can be configured to follow best practices for
+    cloud-service-based workloads, but Coder is not responsible for how you
+    define or deploy the software you write.
+
+- Coder is not an online IDE.
+
+  - Coder supports common editors, such as VS Code, vim, and JetBrains,
+    all over HTTPS or SSH.
+
+- Coder is not a collaboration platform.
+
+  - You can use Git with your favorite Git platform and dedicated IDE
+    extensions for pull requests, code reviews, and pair programming.
+
+- Coder is not a SaaS/fully-managed offering.
+  - Coder is a [self-hosted](<https://en.wikipedia.org/wiki/Self-hosting_(web_services)>)
+    solution.
+    You must host Coder in a private data center or on a cloud service, such as
+    AWS, Azure, or GCP.
+
+## Using Coder v1?
+
+If you're a Coder v1 customer, view [the v1 documentation](https://coder.com/docs/v1)
+or [the v2 migration guide and FAQ](https://coder.com/docs/v1/guides/v2-faq).
+
+## Up next
+
+- [Template](./admin/templates/index.md)
+- [Installing Coder](./install/index.md)
+- [Quickstart](./tutorials/quickstart.md) to try Coder out for yourself.

.mux/skills/coder-docs/references/docs/README.md

@@ -0,0 +1,5 @@
+{
+  "upstream_repo": "coder/coder",
+  "upstream_sha": "342d2e4bedf60b7d73bf11310e290871986ca874",
+  "generated_at": "2026-02-10T08:17:11Z"
+}

.mux/skills/coder-docs/references/docs/SNAPSHOT.json

@@ -0,0 +1,32 @@
+# AI Contribution Guidelines
+
+This document defines rules for contributions where an AI system is the primary author of the code (i.e., most of the pull request was generated by AI).
+It applies to all Coder repositories and is a supplement to the [existing contributing guidelines](./CONTRIBUTING.md), not a replacement.
+
+For minor AI-assisted edits, suggestions, or completions where the human contributor is clearly the primary author, these rules do not apply — standard contributing guidelines are sufficient.
+
+## Disclosure
+
+Contributors must **disclose AI involvement** in the pull request description whenever these guidelines apply.
+
+## Human Ownership & Attribution
+
+- All pull requests must be opened under **user accounts linked to a human**, and not an application ("bot account").
+- Contributors are personally accountable for the content of their PRs, regardless of how it was generated.
+
+## Verification & Evidence
+
+All AI-assisted contributions require **manual verification**.
+Contributions without verification evidence will be rejected.
+
+- Test your changes yourself. Don’t assume AI is correct.
+- Provide screenshots showing that the change works as intended.
+  - For visual/UI changes: include before/after screenshots.
+  - For CLI or backend changes: include terminal or api output.
+
+## Why These Rules Exist
+
+Traditionally, maintainers assumed that producing a pull request required more effort than reviewing it.
+With AI-assisted tools, the balance has shifted: generating code is often faster than reviewing it.
+
+Our guidelines exist to safeguard maintainers’ time, uphold contributor accountability, and preserve the overall quality of the project.

.mux/skills/coder-docs/references/docs/about/contributing/AI_CONTRIBUTING.md

@@ -0,0 +1,77 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality,
+personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <opensource@coder.com>. All complaints
+will be reviewed and investigated and will result in a response that is deemed
+necessary and appropriate to the circumstances. The project team is obligated to
+maintain confidentiality with regard to the reporter of an incident. Further
+details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+<https://www.contributor-covenant.org/faq>