{"owner":"lima-vm","repo":"lima","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":735,"categories":["claude-rule","root-instruction"],"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md","AGENTS.md"],"skills":{"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","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`. `make gomodjail` statically\n  verifies that the modules annotated `gomodjail:confined` cannot reach a denied capability\n  (filesystem, network, process execution, raw syscalls, ...); when a dependency bump makes one\n  of them reach a capability, `make gomodjail-fix` downgrades that annotation to\n  `gomodjail:unconfined` instead of confining it by hand.\n"},"files":{"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","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`. `make gomodjail` statically\n  verifies that the modules annotated `gomodjail:confined` cannot reach a denied capability\n  (filesystem, network, process execution, raw syscalls, ...); when a dependency bump makes one\n  of them reach a capability, `make gomodjail-fix` downgrades that annotation to\n  `gomodjail:unconfined` instead of confining it by hand.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/lima-vm/lima/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","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`. `make gomodjail` statically\n  verifies that the modules annotated `gomodjail:confined` cannot reach a denied capability\n  (filesystem, network, process execution, raw syscalls, ...); when a dependency bump makes one\n  of them reach a capability, `make gomodjail-fix` downgrades that annotation to\n  `gomodjail:unconfined` instead of confining it by hand.\n","isInternal":false,"tokens":675,"sizeBytes":2632},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/lima-vm/lima/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","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","isInternal":false,"tokens":60,"sizeBytes":225}],"systemPromptSnippet":"<yakaai_skills repo=\"lima-vm/lima\">\n<!-- File: AGENTS.md (Tokens: ~675 | Category: root-instruction) -->\n# 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`. `make gomodjail` statically\n  verifies that the modules annotated `gomodjail:confined` cannot reach a denied capability\n  (filesystem, network, process execution, raw syscalls, ...); when a dependency bump makes one\n  of them reach a capability, `make gomodjail-fix` downgrades that annotation to\n  `gomodjail:unconfined` instead of confining it by hand.\n\n<!-- File: CLAUDE.md (Tokens: ~60 | Category: claude-rule) -->\n# 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</yakaai_skills>"}