{"owner":"rolling-scopes","repo":"rsschool-app","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/copilot-instructions.md"],"skills":{"AGENTS.md":"# LLM Agents Instructions\n\n## General\n\n- Read `README.md` first for project overview and architecture\n- Read `CONTRIBUTING.md` for local development setup, commands, commit messages, and PR conventions\n- Read `GUIDELINES.md` for code style and testing patterns\n- Read `DOMAIN.md` for application domain and data models\n- Read all `*/README.md` files for workspace specific architecture and development guidelines\n\n## Instructions\n\n- Use the `tmp` folder in the repository to store temporary files during execution and planning if needed\n- Never run deploy commands\n- Run `npm run lint`, `npm run test`, `npm run compile`, and `npm run format` at the end of each completed task if you modified any files. If any of these steps fail, fix the issues and run the commands again.\n- Prefer telegraph style for communications and reasoning. Sacrifice grammar and punctuation for clarity and conciseness. Save tokens.\n\n## Documentation Style\n\nUse the following writing style for documentation, comments and README files.\n\nAudience: Software Engineers. Expect half to be native speakers and half non-native speakers.\n\n- Keep the reading level at or below 9th grade (Flesch-Kincaid)\n- Write in clear, concise, active voice; don't assume passive voice reads well\n- Keep noun phrases short and avoid stacked modifiers\n- Limit embedded clauses to one level\n- Use conditionals sparingly and stick to simple if/then forms; avoid mixed or inverted versions\n- Use transition words (however, therefore, because) to show logic instead of expecting readers to infer it\n- Spread new ideas across sentences; avoid packing many concepts into one\n- Do not end list items with a period\n- Do not use emojis\n- Do not write obvious comments; explain why, not how or what\n\n## Commands\n\n- `npm run lint`: Run linting\n- `npm run test`: Run tests\n- `npm run compile`: Compile the project\n- `npm run format`: Format the code",".github/copilot-instructions.md":"Use instructions from `AGENTS.md` to guide your work."},"files":{"AGENTS.md":"# LLM Agents Instructions\n\n## General\n\n- Read `README.md` first for project overview and architecture\n- Read `CONTRIBUTING.md` for local development setup, commands, commit messages, and PR conventions\n- Read `GUIDELINES.md` for code style and testing patterns\n- Read `DOMAIN.md` for application domain and data models\n- Read all `*/README.md` files for workspace specific architecture and development guidelines\n\n## Instructions\n\n- Use the `tmp` folder in the repository to store temporary files during execution and planning if needed\n- Never run deploy commands\n- Run `npm run lint`, `npm run test`, `npm run compile`, and `npm run format` at the end of each completed task if you modified any files. If any of these steps fail, fix the issues and run the commands again.\n- Prefer telegraph style for communications and reasoning. Sacrifice grammar and punctuation for clarity and conciseness. Save tokens.\n\n## Documentation Style\n\nUse the following writing style for documentation, comments and README files.\n\nAudience: Software Engineers. Expect half to be native speakers and half non-native speakers.\n\n- Keep the reading level at or below 9th grade (Flesch-Kincaid)\n- Write in clear, concise, active voice; don't assume passive voice reads well\n- Keep noun phrases short and avoid stacked modifiers\n- Limit embedded clauses to one level\n- Use conditionals sparingly and stick to simple if/then forms; avoid mixed or inverted versions\n- Use transition words (however, therefore, because) to show logic instead of expecting readers to infer it\n- Spread new ideas across sentences; avoid packing many concepts into one\n- Do not end list items with a period\n- Do not use emojis\n- Do not write obvious comments; explain why, not how or what\n\n## Commands\n\n- `npm run lint`: Run linting\n- `npm run test`: Run tests\n- `npm run compile`: Compile the project\n- `npm run format`: Format the code",".github/copilot-instructions.md":"Use instructions from `AGENTS.md` to guide your work."},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# LLM Agents Instructions\n\n## General\n\n- Read `README.md` first for project overview and architecture\n- Read `CONTRIBUTING.md` for local development setup, commands, commit messages, and PR conventions\n- Read `GUIDELINES.md` for code style and testing patterns\n- Read `DOMAIN.md` for application domain and data models\n- Read all `*/README.md` files for workspace specific architecture and development guidelines\n\n## Instructions\n\n- Use the `tmp` folder in the repository to store temporary files during execution and planning if needed\n- Never run deploy commands\n- Run `npm run lint`, `npm run test`, `npm run compile`, and `npm run format` at the end of each completed task if you modified any files. If any of these steps fail, fix the issues and run the commands again.\n- Prefer telegraph style for communications and reasoning. Sacrifice grammar and punctuation for clarity and conciseness. Save tokens.\n\n## Documentation Style\n\nUse the following writing style for documentation, comments and README files.\n\nAudience: Software Engineers. Expect half to be native speakers and half non-native speakers.\n\n- Keep the reading level at or below 9th grade (Flesch-Kincaid)\n- Write in clear, concise, active voice; don't assume passive voice reads well\n- Keep noun phrases short and avoid stacked modifiers\n- Limit embedded clauses to one level\n- Use conditionals sparingly and stick to simple if/then forms; avoid mixed or inverted versions\n- Use transition words (however, therefore, because) to show logic instead of expecting readers to infer it\n- Spread new ideas across sentences; avoid packing many concepts into one\n- Do not end list items with a period\n- Do not use emojis\n- Do not write obvious comments; explain why, not how or what\n\n## Commands\n\n- `npm run lint`: Run linting\n- `npm run test`: Run tests\n- `npm run compile`: Compile the project\n- `npm run format`: Format the code","category":"root","tokens":473},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"Use instructions from `AGENTS.md` to guide your work.","category":".github","tokens":14}]}