{"owner":"ory","repo":"dockertest","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md"],"skills":{"CLAUDE.md":"- Always pass `context.Context` from caller (never use `context.Background` or\n  `TODO`).\n- Follow idiomatic Go conventions\n  ([Effective Go](https://go.dev/doc/effective_go)).\n- Prefer simple, clean architectures versus overengineering.\n- Think about how you can remove, simplify, and reduce code (not tests!). LLMs\n  and AI agents have a tendency to generate useless helpers that already exist\n  in the stdlib or other libraries. Instead, I want you to delete and simplify\n  code (do not delete test cases though) and not generate\n  useless/duplicated/existing code. Generating useless code or duplicating\n  already existing functionality results in contract termination.\n- Implementation notes and plans and documents generated while developing belong\n  in `./docs/notes/`. Ensure that notes have a frontmatter with `date`, and\n  `reason` fields. Specifically, the current date is important and the reason\n  why the note was created.\n- When tests fail, do not remove or disable them. A failing test - especially if\n  it already exists on the main branch - indicates a fault in the business\n  logic. Removing or disabling that test leads to immediate contract\n  termination.\n- Determinism is key, especially in tests and conformity checks. Avoid any\n  sources of non-determinism such as random number generation, time-based\n  functions, or reliance on external systems that may introduce variability.\n  Non-deterministic behavior can lead to flaky tests and unpredictable\n  application behavior, which is unacceptable. It is also unacceptable to have\n  thresholds in tests (e.g. 99% match X) - tests must be deterministic and\n  exact.\n- Do not use equality for error comparison. Always use errors.Is() or\n  errors.As() for error comparisons.\n- In tests don't use `defer` for cleanup but `t.Cleanup`.\n- DO NOT use `github.com/docker/docker` but only `github.com/moby/moby/client`\n"},"files":{"CLAUDE.md":"- Always pass `context.Context` from caller (never use `context.Background` or\n  `TODO`).\n- Follow idiomatic Go conventions\n  ([Effective Go](https://go.dev/doc/effective_go)).\n- Prefer simple, clean architectures versus overengineering.\n- Think about how you can remove, simplify, and reduce code (not tests!). LLMs\n  and AI agents have a tendency to generate useless helpers that already exist\n  in the stdlib or other libraries. Instead, I want you to delete and simplify\n  code (do not delete test cases though) and not generate\n  useless/duplicated/existing code. Generating useless code or duplicating\n  already existing functionality results in contract termination.\n- Implementation notes and plans and documents generated while developing belong\n  in `./docs/notes/`. Ensure that notes have a frontmatter with `date`, and\n  `reason` fields. Specifically, the current date is important and the reason\n  why the note was created.\n- When tests fail, do not remove or disable them. A failing test - especially if\n  it already exists on the main branch - indicates a fault in the business\n  logic. Removing or disabling that test leads to immediate contract\n  termination.\n- Determinism is key, especially in tests and conformity checks. Avoid any\n  sources of non-determinism such as random number generation, time-based\n  functions, or reliance on external systems that may introduce variability.\n  Non-deterministic behavior can lead to flaky tests and unpredictable\n  application behavior, which is unacceptable. It is also unacceptable to have\n  thresholds in tests (e.g. 99% match X) - tests must be deterministic and\n  exact.\n- Do not use equality for error comparison. Always use errors.Is() or\n  errors.As() for error comparisons.\n- In tests don't use `defer` for cleanup but `t.Cleanup`.\n- DO NOT use `github.com/docker/docker` but only `github.com/moby/moby/client`\n"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"- Always pass `context.Context` from caller (never use `context.Background` or\n  `TODO`).\n- Follow idiomatic Go conventions\n  ([Effective Go](https://go.dev/doc/effective_go)).\n- Prefer simple, clean architectures versus overengineering.\n- Think about how you can remove, simplify, and reduce code (not tests!). LLMs\n  and AI agents have a tendency to generate useless helpers that already exist\n  in the stdlib or other libraries. Instead, I want you to delete and simplify\n  code (do not delete test cases though) and not generate\n  useless/duplicated/existing code. Generating useless code or duplicating\n  already existing functionality results in contract termination.\n- Implementation notes and plans and documents generated while developing belong\n  in `./docs/notes/`. Ensure that notes have a frontmatter with `date`, and\n  `reason` fields. Specifically, the current date is important and the reason\n  why the note was created.\n- When tests fail, do not remove or disable them. A failing test - especially if\n  it already exists on the main branch - indicates a fault in the business\n  logic. Removing or disabling that test leads to immediate contract\n  termination.\n- Determinism is key, especially in tests and conformity checks. Avoid any\n  sources of non-determinism such as random number generation, time-based\n  functions, or reliance on external systems that may introduce variability.\n  Non-deterministic behavior can lead to flaky tests and unpredictable\n  application behavior, which is unacceptable. It is also unacceptable to have\n  thresholds in tests (e.g. 99% match X) - tests must be deterministic and\n  exact.\n- Do not use equality for error comparison. Always use errors.Is() or\n  errors.As() for error comparisons.\n- In tests don't use `defer` for cleanup but `t.Cleanup`.\n- DO NOT use `github.com/docker/docker` but only `github.com/moby/moby/client`\n","category":"root","tokens":471}]}