{"owner":"monkeytypegame","repo":"monkeytype","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.md"],"skills":{"AGENTS.md":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise.","CLAUDE.md":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise."},"files":{"AGENTS.md":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise.","CLAUDE.md":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise."},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise.","category":"root","tokens":191},{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"Be extremely concise. Sacrifice grammar for concision.\nFrontend is partially migrated from vanilla JS to SolidJS — new components use `.tsx`, legacy code remains vanilla.\nSingle test file: `pnpm vitest run path/to/test.ts`\nWhen running oxc lint, always use `--format agent`.\nFor typechecking, use `pnpm oxlint --type-aware --type-check` instead of `tsc`.\nFor styling, use Tailwind CSS, class property, `cn` utility. Do not use classlist. Only colors available are those defined in Tailwind config.\nIn legacy code, use `i` tags with FontAwesome classes. In new code, use `Fa` component.\nIn plan mode, before writing up a plan, ask clarifying questions if needed. At the end of plan mode, give me a list of unresolved questions to answer, if any. Make them concise.","category":"root","tokens":191}]}