set up a proper claude plugin directory

[MichaelDoyle]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @MichaelDoyle, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Claude plugin setup by introducing a standardized directory structure for individual plugins. The primary goal is to improve organization and maintainability by centralizing plugin-specific metadata and configurations into their own dedicated folders, rather than embedding them directly within the main marketplace.json file. This change promotes modularity and prepares the system for easier management of multiple plugins.

Highlights

• Plugin Directory Structure Refactor: The pull request introduces a new, dedicated directory structure for Claude plugins, moving from a monolithic configuration to a more modular approach.
• marketplace.json Simplification: The main marketplace.json file has been significantly streamlined, removing detailed plugin metadata and MCP server configurations.
• Dedicated Plugin Configuration Files: New files (plugin.json, .mcp.json, skills) are now used within claude-plugins/firebase to store specific metadata and configurations for the Firebase plugin.
• Updated Plugin Source Path: The source field in marketplace.json for the Firebase plugin now correctly points to its new dedicated directory: ./claude-plugins/firebase.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the Claude plugin configuration into a more modular directory structure, which is a great improvement for maintainability. I have a couple of suggestions to further improve the changes. First, I recommend pinning the version of firebase-tools to ensure stability. Second, a minor point about adding a trailing newline to the skills file to adhere to common conventions.