{"owner":"lima-vm","repo":"lima","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\nGuidance for AI coding agents working in the Lima repository. It points to the authoritative docs\ninstead of duplicating them, so it stays in sync with the code.\n\n## AI contribution rules\n\nRead @website/content/en/docs/community/contributing.md and follow its \"AI Contribution Rules\"\nsection.\n\n## Build, test, lint\n\nLima is `github.com/lima-vm/lima/v2` (imports use the `/v2` suffix). The build\nuses a GNU Makefile; output goes to `_output/`.\n\n```bash\nmake native        # build limactl + native guestagent + templates (fastest full dev build)\nmake minimal       # build just limactl + native guestagent + default template\ngo test ./...      # unit tests - never boot VMs\nmake bats          # integration tests (BATS); boot real VMs (needs git submodules)\nmake lint          # editorconfig, golangci-lint, yamllint, ls-lint, shellcheck, ltag, ...\nmake generate      # regenerate protobuf after editing a .proto file\n```\n\nUnit tests never execute VMs; anything that boots a VM is a BATS or template test under `hack/`\n(for example `./hack/test-templates.sh ./templates/default.yaml`). Every commit must be signed off\nwith `git commit -s`, or CI fails.\n\n## Where things are\n\nPointers to the authoritative sources - read these rather than a duplicated copy here.\n\n- Architecture, the three processes (`limactl` / hostagent / guestagent), the on-disk `${LIMA_HOME}`\n  layout, and every `LIMA_CIDATA_*` variable:\n  [`website/content/en/docs/dev/internals.md`](website/content/en/docs/dev/internals.md).\n- Config / data model: `pkg/limatype` (core `LimaYAML` / `Instance` types), `pkg/limayaml`\n  (load / default / validate), `pkg/limatmpl` and `pkg/templatestore` (templates).\n- Drivers (virtualization backends): `pkg/driver/`\n- Guest provisioning: `pkg/cidata/` builds `cidata.iso` (guestagent binary, boot scripts, and the\n  `user-data` file). `user-data` uses the cloud-config YAML format defined by cloud-init, which a\n  guest may consume with an implementation other than Python cloud-init.\n- Instance lifecycle: `pkg/instance/`.\n\n## Conventions\n\n- New Go, shell, Dockerfile, and Makefile files need an SPDX header (`ltag` enforces this in CI;\n  other file types, including markdown, are exempt).\n- Keep the `gomodjail` / `gosocialcheck` annotations in `go.mod`.\n","CLAUDE.md":"# CLAUDE.md\n\n@AGENTS.md\n\n`AGENTS.md` is the shared guidance for AI coding agents in this repository; the `@` line above makes\nthe harness load it. Personal, machine-local overrides may live in `CLAUDE.local.md` (gitignored).\n"},"files":{"AGENTS.md":"# AGENTS.md\n\nGuidance for AI coding agents working in the Lima repository. It points to the authoritative docs\ninstead of duplicating them, so it stays in sync with the code.\n\n## AI contribution rules\n\nRead @website/content/en/docs/community/contributing.md and follow its \"AI Contribution Rules\"\nsection.\n\n## Build, test, lint\n\nLima is `github.com/lima-vm/lima/v2` (imports use the `/v2` suffix). The build\nuses a GNU Makefile; output goes to `_output/`.\n\n```bash\nmake native        # build limactl + native guestagent + templates (fastest full dev build)\nmake minimal       # build just limactl + native guestagent + default template\ngo test ./...      # unit tests - never boot VMs\nmake bats          # integration tests (BATS); boot real VMs (needs git submodules)\nmake lint          # editorconfig, golangci-lint, yamllint, ls-lint, shellcheck, ltag, ...\nmake generate      # regenerate protobuf after editing a .proto file\n```\n\nUnit tests never execute VMs; anything that boots a VM is a BATS or template test under `hack/`\n(for example `./hack/test-templates.sh ./templates/default.yaml`). Every commit must be signed off\nwith `git commit -s`, or CI fails.\n\n## Where things are\n\nPointers to the authoritative sources - read these rather than a duplicated copy here.\n\n- Architecture, the three processes (`limactl` / hostagent / guestagent), the on-disk `${LIMA_HOME}`\n  layout, and every `LIMA_CIDATA_*` variable:\n  [`website/content/en/docs/dev/internals.md`](website/content/en/docs/dev/internals.md).\n- Config / data model: `pkg/limatype` (core `LimaYAML` / `Instance` types), `pkg/limayaml`\n  (load / default / validate), `pkg/limatmpl` and `pkg/templatestore` (templates).\n- Drivers (virtualization backends): `pkg/driver/`\n- Guest provisioning: `pkg/cidata/` builds `cidata.iso` (guestagent binary, boot scripts, and the\n  `user-data` file). `user-data` uses the cloud-config YAML format defined by cloud-init, which a\n  guest may consume with an implementation other than Python cloud-init.\n- Instance lifecycle: `pkg/instance/`.\n\n## Conventions\n\n- New Go, shell, Dockerfile, and Makefile files need an SPDX header (`ltag` enforces this in CI;\n  other file types, including markdown, are exempt).\n- Keep the `gomodjail` / `gosocialcheck` annotations in `go.mod`.\n","CLAUDE.md":"# CLAUDE.md\n\n@AGENTS.md\n\n`AGENTS.md` is the shared guidance for AI coding agents in this repository; the `@` line above makes\nthe harness load it. Personal, machine-local overrides may live in `CLAUDE.local.md` (gitignored).\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\nGuidance for AI coding agents working in the Lima repository. It points to the authoritative docs\ninstead of duplicating them, so it stays in sync with the code.\n\n## AI contribution rules\n\nRead @website/content/en/docs/community/contributing.md and follow its \"AI Contribution Rules\"\nsection.\n\n## Build, test, lint\n\nLima is `github.com/lima-vm/lima/v2` (imports use the `/v2` suffix). The build\nuses a GNU Makefile; output goes to `_output/`.\n\n```bash\nmake native        # build limactl + native guestagent + templates (fastest full dev build)\nmake minimal       # build just limactl + native guestagent + default template\ngo test ./...      # unit tests - never boot VMs\nmake bats          # integration tests (BATS); boot real VMs (needs git submodules)\nmake lint          # editorconfig, golangci-lint, yamllint, ls-lint, shellcheck, ltag, ...\nmake generate      # regenerate protobuf after editing a .proto file\n```\n\nUnit tests never execute VMs; anything that boots a VM is a BATS or template test under `hack/`\n(for example `./hack/test-templates.sh ./templates/default.yaml`). Every commit must be signed off\nwith `git commit -s`, or CI fails.\n\n## Where things are\n\nPointers to the authoritative sources - read these rather than a duplicated copy here.\n\n- Architecture, the three processes (`limactl` / hostagent / guestagent), the on-disk `${LIMA_HOME}`\n  layout, and every `LIMA_CIDATA_*` variable:\n  [`website/content/en/docs/dev/internals.md`](website/content/en/docs/dev/internals.md).\n- Config / data model: `pkg/limatype` (core `LimaYAML` / `Instance` types), `pkg/limayaml`\n  (load / default / validate), `pkg/limatmpl` and `pkg/templatestore` (templates).\n- Drivers (virtualization backends): `pkg/driver/`\n- Guest provisioning: `pkg/cidata/` builds `cidata.iso` (guestagent binary, boot scripts, and the\n  `user-data` file). `user-data` uses the cloud-config YAML format defined by cloud-init, which a\n  guest may consume with an implementation other than Python cloud-init.\n- Instance lifecycle: `pkg/instance/`.\n\n## Conventions\n\n- New Go, shell, Dockerfile, and Makefile files need an SPDX header (`ltag` enforces this in CI;\n  other file types, including markdown, are exempt).\n- Keep the `gomodjail` / `gosocialcheck` annotations in `go.mod`.\n","category":"root","tokens":570},{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# CLAUDE.md\n\n@AGENTS.md\n\n`AGENTS.md` is the shared guidance for AI coding agents in this repository; the `@` line above makes\nthe harness load it. Personal, machine-local overrides may live in `CLAUDE.local.md` (gitignored).\n","category":"root","tokens":57}]}