Aleksei Sviridkin c35cc848f0 docs(agents): widen overview.md routing and condense activation rules (#3373)
## What this PR does

`AGENTS.md` routes an agent to a documentation file based on how a
request is phrased. Two things were wrong with that routing.

The `overview.md` route listed only structural triggers — "where should
I put X", "what's the convention for Y", "how is the project organized".
Go, Helm chart and build/test work matched none of them, so an agent
asked to add a field to a CRD, fix a controller, add a value to a chart
or regenerate a values schema reached no documentation at all — even
though `overview.md` already covers every one of those under `Go Code`,
`Helm Charts`, `Values schema generation`, `Build and Development
Commands` and `Package Structure`. This widens the trigger phrases to
the work agents actually get asked to do and names the sections to land
in. No new documentation is added here: the content already existed, it
was just unreachable from the router.

The activation rule list spent seven bullets on three rules. Bullets 1
and 6 stated the same scope constraint, once positively and once
negatively; bullets 3, 4 and 5 each said "follow the documentation
exactly" in different words. Condensed to three bullets, with no
instruction dropped.

### Screenshots

Not a UI change.

### Downstream repositories

Walked the trigger map in `docs/agents/contributing.md` against the diff
rather than the title. The diff touches exactly one file, `AGENTS.md`,
and no trigger in the map matches it: nothing under `packages/apps/`,
`packages/extra/` or `packages/core/`, nothing under `hack/`, no
platform variant, no annotation or label value, no telemetry metric, and
no change to node or network requirements.

- [x] No downstream repository is affected by this change
- [ ] [cozystack/website](https://github.com/cozystack/website) -
follow-up:
- [ ]
[cozystack/terraform-provider-cozystack](https://github.com/cozystack/terraform-provider-cozystack)
- follow-up:
- [ ]
[cozystack/ansible-cozystack](https://github.com/cozystack/ansible-cozystack)
- follow-up:
- [ ] [cozystack/ccp](https://github.com/cozystack/ccp) - follow-up:
- [ ] [cozystack/talm](https://github.com/cozystack/talm) - follow-up:
- [ ] [cozystack/cozyhr](https://github.com/cozystack/cozyhr) -
follow-up:
- [ ] [cozystack/cozy-proxy](https://github.com/cozystack/cozy-proxy) -
follow-up:
- [ ]
[cozystack/cozystack-telemetry-server](https://github.com/cozystack/cozystack-telemetry-server)
- follow-up:
- [ ]
[cozystack/external-apps-example](https://github.com/cozystack/external-apps-example)
- follow-up:
- [ ] [cozystack/examples](https://github.com/cozystack/examples) -
follow-up:

### Release note

```release-note
NONE
```


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Updated guidance to direct questions about Go code, Helm charts, build
and test commands, and project structure to the relevant sections of the
project overview.
* Clarified that process documentation should be loaded before starting
tasks within its scope, followed without skipping steps, and used
alongside the overview as a standing reference.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-10-07 05:49:54 +03:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

GitHub Release Apache-2.0 License Commit activity OpenSSF Best Practices OpenSSF Scorecard CLOMonitor Support

Cozystack

Cozystack is a free and open-source platform and framework for building clouds.

Cozystack is a CNCF Sandbox project that was originally built and sponsored by Ænix.

With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.

Use Cozystack to build your own cloud or provide a cost-effective development environment.

Cozystack user interface

Use-Cases

Documentation

The documentation is located on the cozystack.io website.

Read the Getting Started section for a quick start.

If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.

Versioning

Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.

Contributions

Contributions are highly appreciated and very welcomed!

In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.

You are welcome to take on the fix yourself. Commits are used to generate the changelog, and their author will be referenced in it.

If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.

Community

You are welcome to join us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.

Project documents

Document What it covers
Governance How decisions are made and who makes them
Contributor Ladder How to grow from contributor to maintainer
Maintainers Who maintains the project
Code of Conduct What we expect of each other
Security Policy Reporting a vulnerability, and which releases get fixes
Adopters Who runs Cozystack in production
Roadmap Where the project is going

License

Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.

Commercial Support

A list of companies providing commercial support for this project can be found on official site.

Languages
Go 52%
Shell 34%
TypeScript 6.8%
Go Template 4.7%
Makefile 1.3%
Other 1.1%