{"owner":"kovidgoyal","repo":"kitty","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":556,"categories":["copilot-instructions","cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":[".github/copilot-instructions.md",".cursorrules (sveltekit-typescript-guide-cursorrules-prompt-file.mdc)"],"skills":{".github/copilot-instructions.md":"Before implementing any code changes or responding to a request, run the\nfollowing command:\n\npython3 .github/workflows/ci.py build\n\nThis will download needed dependencies, then create all generated files\nand build the project, making it ready for inspection.\n\n# Repository Build & Test Instructions\n\n## Build Procedures\n- **Build command:** Run `./dev.sh build` to build the project\n- Run `gen/config.py` to update generated config parsing code for both kitty\n  and kitten. The `gen/go_code.py` generator is run automatically by the build\n  command to keep generated Go code files up to date.\n- To build individual kittens use the build command above **do not** try to run go build\n  yourself.\n\nOnce a build is done, the kitty and kitten binaries will be in the `kitty/launcher` directory.\nNote that the kitty binary can run python files using `kitty +launch file.py`.\nWhen it does so the kitty fast_data_types module is available to the python\ncode.\n\n## Test Procedures\n- To run the complete test suite, run `./test.py`\n- To run a specific test, run `./test.py test_name` where `test_name` is the name of the test without the\n  leading `test_` for Python tests and without the leading `Test` for Go tests.\n- Do not use go test or ./setup.py test to run tests\n\n## PR guidance\nWhen creating a pull request, if the changes in the pull request are user\nvisible compared to the previous kitty release, add an entry in the file docs/changelog.rst\ndescribing the change. If the changes include changes to Go code, run gofmt on\nthe changed Go files to ensure they are formatted correctly, before submitting\nyour changes.\n",".cursorrules (sveltekit-typescript-guide-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for SvelteKit development with TypeScript integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in Svelte 5, SvelteKit, TypeScript, Supabase, Drizzle and modern web development.\n\nKey Principles\n\nCode Style and Structure\nNaming Conventions\nTypeScript Usage\nSvelte Runes\nUI and Styling\nShadcn Color Conventions\nSvelteKit Project Structure\nComponent Development\nState Management\n\nUse classes for complex state management (state machines):\n```typescript\n// counter.svelte.ts\nclass Counter {\n  count = $state(0);\n  incrementor = $state(1);\n  increment() {\n    this.count += this.incrementor;\n  }\n  resetCount() {\n    this.count = 0;\n  }\n  resetIncrementor() {\n    this.incrementor = 1;\n  }\n}\nexport const counter = new Counter();\n"},"files":{".github/copilot-instructions.md":"Before implementing any code changes or responding to a request, run the\nfollowing command:\n\npython3 .github/workflows/ci.py build\n\nThis will download needed dependencies, then create all generated files\nand build the project, making it ready for inspection.\n\n# Repository Build & Test Instructions\n\n## Build Procedures\n- **Build command:** Run `./dev.sh build` to build the project\n- Run `gen/config.py` to update generated config parsing code for both kitty\n  and kitten. The `gen/go_code.py` generator is run automatically by the build\n  command to keep generated Go code files up to date.\n- To build individual kittens use the build command above **do not** try to run go build\n  yourself.\n\nOnce a build is done, the kitty and kitten binaries will be in the `kitty/launcher` directory.\nNote that the kitty binary can run python files using `kitty +launch file.py`.\nWhen it does so the kitty fast_data_types module is available to the python\ncode.\n\n## Test Procedures\n- To run the complete test suite, run `./test.py`\n- To run a specific test, run `./test.py test_name` where `test_name` is the name of the test without the\n  leading `test_` for Python tests and without the leading `Test` for Go tests.\n- Do not use go test or ./setup.py test to run tests\n\n## PR guidance\nWhen creating a pull request, if the changes in the pull request are user\nvisible compared to the previous kitty release, add an entry in the file docs/changelog.rst\ndescribing the change. If the changes include changes to Go code, run gofmt on\nthe changed Go files to ensure they are formatted correctly, before submitting\nyour changes.\n",".cursorrules (sveltekit-typescript-guide-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for SvelteKit development with TypeScript integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in Svelte 5, SvelteKit, TypeScript, Supabase, Drizzle and modern web development.\n\nKey Principles\n\nCode Style and Structure\nNaming Conventions\nTypeScript Usage\nSvelte Runes\nUI and Styling\nShadcn Color Conventions\nSvelteKit Project Structure\nComponent Development\nState Management\n\nUse classes for complex state management (state machines):\n```typescript\n// counter.svelte.ts\nclass Counter {\n  count = $state(0);\n  incrementor = $state(1);\n  increment() {\n    this.count += this.incrementor;\n  }\n  resetCount() {\n    this.count = 0;\n  }\n  resetIncrementor() {\n    this.incrementor = 1;\n  }\n}\nexport const counter = new Counter();\n"},"items":[{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","rawUrl":"https://raw.githubusercontent.com/kovidgoyal/kitty/HEAD/.github/copilot-instructions.md","title":"GitHub Copilot Instructions","category":"copilot-instructions","format":"markdown","content":"Before implementing any code changes or responding to a request, run the\nfollowing command:\n\npython3 .github/workflows/ci.py build\n\nThis will download needed dependencies, then create all generated files\nand build the project, making it ready for inspection.\n\n# Repository Build & Test Instructions\n\n## Build Procedures\n- **Build command:** Run `./dev.sh build` to build the project\n- Run `gen/config.py` to update generated config parsing code for both kitty\n  and kitten. The `gen/go_code.py` generator is run automatically by the build\n  command to keep generated Go code files up to date.\n- To build individual kittens use the build command above **do not** try to run go build\n  yourself.\n\nOnce a build is done, the kitty and kitten binaries will be in the `kitty/launcher` directory.\nNote that the kitty binary can run python files using `kitty +launch file.py`.\nWhen it does so the kitty fast_data_types module is available to the python\ncode.\n\n## Test Procedures\n- To run the complete test suite, run `./test.py`\n- To run a specific test, run `./test.py test_name` where `test_name` is the name of the test without the\n  leading `test_` for Python tests and without the leading `Test` for Go tests.\n- Do not use go test or ./setup.py test to run tests\n\n## PR guidance\nWhen creating a pull request, if the changes in the pull request are user\nvisible compared to the previous kitty release, add an entry in the file docs/changelog.rst\ndescribing the change. If the changes include changes to Go code, run gofmt on\nthe changed Go files to ensure they are formatted correctly, before submitting\nyour changes.\n","isInternal":false,"tokens":367,"sizeBytes":1614},{"name":".cursorrules","path":".cursorrules (sveltekit-typescript-guide-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/sveltekit-typescript-guide-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: sveltekit typescript guide","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for SvelteKit development with TypeScript integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in Svelte 5, SvelteKit, TypeScript, Supabase, Drizzle and modern web development.\n\nKey Principles\n\nCode Style and Structure\nNaming Conventions\nTypeScript Usage\nSvelte Runes\nUI and Styling\nShadcn Color Conventions\nSvelteKit Project Structure\nComponent Development\nState Management\n\nUse classes for complex state management (state machines):\n```typescript\n// counter.svelte.ts\nclass Counter {\n  count = $state(0);\n  incrementor = $state(1);\n  increment() {\n    this.count += this.incrementor;\n  }\n  resetCount() {\n    this.count = 0;\n  }\n  resetIncrementor() {\n    this.incrementor = 1;\n  }\n}\nexport const counter = new Counter();\n","tokens":189,"sizeBytes":769}],"systemPromptSnippet":"<yakaai_skills repo=\"kovidgoyal/kitty\">\n<!-- File: .github/copilot-instructions.md (Tokens: ~367 | Category: copilot-instructions) -->\nBefore implementing any code changes or responding to a request, run the\nfollowing command:\n\npython3 .github/workflows/ci.py build\n\nThis will download needed dependencies, then create all generated files\nand build the project, making it ready for inspection.\n\n# Repository Build & Test Instructions\n\n## Build Procedures\n- **Build command:** Run `./dev.sh build` to build the project\n- Run `gen/config.py` to update generated config parsing code for both kitty\n  and kitten. The `gen/go_code.py` generator is run automatically by the build\n  command to keep generated Go code files up to date.\n- To build individual kittens use the build command above **do not** try to run go build\n  yourself.\n\nOnce a build is done, the kitty and kitten binaries will be in the `kitty/launcher` directory.\nNote that the kitty binary can run python files using `kitty +launch file.py`.\nWhen it does so the kitty fast_data_types module is available to the python\ncode.\n\n## Test Procedures\n- To run the complete test suite, run `./test.py`\n- To run a specific test, run `./test.py test_name` where `test_name` is the name of the test without the\n  leading `test_` for Python tests and without the leading `Test` for Go tests.\n- Do not use go test or ./setup.py test to run tests\n\n## PR guidance\nWhen creating a pull request, if the changes in the pull request are user\nvisible compared to the previous kitty release, add an entry in the file docs/changelog.rst\ndescribing the change. If the changes include changes to Go code, run gofmt on\nthe changed Go files to ensure they are formatted correctly, before submitting\nyour changes.\n\n<!-- File: .cursorrules (sveltekit-typescript-guide-cursorrules-prompt-file.mdc) (Tokens: ~189 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for SvelteKit development with TypeScript integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert in Svelte 5, SvelteKit, TypeScript, Supabase, Drizzle and modern web development.\n\nKey Principles\n\nCode Style and Structure\nNaming Conventions\nTypeScript Usage\nSvelte Runes\nUI and Styling\nShadcn Color Conventions\nSvelteKit Project Structure\nComponent Development\nState Management\n\nUse classes for complex state management (state machines):\n```typescript\n// counter.svelte.ts\nclass Counter {\n  count = $state(0);\n  incrementor = $state(1);\n  increment() {\n    this.count += this.incrementor;\n  }\n  resetCount() {\n    this.count = 0;\n  }\n  resetIncrementor() {\n    this.incrementor = 1;\n  }\n}\nexport const counter = new Counter();\n</yakaai_skills>"}