[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFGY8DSHNQ7QEBZZCDCX7E":3,"skill-same:01M7DFGY8DSHNQ7QEBZZCDCX7E":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M7DFGY8DSHNQ7QEBZZCDCX7E","apple-container",null,"Build, run, and manage OCI\u002FLinux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: apple-container\ndescription: \"Build, run, and manage OCI\u002FLinux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.\"\ncategory: devops\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fsanjay3290\u002Fai-skills\u002Ftree\u002Fmain\u002Fskills\u002Fapple-container\nsource_repo: sanjay3290\u002Fai-skills\nsource_type: community\ndate_added: \"2026-07-09\"\nauthor: sanjay3290\ntags: [macos, containers, oci, apple-silicon]\ntools: [claude, cursor, gemini]\nlicense: \"Apache-2.0\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fsanjay3290\u002Fai-skills\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Apple `container`\n\n## When to Use\n\n- Use when building, running, or managing OCI\u002FLinux containers on Apple-silicon macOS with Apple's open-source `container` CLI\n- Use when you want lightweight per-container VMs instead of a Docker daemon\n- Use when translating Docker-style workflows (build, run, exec, logs, networking) to Apple's container tooling\n\nApple's `container` is an open-source CLI for building, running, and managing OCI\u002FLinux\ncontainers on Apple-silicon Macs. Each container runs inside its own lightweight virtual\nmachine (backed by the Containerization framework and the Virtualization API), so there is no\nshared daemon like Docker — services run per-user via `launchd`. Images are standard OCI\nartifacts, so they interoperate with Docker registries and other OCI tooling. The CLI is\ndeliberately Docker-like (`container run`, `container build`, and image ops under\n`container image push`\u002F`pull`), but it is a distinct tool: do not assume Docker command paths,\nflags, defaults, or daemon behavior carry over (e.g. there is no `container images`\u002F`push`\u002F`pull`\ntop-level command — image verbs live under `container image`).\n\n## Safety Gate\n\nContainer installation, service startup, image pulls, builds, runs, registry login, pushes,\nand resource cleanup change local or remote state. Explain the exact command, image registry,\nmounts, ports, privileges, and data-persistence impact, then obtain explicit user approval\nbefore executing it. Do not provide registry credentials, mount sensitive paths, or expose\nports without the user's explicit instruction.\n\n## Requirements\n\n- **Apple silicon only** (M1 or later). Intel Macs are not supported.\n- **macOS 26 (Tahoe) is the officially supported target.** The maintainers do not support\n  older macOS and typically will not fix issues that can't be reproduced on 26. The binary\n  still runs on **macOS 15 (Sequoia)** but with reduced networking: only the single default\n  subnet is available, and the `container network` group and `--network` flag error out.\n  macOS-26-gated features are called out throughout the reference files.\n- **Version:** this skill documents the **1.0.0** release (the fullest feature set). The `machine`\n  group, `container cp`, `container export`, `container prune`, `container image prune`,\n  `container registry list`, and `container system version` were **added in 1.0.0** (not in 0.7.1)\n  — features that postdate 0.7.1 are flagged *(1.0.0+)* in the reference files. Run `container --version` and\n  `container \u003Cgroup> --help` to see what your installed build supports.\n- Install by downloading the signed `.pkg` installer from the project's GitHub releases\n  (`apple\u002Fcontainer`) and running it. See `references\u002Fconcepts.md` for the full\n  requirements\u002Fcompatibility matrix and how the VM-per-container model works.\n\n## Setup\n\nInstall the signed package, then start the background services once:\n\n1. **Download** the latest signed installer `.pkg` from the\n   [GitHub releases page](https:\u002F\u002Fgithub.com\u002Fapple\u002Fcontainer\u002Freleases).\n2. **Double-click** the downloaded package and follow the prompts, entering your admin\n   password so it can place files under `\u002Fusr\u002Flocal`. (There is no documented CLI `installer`\n   invocation — installation is via the GUI package.)\n3. **Start the services** and confirm they are healthy:\n\n```bash\n# Start the container services (container-apiserver + helpers via launchd). On first run it\n# offers to install the default Linux kernel — accept it, or start non-interactively with\n# `--disable-kernel-install` and add a kernel later via `container system kernel set`.\ncontainer system start\n\n# Verify services are healthy\ncontainer system status\n```\n\n`container system start` must have run before any container\u002Fimage\u002Fbuild command works — a\nconnection\u002FXPC error almost always means the services are stopped, so run it again. Stop and\nderegister the `launchd` services with `container system stop` (which takes only `-p\u002F--prefix`).\nThe startup flags for `container system start` (`-a\u002F--app-root`, `--install-root`, `--log-root`,\n`--enable-kernel-install`\u002F`--disable-kernel-install`, `--timeout`) are in\n`references\u002Fconfiguration.md`.\n\n**Upgrade \u002F downgrade \u002F uninstall** use helper scripts in `\u002Fusr\u002Flocal\u002Fbin` (stop first with\n`container system stop`): `update-container.sh` (add `-v \u003Cversion>` to pin a version), and\n`uninstall-container.sh -d` to remove user data or `-k` to keep it. Full recipes in\n`references\u002Fworkflows.md`.\n\n## Command groups at a glance\n\nInvoke everything as `container \u003Cgroup> \u003Csubcommand>`. Container-lifecycle verbs (`run`,\n`create`, `start`, `stop`, `exec`, `logs`, `inspect`, `list`\u002F`ls`, `delete`\u002F`rm`, `kill`,\n`stats`) and `build` are top-level; image operations like `push`, `pull`, and `tag` live\nunder `container image`. Run `container \u003Cgroup> --help` for exact flags, or read\n`references\u002Fcommands.md` for the exhaustive matrix.\n\n| Group | What it does | Example |\n|-------|--------------|---------|\n| container lifecycle | Create, start, run, stop, exec, inspect, list, remove containers | `container run --rm -it docker.io\u002Flibrary\u002Falpine sh` |\n| build | Build an OCI image from a Dockerfile in the builder VM | `container build -t myapp:latest .` |\n| image | List, tag, inspect, remove, load\u002Fsave, prune local images; push\u002Fpull to registries | `container image ls` |\n| registry | Authenticate (login\u002Flogout\u002Flist) to OCI registries | `container registry login ghcr.io` |\n| system | Start\u002Fstop\u002Fstatus services, logs, disk usage (`df`), DNS, kernel, properties | `container system status` |\n| network | Create\u002Flist\u002Fremove container networks (**macOS 26 only**) | `container network create mynet` |\n| volume | Create\u002Flist\u002Finspect\u002Fremove persistent volumes | `container volume create data` |\n| builder | Manage the builder VM that runs `container build` (start\u002Fstop\u002Fstatus) | `container builder status` |\n| machine *(1.0.0+)* | Persistent Linux \"machine\" environments (added in 1.0.0) | `container machine --help` |\n\nExact subcommand names, aliases, arguments, and flags for each group live in\n`references\u002Fcommands.md` — consult it before running an unfamiliar command rather than\nguessing Docker-equivalent syntax.\n\n## Navigating this skill\n\nRead the reference file that matches the task; do not guess flags or behavior.\n\n- **`references\u002Fcommands.md`** — exhaustive CLI reference: every command group, subcommand,\n  alias, argument, and flag. Read this to construct any concrete `container ...` invocation,\n  or to confirm a flag exists before using it.\n- **`references\u002Fconcepts.md`** — architecture (VM-per-container, Containerization framework),\n  system requirements and macOS 15 vs 26 differences, networking model, per-container IPs,\n  security model, and a Docker-vs-`container` comparison. Read this to explain how or why\n  something works, or when a Docker mental model gives the wrong answer.\n- **`references\u002Fconfiguration.md`** — the system service, `config.toml` \u002F property model,\n  default kernel, DNS domains, default registry, builder resources, and machine settings.\n  Read this to change defaults, tune CPU\u002Fmemory, point at a private registry, or manage the\n  kernel.\n- **`references\u002Fworkflows.md`** — copy-pasteable task recipes (run an image, build & push,\n  wire up local DNS, mount a volume, expose ports) and troubleshooting for common failures.\n  Read this first when the user wants to accomplish a concrete end-to-end task.\n\n## Key rules\n\n- **This is not Docker.** The CLI resembles Docker, but flags, defaults, and daemon behavior\n  differ. Verify syntax in `references\u002Fcommands.md` instead of assuming Docker equivalence.\n- **Always ensure services are up first.** Run `container system start` (and confirm with\n  `container system status`) before any container\u002Fimage\u002Fbuild command; connection errors\n  usually mean the services are stopped.\n- **Images are standard OCI artifacts** and interoperate with Docker registries and other OCI\n  tools. Image references that omit a registry default to `docker.io` (configurable via the\n  `registry.domain` property — see `references\u002Fconfiguration.md`).\n- **Each container gets its own IP address** on its network (one lightweight VM per\n  container). There is no shared Docker bridge; reach a container directly by its IP, or set\n  up a local DNS domain (`container system dns create ...`, admin required) for name-based\n  access.\n- **`container network` requires macOS 26.** On macOS 15 only the single default subnet is\n  available and the network command group is unavailable — see `references\u002Fconcepts.md`.\n- **Use fully-qualified image references** when precision matters (e.g.\n  `docker.io\u002Flibrary\u002Falpine` rather than bare `alpine`) to avoid ambiguity about the source\n  registry.\n\n## Limitations\n\n- Apple Container requires Apple silicon and has materially different support and networking\n  behavior across macOS releases; verify the installed CLI version before relying on a flag.\n- OCI images and registry content are third-party inputs. Inspect and trust the image source\n  before pulling or running it.\n- This skill does not make container workloads safe by default: mounts, published ports,\n  privileged settings, registry credentials, and cleanup can expose or destroy data.\n- Stop before uninstalling, pruning, deleting containers, volumes, or images, and require\n  explicit approval for each destructive action.\n","# Apple `container`\n\n## When to Use\n\n- Use when building, running, or managing OCI\u002FLinux containers on Apple-silicon macOS with Apple's open-source `container` CLI\n- Use when you want lightweight per-container VMs instead of a Docker daemon\n- Use when translating Docker-style workflows (build, run, exec, logs, networking) to Apple's container tooling\n\nApple's `container` is an open-source CLI for building, running, and managing OCI\u002FLinux\ncontainers on Apple-silicon Macs. Each container runs inside its own lightweight virtual\nmachine (backed by the Containerization framework and the Virtualization API), so there is no\nshared daemon like Docker — services run per-user via `launchd`. Images are standard OCI\nartifacts, so they interoperate with Docker registries and other OCI tooling. The CLI is\ndeliberately Docker-like (`container run`, `container build`, and image ops under\n`container image push`\u002F`pull`), but it is a distinct tool: do not assume Docker command paths,\nflags, defaults, or daemon behavior carry over (e.g. there is no `container images`\u002F`push`\u002F`pull`\ntop-level command — image verbs live under `container image`).\n\n## Safety Gate\n\nContainer installation, service startup, image pulls, builds, runs, registry login, pushes,\nand resource cleanup change local or remote state. Explain the exact command, image registry,\nmounts, ports, privileges, and data-persistence impact, then obtain explicit user approval\nbefore executing it. Do not provide registry credentials, mount sensitive paths, or expose\nports without the user's explicit instruction.\n\n## Requirements\n\n- **Apple silicon only** (M1 or later). Intel Macs are not supported.\n- **macOS 26 (Tahoe) is the officially supported target.** The maintainers do not support\n  older macOS and typically will not fix issues that can't be reproduced on 26. The binary\n  still runs on **macOS 15 (Sequoia)** but with reduced networking: only the single default\n  subnet is available, and the `container network` group and `--network` flag error out.\n  macOS-26-gated features are called out throughout the reference files.\n- **Version:** this skill documents the **1.0.0** release (the fullest feature set). The `machine`\n  group, `container cp`, `container export`, `container prune`, `container image prune`,\n  `container registry list`, and `container system version` were **added in 1.0.0** (not in 0.7.1)\n  — features that postdate 0.7.1 are flagged *(1.0.0+)* in the reference files. Run `container --version` and\n  `container \u003Cgroup> --help` to see what your installed build supports.\n- Install by downloading the signed `.pkg` installer from the project's GitHub releases\n  (`apple\u002Fcontainer`) and running it. See `references\u002Fconcepts.md` for the full\n  requirements\u002Fcompatibility matrix and how the VM-per-container model works.\n\n## Setup\n\nInstall the signed package, then start the background services once:\n\n1. **Download** the latest signed installer `.pkg` from the\n   [GitHub releases page](https:\u002F\u002Fgithub.com\u002Fapple\u002Fcontainer\u002Freleases).\n2. **Double-click** the downloaded package and follow the prompts, entering your admin\n   password so it can place files under `\u002Fusr\u002Flocal`. (There is no documented CLI `installer`\n   invocation — installation is via the GUI package.)\n3. **Start the services** and confirm they are healthy:\n\n```bash\n# Start the container services (container-apiserver + helpers via launchd). On first run it\n# offers to install the default Linux kernel — accept it, or start non-interactively with\n# `--disable-kernel-install` and add a kernel later via `container system kernel set`.\ncontainer system start\n\n# Verify services are healthy\ncontainer system status\n```\n\n`container system start` must have run before any container\u002Fimage\u002Fbuild command works — a\nconnection\u002FXPC error almost always means the services are stopped, so run it again. Stop and\nderegister the `launchd` services with `container system stop` (which takes only `-p\u002F--prefix`).\nThe startup flags for `container system start` (`-a\u002F--app-root`, `--install-root`, `--log-root`,\n`--enable-kernel-install`\u002F`--disable-kernel-install`, `--timeout`) are in\n`references\u002Fconfiguration.md`.\n\n**Upgrade \u002F downgrade \u002F uninstall** use helper scripts in `\u002Fusr\u002Flocal\u002Fbin` (stop first with\n`container system stop`): `update-container.sh` (add `-v \u003Cversion>` to pin a version), and\n`uninstall-container.sh -d` to remove user data or `-k` to keep it. Full recipes in\n`references\u002Fworkflows.md`.\n\n## Command groups at a glance\n\nInvoke everything as `container \u003Cgroup> \u003Csubcommand>`. Container-lifecycle verbs (`run`,\n`create`, `start`, `stop`, `exec`, `logs`, `inspect`, `list`\u002F`ls`, `delete`\u002F`rm`, `kill`,\n`stats`) and `build` are top-level; image operations like `push`, `pull`, and `tag` live\nunder `container image`. Run `container \u003Cgroup> --help` for exact flags, or read\n`references\u002Fcommands.md` for the exhaustive matrix.\n\n| Group | What it does | Example |\n|-------|--------------|---------|\n| container lifecycle | Create, start, run, stop, exec, inspect, list, remove containers | `container run --rm -it docker.io\u002Flibrary\u002Falpine sh` |\n| build | Build an OCI image from a Dockerfile in the builder VM | `container build -t myapp:latest .` |\n| image | List, tag, inspect, remove, load\u002Fsave, prune local images; push\u002Fpull to registries | `container image ls` |\n| registry | Authenticate (login\u002Flogout\u002Flist) to OCI registries | `container registry login ghcr.io` |\n| system | Start\u002Fstop\u002Fstatus services, logs, disk usage (`df`), DNS, kernel, properties | `container system status` |\n| network | Create\u002Flist\u002Fremove container networks (**macOS 26 only**) | `container network create mynet` |\n| volume | Create\u002Flist\u002Finspect\u002Fremove persistent volumes | `container volume create data` |\n| builder | Manage the builder VM that runs `container build` (start\u002Fstop\u002Fstatus) | `container builder status` |\n| machine *(1.0.0+)* | Persistent Linux \"machine\" environments (added in 1.0.0) | `container machine --help` |\n\nExact subcommand names, aliases, arguments, and flags for each group live in\n`references\u002Fcommands.md` — consult it before running an unfamiliar command rather than\nguessing Docker-equivalent syntax.\n\n## Navigating this skill\n\nRead the reference file that matches the task; do not guess flags or behavior.\n\n- **`references\u002Fcommands.md`** — exhaustive CLI reference: every command group, subcommand,\n  alias, argument, and flag. Read this to construct any concrete `container ...` invocation,\n  or to confirm a flag exists before using it.\n- **`references\u002Fconcepts.md`** — architecture (VM-per-container, Containerization framework),\n  system requirements and macOS 15 vs 26 differences, networking model, per-container IPs,\n  security model, and a Docker-vs-`container` comparison. Read this to explain how or why\n  something works, or when a Docker mental model gives the wrong answer.\n- **`references\u002Fconfiguration.md`** — the system service, `config.toml` \u002F property model,\n  default kernel, DNS domains, default registry, builder resources, and machine settings.\n  Read this to change defaults, tune CPU\u002Fmemory, point at a private registry, or manage the\n  kernel.\n- **`references\u002Fworkflows.md`** — copy-pasteable task recipes (run an image, build & push,\n  wire up local DNS, mount a volume, expose ports) and troubleshooting for common failures.\n  Read this first when the user wants to accomplish a concrete end-to-end task.\n\n## Key rules\n\n- **This is not Docker.** The CLI resembles Docker, but flags, defaults, and daemon behavior\n  differ. Verify syntax in `references\u002Fcommands.md` instead of assuming Docker equivalence.\n- **Always ensure services are up first.** Run `container system start` (and confirm with\n  `container system status`) before any container\u002Fimage\u002Fbuild command; connection errors\n  usually mean the services are stopped.\n- **Images are standard OCI artifacts** and interoperate with Docker registries and other OCI\n  tools. Image references that omit a registry default to `docker.io` (configurable via the\n  `registry.domain` property — see `references\u002Fconfiguration.md`).\n- **Each container gets its own IP address** on its network (one lightweight VM per\n  container). There is no shared Docker bridge; reach a container directly by its IP, or set\n  up a local DNS domain (`container system dns create ...`, admin required) for name-based\n  access.\n- **`container network` requires macOS 26.** On macOS 15 only the single default subnet is\n  available and the network command group is unavailable — see `references\u002Fconcepts.md`.\n- **Use fully-qualified image references** when precision matters (e.g.\n  `docker.io\u002Flibrary\u002Falpine` rather than bare `alpine`) to avoid ambiguity about the source\n  registry.\n\n## Limitations\n\n- Apple Container requires Apple silicon and has materially different support and networking\n  behavior across macOS releases; verify the installed CLI version before relying on a flag.\n- OCI images and registry content are third-party inputs. Inspect and trust the image source\n  before pulling or running it.\n- This skill does not make container workloads safe by default: mounts, published ports,\n  privileged settings, registry credentials, and cleanup can expose or destroy data.\n- Stop before uninstalling, pruning, deleting containers, volumes, or images, and require\n  explicit approval for each destructive action.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":34,"source":35,"license":15,"category":36,"date_added":37,"description":7,"source_repo":38,"source_type":39,"license_source":40},"critical",[26,27,28,29],"macos","containers","oci","apple-silicon",[31,32,33],"claude","cursor","gemini","sanjay3290","https:\u002F\u002Fgithub.com\u002Fsanjay3290\u002Fai-skills\u002Ftree\u002Fmain\u002Fskills\u002Fapple-container","devops","2026-07-09","sanjay3290\u002Fai-skills","community","https:\u002F\u002Fgithub.com\u002Fsanjay3290\u002Fai-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fapple-container",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill apple-container",{"tool":54,"command":55},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill apple-container",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill apple-container","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002FSKILL.md",true,[62,68,72,76],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcommands.md","REFERENCE","参考文档",54119,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002Freferences\u002Fcommands.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fconcepts.md",18001,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002Freferences\u002Fconcepts.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fconfiguration.md",25402,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002Freferences\u002Fconfiguration.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflows.md",17908,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapple-container\u002Freferences\u002Fworkflows.md",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]