{"owner":"rustdesk","repo":"rustdesk-server","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":308,"categories":["root-instruction","claude-rule"],"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.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","CLAUDE.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","CLAUDE.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","rawUrl":"https://raw.githubusercontent.com/rustdesk/rustdesk-server/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","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","isInternal":false,"tokens":154,"sizeBytes":754},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/rustdesk/rustdesk-server/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","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","isInternal":false,"tokens":154,"sizeBytes":754}],"systemPromptSnippet":"<yakaai_skills repo=\"rustdesk/rustdesk-server\">\n<!-- File: AGENTS.md (Tokens: ~154 | Category: root-instruction) -->\n# 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<!-- File: CLAUDE.md (Tokens: ~154 | Category: claude-rule) -->\n# 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</yakaai_skills>"}