{"owner":"Automattic","repo":"lean","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1278,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"lean":{"command":"npx","args":["-y","@modelcontextprotocol/server-lean"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (clean-code.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/Automattic/lean/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/Automattic/lean/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/Automattic/lean/HEAD/.claude-plugin/plugin.json)",".cursorrules (clean-code.mdc)":"# Clean Code Guidelines\n\n## Constants Over Magic Numbers\n- Replace hard-coded values with named constants\n- Use descriptive constant names that explain the value's purpose\n- Keep constants at the top of the file or in a dedicated constants file\n\n## Meaningful Names\n- Variables, functions, and classes should reveal their purpose\n- Names should explain why something exists and how it's used\n- Avoid abbreviations unless they're universally understood\n\n## Smart Comments\n- Don't comment on what the code does - make the code self-documenting\n- Use comments to explain why something is done a certain way\n- Document APIs, complex algorithms, and non-obvious side effects\n\n## Single Responsibility\n- Each function should do exactly one thing\n- Functions should be small and focused\n- If a function needs a comment to explain what it does, it should be split\n\n## DRY (Don't Repeat Yourself)\n- Extract repeated code into reusable functions\n- Share common logic through proper abstraction\n- Maintain single sources of truth\n\n## Clean Structure\n- Keep related code together\n- Organize code in a logical hierarchy\n- Use consistent file and folder naming conventions\n\n## Encapsulation\n- Hide implementation details\n- Expose clear interfaces\n- Move nested conditionals into well-named functions\n\n## Code Quality Maintenance\n- Refactor continuously\n- Fix technical debt early\n- Leave code cleaner than you found it\n\n## Testing\n- Write tests before fixing bugs\n- Keep tests readable and maintainable\n- Test edge cases and error conditions\n\n## Version Control\n- Write clear commit messages\n- Make small, focused commits\n- Use meaningful branch names"},"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/Automattic/lean/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/Automattic/lean/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/Automattic/lean/HEAD/.claude-plugin/plugin.json)",".cursorrules (clean-code.mdc)":"# Clean Code Guidelines\n\n## Constants Over Magic Numbers\n- Replace hard-coded values with named constants\n- Use descriptive constant names that explain the value's purpose\n- Keep constants at the top of the file or in a dedicated constants file\n\n## Meaningful Names\n- Variables, functions, and classes should reveal their purpose\n- Names should explain why something exists and how it's used\n- Avoid abbreviations unless they're universally understood\n\n## Smart Comments\n- Don't comment on what the code does - make the code self-documenting\n- Use comments to explain why something is done a certain way\n- Document APIs, complex algorithms, and non-obvious side effects\n\n## Single Responsibility\n- Each function should do exactly one thing\n- Functions should be small and focused\n- If a function needs a comment to explain what it does, it should be split\n\n## DRY (Don't Repeat Yourself)\n- Extract repeated code into reusable functions\n- Share common logic through proper abstraction\n- Maintain single sources of truth\n\n## Clean Structure\n- Keep related code together\n- Organize code in a logical hierarchy\n- Use consistent file and folder naming conventions\n\n## Encapsulation\n- Hide implementation details\n- Expose clear interfaces\n- Move nested conditionals into well-named functions\n\n## Code Quality Maintenance\n- Refactor continuously\n- Fix technical debt early\n- Leave code cleaner than you found it\n\n## Testing\n- Write tests before fixing bugs\n- Keep tests readable and maintainable\n- Test edge cases and error conditions\n\n## Version Control\n- Write clear commit messages\n- Make small, focused commits\n- Use meaningful branch names"},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/Automattic/lean/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/Automattic/lean/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":194},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/Automattic/lean/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/Automattic/lean/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":180},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/Automattic/lean/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/Automattic/lean/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":173},{"name":".cursorrules","path":".cursorrules (clean-code.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/clean-code.mdc","title":"Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.","category":"cursor-rule","format":"markdown","content":"# Clean Code Guidelines\n\n## Constants Over Magic Numbers\n- Replace hard-coded values with named constants\n- Use descriptive constant names that explain the value's purpose\n- Keep constants at the top of the file or in a dedicated constants file\n\n## Meaningful Names\n- Variables, functions, and classes should reveal their purpose\n- Names should explain why something exists and how it's used\n- Avoid abbreviations unless they're universally understood\n\n## Smart Comments\n- Don't comment on what the code does - make the code self-documenting\n- Use comments to explain why something is done a certain way\n- Document APIs, complex algorithms, and non-obvious side effects\n\n## Single Responsibility\n- Each function should do exactly one thing\n- Functions should be small and focused\n- If a function needs a comment to explain what it does, it should be split\n\n## DRY (Don't Repeat Yourself)\n- Extract repeated code into reusable functions\n- Share common logic through proper abstraction\n- Maintain single sources of truth\n\n## Clean Structure\n- Keep related code together\n- Organize code in a logical hierarchy\n- Use consistent file and folder naming conventions\n\n## Encapsulation\n- Hide implementation details\n- Expose clear interfaces\n- Move nested conditionals into well-named functions\n\n## Code Quality Maintenance\n- Refactor continuously\n- Fix technical debt early\n- Leave code cleaner than you found it\n\n## Testing\n- Write tests before fixing bugs\n- Keep tests readable and maintainable\n- Test edge cases and error conditions\n\n## Version Control\n- Write clear commit messages\n- Make small, focused commits\n- Use meaningful branch names","frontmatter":{"description":"Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.","globs":["**/*"],"alwaysApply":false},"tokens":378,"sizeBytes":1637}],"systemPromptSnippet":"<yakaai_skills repo=\"Automattic/lean\">\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/Automattic/lean/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/Automattic/lean/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/Automattic/lean/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (clean-code.mdc) (Tokens: ~378 | Category: cursor-rule) -->\n# Clean Code Guidelines\n\n## Constants Over Magic Numbers\n- Replace hard-coded values with named constants\n- Use descriptive constant names that explain the value's purpose\n- Keep constants at the top of the file or in a dedicated constants file\n\n## Meaningful Names\n- Variables, functions, and classes should reveal their purpose\n- Names should explain why something exists and how it's used\n- Avoid abbreviations unless they're universally understood\n\n## Smart Comments\n- Don't comment on what the code does - make the code self-documenting\n- Use comments to explain why something is done a certain way\n- Document APIs, complex algorithms, and non-obvious side effects\n\n## Single Responsibility\n- Each function should do exactly one thing\n- Functions should be small and focused\n- If a function needs a comment to explain what it does, it should be split\n\n## DRY (Don't Repeat Yourself)\n- Extract repeated code into reusable functions\n- Share common logic through proper abstraction\n- Maintain single sources of truth\n\n## Clean Structure\n- Keep related code together\n- Organize code in a logical hierarchy\n- Use consistent file and folder naming conventions\n\n## Encapsulation\n- Hide implementation details\n- Expose clear interfaces\n- Move nested conditionals into well-named functions\n\n## Code Quality Maintenance\n- Refactor continuously\n- Fix technical debt early\n- Leave code cleaner than you found it\n\n## Testing\n- Write tests before fixing bugs\n- Keep tests readable and maintainable\n- Test edge cases and error conditions\n\n## Version Control\n- Write clear commit messages\n- Make small, focused commits\n- Use meaningful branch names\n</yakaai_skills>"}