{"owner":"linkedin","repo":"Liger-Kernel","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\nGuidance for AI coding assistants working in this repository.\n\n## Skills\n\nRepository-specific workflow guides (\"skills\") live in [`.agents/skills/`](.agents/skills/). Each subdirectory is a self-contained guide for a multi-stage workflow. Read the `SKILL.md` at the top of each subdirectory for an overview; the other files in that directory are referenced from `SKILL.md` and should be read on demand.\n\n| Skill | What it does |\n|-------|--------------|\n| [`liger-kernel-dev`](.agents/skills/liger-kernel-dev/SKILL.md) | Develops new Triton kernels from a PyTorch reference (or modifies existing kernels). 3-stage pipeline: Analyze → Generate → Validate. NVIDIA GPUs only. |\n| [`liger-autopatch`](.agents/skills/liger-autopatch/SKILL.md) | Adds Liger Kernel support for a new HuggingFace Transformers model, or modifies an existing monkey-patch. 3-stage pipeline: Analyze → Generate → Validate. |\n| [`liger-kernel-perf`](.agents/skills/liger-kernel-perf/SKILL.md) | Optimizes the performance of an existing Liger Triton kernel. 3-stage pipeline: Profile → Optimize → Finalize. NVIDIA GPUs only. |\n\nThe skills are written to be runtime-agnostic — they describe the workflow as a sequence of stages a competent agent (or human) can follow. Where a stage says \"Follow the X workflow in `x.md`\", that's a directive to read and execute that file's instructions; runtimes that support parallel subagents may delegate the stage, but it is not required.\n\n## Vendor-specific shortcuts\n\nFor convenience, some assistants auto-discover skills from vendor-specific paths. These point at the canonical `.agents/skills/` directory:\n\n- `.claude/skills` → symlink → `.agents/skills` (for Claude Code)\n\nIf you're adding support for another assistant, add a symlink (or your tool's preferred adapter) pointing to `.agents/skills/`. Do not duplicate the content.\n\n## Repo conventions\n\n- Source layout: `src/liger_kernel/{ops,transformers}/` for Triton ops and `nn.Module` / HF wrappers respectively\n- Tests: `test/transformers/` (unit) and `test/convergence/{bf16,fp32}/` (model convergence)\n- Benchmarks: `benchmark/scripts/` (scripts) and `benchmark/data/all_benchmark_data.csv` (results)\n- Lint/format: `make checkstyle` (uses `ruff`)\n- Install dev mode: `pip install -e \".[dev]\"`\n\nSee `README.md` for the project overview and contribution guide.\n"},"files":{"AGENTS.md":"# AGENTS.md\n\nGuidance for AI coding assistants working in this repository.\n\n## Skills\n\nRepository-specific workflow guides (\"skills\") live in [`.agents/skills/`](.agents/skills/). Each subdirectory is a self-contained guide for a multi-stage workflow. Read the `SKILL.md` at the top of each subdirectory for an overview; the other files in that directory are referenced from `SKILL.md` and should be read on demand.\n\n| Skill | What it does |\n|-------|--------------|\n| [`liger-kernel-dev`](.agents/skills/liger-kernel-dev/SKILL.md) | Develops new Triton kernels from a PyTorch reference (or modifies existing kernels). 3-stage pipeline: Analyze → Generate → Validate. NVIDIA GPUs only. |\n| [`liger-autopatch`](.agents/skills/liger-autopatch/SKILL.md) | Adds Liger Kernel support for a new HuggingFace Transformers model, or modifies an existing monkey-patch. 3-stage pipeline: Analyze → Generate → Validate. |\n| [`liger-kernel-perf`](.agents/skills/liger-kernel-perf/SKILL.md) | Optimizes the performance of an existing Liger Triton kernel. 3-stage pipeline: Profile → Optimize → Finalize. NVIDIA GPUs only. |\n\nThe skills are written to be runtime-agnostic — they describe the workflow as a sequence of stages a competent agent (or human) can follow. Where a stage says \"Follow the X workflow in `x.md`\", that's a directive to read and execute that file's instructions; runtimes that support parallel subagents may delegate the stage, but it is not required.\n\n## Vendor-specific shortcuts\n\nFor convenience, some assistants auto-discover skills from vendor-specific paths. These point at the canonical `.agents/skills/` directory:\n\n- `.claude/skills` → symlink → `.agents/skills` (for Claude Code)\n\nIf you're adding support for another assistant, add a symlink (or your tool's preferred adapter) pointing to `.agents/skills/`. Do not duplicate the content.\n\n## Repo conventions\n\n- Source layout: `src/liger_kernel/{ops,transformers}/` for Triton ops and `nn.Module` / HF wrappers respectively\n- Tests: `test/transformers/` (unit) and `test/convergence/{bf16,fp32}/` (model convergence)\n- Benchmarks: `benchmark/scripts/` (scripts) and `benchmark/data/all_benchmark_data.csv` (results)\n- Lint/format: `make checkstyle` (uses `ruff`)\n- Install dev mode: `pip install -e \".[dev]\"`\n\nSee `README.md` for the project overview and contribution guide.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\nGuidance for AI coding assistants working in this repository.\n\n## Skills\n\nRepository-specific workflow guides (\"skills\") live in [`.agents/skills/`](.agents/skills/). Each subdirectory is a self-contained guide for a multi-stage workflow. Read the `SKILL.md` at the top of each subdirectory for an overview; the other files in that directory are referenced from `SKILL.md` and should be read on demand.\n\n| Skill | What it does |\n|-------|--------------|\n| [`liger-kernel-dev`](.agents/skills/liger-kernel-dev/SKILL.md) | Develops new Triton kernels from a PyTorch reference (or modifies existing kernels). 3-stage pipeline: Analyze → Generate → Validate. NVIDIA GPUs only. |\n| [`liger-autopatch`](.agents/skills/liger-autopatch/SKILL.md) | Adds Liger Kernel support for a new HuggingFace Transformers model, or modifies an existing monkey-patch. 3-stage pipeline: Analyze → Generate → Validate. |\n| [`liger-kernel-perf`](.agents/skills/liger-kernel-perf/SKILL.md) | Optimizes the performance of an existing Liger Triton kernel. 3-stage pipeline: Profile → Optimize → Finalize. NVIDIA GPUs only. |\n\nThe skills are written to be runtime-agnostic — they describe the workflow as a sequence of stages a competent agent (or human) can follow. Where a stage says \"Follow the X workflow in `x.md`\", that's a directive to read and execute that file's instructions; runtimes that support parallel subagents may delegate the stage, but it is not required.\n\n## Vendor-specific shortcuts\n\nFor convenience, some assistants auto-discover skills from vendor-specific paths. These point at the canonical `.agents/skills/` directory:\n\n- `.claude/skills` → symlink → `.agents/skills` (for Claude Code)\n\nIf you're adding support for another assistant, add a symlink (or your tool's preferred adapter) pointing to `.agents/skills/`. Do not duplicate the content.\n\n## Repo conventions\n\n- Source layout: `src/liger_kernel/{ops,transformers}/` for Triton ops and `nn.Module` / HF wrappers respectively\n- Tests: `test/transformers/` (unit) and `test/convergence/{bf16,fp32}/` (model convergence)\n- Benchmarks: `benchmark/scripts/` (scripts) and `benchmark/data/all_benchmark_data.csv` (results)\n- Lint/format: `make checkstyle` (uses `ruff`)\n- Install dev mode: `pip install -e \".[dev]\"`\n\nSee `README.md` for the project overview and contribution guide.\n","category":"root","tokens":586}]}