{"owner":"h2oai","repo":"guide","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1447,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"guide":{"command":"npx","args":["-y","@modelcontextprotocol/server-guide"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (code-guidelines-cursorrules-prompt-file.mdc)"],"skills":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/h2oai/guide/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/h2oai/guide/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/h2oai/guide/HEAD/.claude-plugin/plugin.json)",".cursorrules (code-guidelines-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for code development with guidelines integration.\"\nglobs: **/*\nalwaysApply: false\n---\n1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.\n\n2. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes.\n\n3. **No Apologies**: Never use apologies.\n\n4. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation.\n\n5. **No Whitespace Suggestions**: Don't suggest whitespace changes.\n\n6. **No Summaries**: Don't summarize changes made.\n\n7. **No Inventions**: Don't invent changes other than what's explicitly requested.\n\n8. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context.\n\n9. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.\n\n10. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.\n\n11. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context.\n\n12. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed.\n\n13. **Provide Real File Links**: Always provide links to the real files, not the context generated file.\n\n14. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested.\n\n15. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations.\n\n16. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.\n\n17. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency.\n\n18. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable.\n\n19. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes.\n\n20. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code.\n\n21. **Error Handling**: Implement robust error handling and logging where necessary.\n\n22. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability.\n\n23. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions.\n\n24. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability.\n\n25. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases.\n\n26. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.\n"},"files":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/h2oai/guide/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/h2oai/guide/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/h2oai/guide/HEAD/.claude-plugin/plugin.json)",".cursorrules (code-guidelines-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for code development with guidelines integration.\"\nglobs: **/*\nalwaysApply: false\n---\n1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.\n\n2. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes.\n\n3. **No Apologies**: Never use apologies.\n\n4. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation.\n\n5. **No Whitespace Suggestions**: Don't suggest whitespace changes.\n\n6. **No Summaries**: Don't summarize changes made.\n\n7. **No Inventions**: Don't invent changes other than what's explicitly requested.\n\n8. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context.\n\n9. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.\n\n10. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.\n\n11. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context.\n\n12. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed.\n\n13. **Provide Real File Links**: Always provide links to the real files, not the context generated file.\n\n14. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested.\n\n15. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations.\n\n16. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.\n\n17. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency.\n\n18. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable.\n\n19. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes.\n\n20. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code.\n\n21. **Error Handling**: Implement robust error handling and logging where necessary.\n\n22. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability.\n\n23. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions.\n\n24. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability.\n\n25. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases.\n\n26. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.\n"},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/h2oai/guide/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/h2oai/guide/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":190},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/h2oai/guide/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/h2oai/guide/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":176},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/h2oai/guide/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/h2oai/guide/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":169},{"name":".cursorrules","path":".cursorrules (code-guidelines-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/code-guidelines-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: code guidelines","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for code development with guidelines integration.\"\nglobs: **/*\nalwaysApply: false\n---\n1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.\n\n2. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes.\n\n3. **No Apologies**: Never use apologies.\n\n4. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation.\n\n5. **No Whitespace Suggestions**: Don't suggest whitespace changes.\n\n6. **No Summaries**: Don't summarize changes made.\n\n7. **No Inventions**: Don't invent changes other than what's explicitly requested.\n\n8. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context.\n\n9. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.\n\n10. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.\n\n11. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context.\n\n12. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed.\n\n13. **Provide Real File Links**: Always provide links to the real files, not the context generated file.\n\n14. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested.\n\n15. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations.\n\n16. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.\n\n17. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency.\n\n18. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable.\n\n19. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes.\n\n20. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code.\n\n21. **Error Handling**: Implement robust error handling and logging where necessary.\n\n22. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability.\n\n23. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions.\n\n24. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability.\n\n25. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases.\n\n26. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.\n","tokens":547,"sizeBytes":2937}],"systemPromptSnippet":"<yakaai_skills repo=\"h2oai/guide\">\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/h2oai/guide/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/h2oai/guide/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/h2oai/guide/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (code-guidelines-cursorrules-prompt-file.mdc) (Tokens: ~547 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for code development with guidelines integration.\"\nglobs: **/*\nalwaysApply: false\n---\n1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.\n\n2. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes.\n\n3. **No Apologies**: Never use apologies.\n\n4. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation.\n\n5. **No Whitespace Suggestions**: Don't suggest whitespace changes.\n\n6. **No Summaries**: Don't summarize changes made.\n\n7. **No Inventions**: Don't invent changes other than what's explicitly requested.\n\n8. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context.\n\n9. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.\n\n10. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.\n\n11. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context.\n\n12. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed.\n\n13. **Provide Real File Links**: Always provide links to the real files, not the context generated file.\n\n14. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested.\n\n15. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations.\n\n16. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.\n\n17. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency.\n\n18. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable.\n\n19. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes.\n\n20. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code.\n\n21. **Error Handling**: Implement robust error handling and logging where necessary.\n\n22. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability.\n\n23. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions.\n\n24. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability.\n\n25. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases.\n\n26. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.\n</yakaai_skills>"}