{"owner":"rustdesk","repo":"rustdesk-server","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Instructions\n\n## Rust Rules\n\n- In Rust code, do not introduce `unwrap()` or `expect()`.\n- Allowed exceptions:\n- Tests may use `unwrap()` or `expect()` when it keeps the test focused and readable.\n- Lock acquisition may use `unwrap()` only when the locking API makes that the practical option and the failure mode is poison handling rather than normal control flow.\n- Outside those exceptions, propagate errors, handle them explicitly, or use safer fallbacks instead of `unwrap()` and `expect()`.\n\n## Editing Hygiene\n\n- Do not introduce formatting-only changes.\n- Do not run repository-wide formatters or reflow unrelated code unless the\n  user explicitly asks for formatting.\n- Keep diffs limited to semantic changes required for the task.\n\n"},"files":{"AGENTS.md":"# Repository Instructions\n\n## Rust Rules\n\n- In Rust code, do not introduce `unwrap()` or `expect()`.\n- Allowed exceptions:\n- Tests may use `unwrap()` or `expect()` when it keeps the test focused and readable.\n- Lock acquisition may use `unwrap()` only when the locking API makes that the practical option and the failure mode is poison handling rather than normal control flow.\n- Outside those exceptions, propagate errors, handle them explicitly, or use safer fallbacks instead of `unwrap()` and `expect()`.\n\n## Editing Hygiene\n\n- Do not introduce formatting-only changes.\n- Do not run repository-wide formatters or reflow unrelated code unless the\n  user explicitly asks for formatting.\n- Keep diffs limited to semantic changes required for the task.\n\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Instructions\n\n## Rust Rules\n\n- In Rust code, do not introduce `unwrap()` or `expect()`.\n- Allowed exceptions:\n- Tests may use `unwrap()` or `expect()` when it keeps the test focused and readable.\n- Lock acquisition may use `unwrap()` only when the locking API makes that the practical option and the failure mode is poison handling rather than normal control flow.\n- Outside those exceptions, propagate errors, handle them explicitly, or use safer fallbacks instead of `unwrap()` and `expect()`.\n\n## Editing Hygiene\n\n- Do not introduce formatting-only changes.\n- Do not run repository-wide formatters or reflow unrelated code unless the\n  user explicitly asks for formatting.\n- Keep diffs limited to semantic changes required for the task.\n\n","category":"root","tokens":189}]}