{"owner":"tixl3d","repo":"tixl","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1754,"categories":["copilot-instructions","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"tixl":{"command":"npx","args":["-y","@modelcontextprotocol/server-tixl"]}}},"found":[".github/copilot-instructions.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{".github/copilot-instructions.md":"# Copilot Instructions for TiXL\n\nUse this file as the default instruction source for work in this repository.\n\n## Scope and Priority\n\n1. Follow repository conventions and existing local patterns.\n2. Prefer small, focused diffs over broad refactors.\n3. Preserve behavior unless a task explicitly changes it.\n\n## Architecture Orientation\n\n- `Core/`: shared runtime model, evaluation, resources, and engine logic\n- `Editor/`: authoring UI, interactions, graph editing, and tools\n- `Player/`: exported runtime playback host\n- `Operators/*`: operator packages and effect/content behavior\n\nFor detailed architecture and task routing, see `.agentic/SOLUTION_OVERVIEW.md`.\nFor full conventions, see `.agentic/AGENT_INSTRUCTIONS.md`; for driving the running\neditor programmatically (graphs, parameters, screenshots, visual tests), see\n`.agentic/DEBUG_PROTOCOL.md`.\n\n## Performance Rules (Critical)\n\nFor methods called every frame (operator update, editor draw/update, hot rendering paths):\n\n- Avoid heap allocations\n- Avoid LINQ\n- Prefer explicit loops and reusable buffers\n\nAllocations are acceptable for explicit user-triggered actions.\n\n## Resource and State Rules\n\n- Avoid storing long-lived direct instance/resource references when a stable id exists\n- Prefer storing/resolving by `Guid` where applicable\n- Be careful with stale references after reloads/package changes\n\n## UI Rules (Editor)\n\n- Use `UiColor` / `UiColors` instead of hard-coded `float4` colors\n- Use fonts sparingly, usually `Normal` and `Small`\n- Prefer `CustomComponents` and `FormInputs` helpers for ImGui layout/input tasks\n\n## Operator Rules\n\n- Follow: https://github.com/tixl3d/tixl/wiki/dev.OperatorConventions\n- Keep operator evaluation paths allocation-free\n- Match existing naming and slot conventions\n\n## Formatting and Style\n\n- Put `return` on a separate line (not inline after `if`)\n- Place private fields and private enums at class end\n- Prefix private fields with `_`\n- Prefer clear variable names (`faceIndex` over `i` when clarity helps)\n\n## Line Endings (Important for Bulk Edits)\n\nThe repo has **mixed line endings**: most `.cs` files use CRLF, some are LF.\nThere is no `.gitattributes` enforcing a single convention and `core.autocrlf`\nis `false`. When writing scripts that batch-rewrite many files this is the\nsingle biggest source of noisy diffs.\n\nRules for any bulk-edit script (Python, sed, etc.):\n\n1. Read files in **binary mode** (`open(path, 'rb')`). Do NOT use `read_text` or\n   text-mode reads — they silently strip `\\r`.\n2. **Detect each file's existing line ending** before writing. If the file\n   contains `\\r\\n`, write CRLF; otherwise LF. Per-file, not per-repo.\n3. Write in **binary mode** (`open(path, 'wb')`) with the bytes you produced.\n4. Sanity-check with `git diff --shortstat` before committing. If the line\n   count is much higher than the logic change implies, line endings were\n   munged — fix the working tree and `commit --amend`.\n\n## Review and Quality Expectations\n\n- Point out obvious bugs, misleading code, incorrect implementations, and typos\n- Fix spelling mistakes in touched comments when editing nearby code\n- Add parameter documentation only when purpose is not obvious from the parameter name\n\n## Working Checklist\n\nBefore editing:\n\n- Identify whether the code path runs every frame\n- Check nearby files for local conventions\n- Confirm the right project boundary (`Core`, `Editor`, `Player`, `Operators`)\n\nAfter editing:\n\n- Validate impacted files/build where practical\n- Call out performance impact and residual risks\n\n## References\n\n- Main docs: https://github.com/tixl3d/tixl/wiki\n- How TiXL works: https://github.com/tixl3d/tixl/wiki/help.HowTixlWorks\n- Existing local guidance: `AGENT_INSTRUCTIONS.md`\n- Architectural map: `SOLUTION_OVERVIEW.md`\n\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/plugin.json)"},"files":{".github/copilot-instructions.md":"# Copilot Instructions for TiXL\n\nUse this file as the default instruction source for work in this repository.\n\n## Scope and Priority\n\n1. Follow repository conventions and existing local patterns.\n2. Prefer small, focused diffs over broad refactors.\n3. Preserve behavior unless a task explicitly changes it.\n\n## Architecture Orientation\n\n- `Core/`: shared runtime model, evaluation, resources, and engine logic\n- `Editor/`: authoring UI, interactions, graph editing, and tools\n- `Player/`: exported runtime playback host\n- `Operators/*`: operator packages and effect/content behavior\n\nFor detailed architecture and task routing, see `.agentic/SOLUTION_OVERVIEW.md`.\nFor full conventions, see `.agentic/AGENT_INSTRUCTIONS.md`; for driving the running\neditor programmatically (graphs, parameters, screenshots, visual tests), see\n`.agentic/DEBUG_PROTOCOL.md`.\n\n## Performance Rules (Critical)\n\nFor methods called every frame (operator update, editor draw/update, hot rendering paths):\n\n- Avoid heap allocations\n- Avoid LINQ\n- Prefer explicit loops and reusable buffers\n\nAllocations are acceptable for explicit user-triggered actions.\n\n## Resource and State Rules\n\n- Avoid storing long-lived direct instance/resource references when a stable id exists\n- Prefer storing/resolving by `Guid` where applicable\n- Be careful with stale references after reloads/package changes\n\n## UI Rules (Editor)\n\n- Use `UiColor` / `UiColors` instead of hard-coded `float4` colors\n- Use fonts sparingly, usually `Normal` and `Small`\n- Prefer `CustomComponents` and `FormInputs` helpers for ImGui layout/input tasks\n\n## Operator Rules\n\n- Follow: https://github.com/tixl3d/tixl/wiki/dev.OperatorConventions\n- Keep operator evaluation paths allocation-free\n- Match existing naming and slot conventions\n\n## Formatting and Style\n\n- Put `return` on a separate line (not inline after `if`)\n- Place private fields and private enums at class end\n- Prefix private fields with `_`\n- Prefer clear variable names (`faceIndex` over `i` when clarity helps)\n\n## Line Endings (Important for Bulk Edits)\n\nThe repo has **mixed line endings**: most `.cs` files use CRLF, some are LF.\nThere is no `.gitattributes` enforcing a single convention and `core.autocrlf`\nis `false`. When writing scripts that batch-rewrite many files this is the\nsingle biggest source of noisy diffs.\n\nRules for any bulk-edit script (Python, sed, etc.):\n\n1. Read files in **binary mode** (`open(path, 'rb')`). Do NOT use `read_text` or\n   text-mode reads — they silently strip `\\r`.\n2. **Detect each file's existing line ending** before writing. If the file\n   contains `\\r\\n`, write CRLF; otherwise LF. Per-file, not per-repo.\n3. Write in **binary mode** (`open(path, 'wb')`) with the bytes you produced.\n4. Sanity-check with `git diff --shortstat` before committing. If the line\n   count is much higher than the logic change implies, line endings were\n   munged — fix the working tree and `commit --amend`.\n\n## Review and Quality Expectations\n\n- Point out obvious bugs, misleading code, incorrect implementations, and typos\n- Fix spelling mistakes in touched comments when editing nearby code\n- Add parameter documentation only when purpose is not obvious from the parameter name\n\n## Working Checklist\n\nBefore editing:\n\n- Identify whether the code path runs every frame\n- Check nearby files for local conventions\n- Confirm the right project boundary (`Core`, `Editor`, `Player`, `Operators`)\n\nAfter editing:\n\n- Validate impacted files/build where practical\n- Call out performance impact and residual risks\n\n## References\n\n- Main docs: https://github.com/tixl3d/tixl/wiki\n- How TiXL works: https://github.com/tixl3d/tixl/wiki/help.HowTixlWorks\n- Existing local guidance: `AGENT_INSTRUCTIONS.md`\n- Architectural map: `SOLUTION_OVERVIEW.md`\n\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","rawUrl":"https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.github/copilot-instructions.md","title":"GitHub Copilot Instructions","category":"copilot-instructions","format":"markdown","content":"# Copilot Instructions for TiXL\n\nUse this file as the default instruction source for work in this repository.\n\n## Scope and Priority\n\n1. Follow repository conventions and existing local patterns.\n2. Prefer small, focused diffs over broad refactors.\n3. Preserve behavior unless a task explicitly changes it.\n\n## Architecture Orientation\n\n- `Core/`: shared runtime model, evaluation, resources, and engine logic\n- `Editor/`: authoring UI, interactions, graph editing, and tools\n- `Player/`: exported runtime playback host\n- `Operators/*`: operator packages and effect/content behavior\n\nFor detailed architecture and task routing, see `.agentic/SOLUTION_OVERVIEW.md`.\nFor full conventions, see `.agentic/AGENT_INSTRUCTIONS.md`; for driving the running\neditor programmatically (graphs, parameters, screenshots, visual tests), see\n`.agentic/DEBUG_PROTOCOL.md`.\n\n## Performance Rules (Critical)\n\nFor methods called every frame (operator update, editor draw/update, hot rendering paths):\n\n- Avoid heap allocations\n- Avoid LINQ\n- Prefer explicit loops and reusable buffers\n\nAllocations are acceptable for explicit user-triggered actions.\n\n## Resource and State Rules\n\n- Avoid storing long-lived direct instance/resource references when a stable id exists\n- Prefer storing/resolving by `Guid` where applicable\n- Be careful with stale references after reloads/package changes\n\n## UI Rules (Editor)\n\n- Use `UiColor` / `UiColors` instead of hard-coded `float4` colors\n- Use fonts sparingly, usually `Normal` and `Small`\n- Prefer `CustomComponents` and `FormInputs` helpers for ImGui layout/input tasks\n\n## Operator Rules\n\n- Follow: https://github.com/tixl3d/tixl/wiki/dev.OperatorConventions\n- Keep operator evaluation paths allocation-free\n- Match existing naming and slot conventions\n\n## Formatting and Style\n\n- Put `return` on a separate line (not inline after `if`)\n- Place private fields and private enums at class end\n- Prefix private fields with `_`\n- Prefer clear variable names (`faceIndex` over `i` when clarity helps)\n\n## Line Endings (Important for Bulk Edits)\n\nThe repo has **mixed line endings**: most `.cs` files use CRLF, some are LF.\nThere is no `.gitattributes` enforcing a single convention and `core.autocrlf`\nis `false`. When writing scripts that batch-rewrite many files this is the\nsingle biggest source of noisy diffs.\n\nRules for any bulk-edit script (Python, sed, etc.):\n\n1. Read files in **binary mode** (`open(path, 'rb')`). Do NOT use `read_text` or\n   text-mode reads — they silently strip `\\r`.\n2. **Detect each file's existing line ending** before writing. If the file\n   contains `\\r\\n`, write CRLF; otherwise LF. Per-file, not per-repo.\n3. Write in **binary mode** (`open(path, 'wb')`) with the bytes you produced.\n4. Sanity-check with `git diff --shortstat` before committing. If the line\n   count is much higher than the logic change implies, line endings were\n   munged — fix the working tree and `commit --amend`.\n\n## Review and Quality Expectations\n\n- Point out obvious bugs, misleading code, incorrect implementations, and typos\n- Fix spelling mistakes in touched comments when editing nearby code\n- Add parameter documentation only when purpose is not obvious from the parameter name\n\n## Working Checklist\n\nBefore editing:\n\n- Identify whether the code path runs every frame\n- Check nearby files for local conventions\n- Confirm the right project boundary (`Core`, `Editor`, `Player`, `Operators`)\n\nAfter editing:\n\n- Validate impacted files/build where practical\n- Call out performance impact and residual risks\n\n## References\n\n- Main docs: https://github.com/tixl3d/tixl/wiki\n- How TiXL works: https://github.com/tixl3d/tixl/wiki/help.HowTixlWorks\n- Existing local guidance: `AGENT_INSTRUCTIONS.md`\n- Architectural map: `SOLUTION_OVERVIEW.md`\n\n","isInternal":false,"tokens":854,"sizeBytes":3778},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":190},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":176},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":169}],"systemPromptSnippet":"<yakaai_skills repo=\"tixl3d/tixl\">\n<!-- File: .github/copilot-instructions.md (Tokens: ~854 | Category: copilot-instructions) -->\n# Copilot Instructions for TiXL\n\nUse this file as the default instruction source for work in this repository.\n\n## Scope and Priority\n\n1. Follow repository conventions and existing local patterns.\n2. Prefer small, focused diffs over broad refactors.\n3. Preserve behavior unless a task explicitly changes it.\n\n## Architecture Orientation\n\n- `Core/`: shared runtime model, evaluation, resources, and engine logic\n- `Editor/`: authoring UI, interactions, graph editing, and tools\n- `Player/`: exported runtime playback host\n- `Operators/*`: operator packages and effect/content behavior\n\nFor detailed architecture and task routing, see `.agentic/SOLUTION_OVERVIEW.md`.\nFor full conventions, see `.agentic/AGENT_INSTRUCTIONS.md`; for driving the running\neditor programmatically (graphs, parameters, screenshots, visual tests), see\n`.agentic/DEBUG_PROTOCOL.md`.\n\n## Performance Rules (Critical)\n\nFor methods called every frame (operator update, editor draw/update, hot rendering paths):\n\n- Avoid heap allocations\n- Avoid LINQ\n- Prefer explicit loops and reusable buffers\n\nAllocations are acceptable for explicit user-triggered actions.\n\n## Resource and State Rules\n\n- Avoid storing long-lived direct instance/resource references when a stable id exists\n- Prefer storing/resolving by `Guid` where applicable\n- Be careful with stale references after reloads/package changes\n\n## UI Rules (Editor)\n\n- Use `UiColor` / `UiColors` instead of hard-coded `float4` colors\n- Use fonts sparingly, usually `Normal` and `Small`\n- Prefer `CustomComponents` and `FormInputs` helpers for ImGui layout/input tasks\n\n## Operator Rules\n\n- Follow: https://github.com/tixl3d/tixl/wiki/dev.OperatorConventions\n- Keep operator evaluation paths allocation-free\n- Match existing naming and slot conventions\n\n## Formatting and Style\n\n- Put `return` on a separate line (not inline after `if`)\n- Place private fields and private enums at class end\n- Prefix private fields with `_`\n- Prefer clear variable names (`faceIndex` over `i` when clarity helps)\n\n## Line Endings (Important for Bulk Edits)\n\nThe repo has **mixed line endings**: most `.cs` files use CRLF, some are LF.\nThere is no `.gitattributes` enforcing a single convention and `core.autocrlf`\nis `false`. When writing scripts that batch-rewrite many files this is the\nsingle biggest source of noisy diffs.\n\nRules for any bulk-edit script (Python, sed, etc.):\n\n1. Read files in **binary mode** (`open(path, 'rb')`). Do NOT use `read_text` or\n   text-mode reads — they silently strip `\\r`.\n2. **Detect each file's existing line ending** before writing. If the file\n   contains `\\r\\n`, write CRLF; otherwise LF. Per-file, not per-repo.\n3. Write in **binary mode** (`open(path, 'wb')`) with the bytes you produced.\n4. Sanity-check with `git diff --shortstat` before committing. If the line\n   count is much higher than the logic change implies, line endings were\n   munged — fix the working tree and `commit --amend`.\n\n## Review and Quality Expectations\n\n- Point out obvious bugs, misleading code, incorrect implementations, and typos\n- Fix spelling mistakes in touched comments when editing nearby code\n- Add parameter documentation only when purpose is not obvious from the parameter name\n\n## Working Checklist\n\nBefore editing:\n\n- Identify whether the code path runs every frame\n- Check nearby files for local conventions\n- Confirm the right project boundary (`Core`, `Editor`, `Player`, `Operators`)\n\nAfter editing:\n\n- Validate impacted files/build where practical\n- Call out performance impact and residual risks\n\n## References\n\n- Main docs: https://github.com/tixl3d/tixl/wiki\n- How TiXL works: https://github.com/tixl3d/tixl/wiki/help.HowTixlWorks\n- Existing local guidance: `AGENT_INSTRUCTIONS.md`\n- Architectural map: `SOLUTION_OVERVIEW.md`\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/tixl3d/tixl/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}