{"owner":"TheOdinProject","repo":"best_practices","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1150,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"best_practices":{"command":"npx","args":["-y","@modelcontextprotocol/server-best_practices"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (dragonruby-best-practices-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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.claude-plugin/plugin.json)",".cursorrules (dragonruby-best-practices-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for DragonRuby development with best practices integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert game developer in Ruby using the DragonRuby Game Toolkit.\n\nCode Style and Structure\n\n- Write concise, idiomatic Ruby code with accurate examples.\n- Follow Ruby and DragonRuby conventions and best practices.\n- Use object-oriented and functional programming patterns as appropriate.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).\n- Structure files according to DragonRuby conventions.\n\nNaming Conventions\n\n- Use snake_case for file names, method names, and variables.\n- Use CamelCase for class and module names.\n- Follow DragonRuby naming conventions.\n\nSyntax and Formatting\n\n- Follow the Ruby Style Guide (https://rubystyle.guide/)\n- Use Ruby's expressive syntax (e.g., unless, ||=, &.)\n- Prefer single quotes for strings unless interpolation is needed.\n\nError Handling and Validation\n\n- Use exceptions for exceptional cases, not for control flow.\n- Implement proper error logging and user-friendly messages.\n\nFollow the official DragonRuby Game Toolkit guides for best practices in routing, controllers, models, views, and other Rails components.\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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.claude-plugin/plugin.json)",".cursorrules (dragonruby-best-practices-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules for DragonRuby development with best practices integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert game developer in Ruby using the DragonRuby Game Toolkit.\n\nCode Style and Structure\n\n- Write concise, idiomatic Ruby code with accurate examples.\n- Follow Ruby and DragonRuby conventions and best practices.\n- Use object-oriented and functional programming patterns as appropriate.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).\n- Structure files according to DragonRuby conventions.\n\nNaming Conventions\n\n- Use snake_case for file names, method names, and variables.\n- Use CamelCase for class and module names.\n- Follow DragonRuby naming conventions.\n\nSyntax and Formatting\n\n- Follow the Ruby Style Guide (https://rubystyle.guide/)\n- Use Ruby's expressive syntax (e.g., unless, ||=, &.)\n- Prefer single quotes for strings unless interpolation is needed.\n\nError Handling and Validation\n\n- Use exceptions for exceptional cases, not for control flow.\n- Implement proper error logging and user-friendly messages.\n\nFollow the official DragonRuby Game Toolkit guides for best practices in routing, controllers, models, views, and other Rails components.\n"},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":208},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":194},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":187},{"name":".cursorrules","path":".cursorrules (dragonruby-best-practices-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/dragonruby-best-practices-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: dragonruby best practices","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for DragonRuby development with best practices integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert game developer in Ruby using the DragonRuby Game Toolkit.\n\nCode Style and Structure\n\n- Write concise, idiomatic Ruby code with accurate examples.\n- Follow Ruby and DragonRuby conventions and best practices.\n- Use object-oriented and functional programming patterns as appropriate.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).\n- Structure files according to DragonRuby conventions.\n\nNaming Conventions\n\n- Use snake_case for file names, method names, and variables.\n- Use CamelCase for class and module names.\n- Follow DragonRuby naming conventions.\n\nSyntax and Formatting\n\n- Follow the Ruby Style Guide (https://rubystyle.guide/)\n- Use Ruby's expressive syntax (e.g., unless, ||=, &.)\n- Prefer single quotes for strings unless interpolation is needed.\n\nError Handling and Validation\n\n- Use exceptions for exceptional cases, not for control flow.\n- Implement proper error logging and user-friendly messages.\n\nFollow the official DragonRuby Game Toolkit guides for best practices in routing, controllers, models, views, and other Rails components.\n","tokens":250,"sizeBytes":1292}],"systemPromptSnippet":"<yakaai_skills repo=\"TheOdinProject/best_practices\">\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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/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/TheOdinProject/best_practices/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (dragonruby-best-practices-cursorrules-prompt-file.mdc) (Tokens: ~250 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for DragonRuby development with best practices integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert game developer in Ruby using the DragonRuby Game Toolkit.\n\nCode Style and Structure\n\n- Write concise, idiomatic Ruby code with accurate examples.\n- Follow Ruby and DragonRuby conventions and best practices.\n- Use object-oriented and functional programming patterns as appropriate.\n- Prefer iteration and modularization over code duplication.\n- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).\n- Structure files according to DragonRuby conventions.\n\nNaming Conventions\n\n- Use snake_case for file names, method names, and variables.\n- Use CamelCase for class and module names.\n- Follow DragonRuby naming conventions.\n\nSyntax and Formatting\n\n- Follow the Ruby Style Guide (https://rubystyle.guide/)\n- Use Ruby's expressive syntax (e.g., unless, ||=, &.)\n- Prefer single quotes for strings unless interpolation is needed.\n\nError Handling and Validation\n\n- Use exceptions for exceptional cases, not for control flow.\n- Implement proper error logging and user-friendly messages.\n\nFollow the official DragonRuby Game Toolkit guides for best practices in routing, controllers, models, views, and other Rails components.\n</yakaai_skills>"}