Fenix plugin for Claude

Patent automation for Claude Code / Cowork. Bundles:

• The Fenix MCP connector — https://claude.fenix.ai/api/plugin (read + draft tools: get_project, save_project, print_patent, install_fenix_skills, and more).
• The patent skills — fenix-application, fenix-office-action, fenix-project — shipped as a static snapshot so they work immediately, with a /fenix-install command to refresh the firm-customized, latest versions from the server.

One key, nothing else

You provide a single API key. The server infers your firm — client and database — from that key, so you never configure a database or client name.

Install (no git required)

The marketplace is served over plain HTTPS and the plugin is distributed via npm, so end users never touch git:

1. Add the marketplace and install the plugin:

   claude plugin marketplace add https://claude.fenix.ai/marketplace.json
   claude plugin install fenix@fenix

2. Set your key (see /fenix-setup for guided steps):
   • macOS/Linux: export FENIX_API_KEY="<your key>" in ~/.zshrc / ~/.bashrc
   • Windows: setx FENIX_API_KEY "<your key>" Restart Claude Code so the connector picks up the key.
3. (Optional) /fenix-install — refresh the skills to your firm's latest customized versions.

Local/dev install (from a clone of this repo, no npm needed): claude plugin marketplace add <path-to-Project-Management> then claude plugin install fenix@fenix — this uses the repo-root .claude-plugin/marketplace.json (relative source).

Publishing a new version (maintainers)

The plugin ships to users as the npm package fenix-claude-plugin, referenced by the HTTPS marketplace at https://claude.fenix.ai/marketplace.json (served by back-end/pages/api/marketplace.ts).

1. Regenerate the bundled snapshot: cd back-end && npm run gen:snapshot.
2. Bump the version in three places (keep them identical):
   • fenix-plugin/package.json → version
   • fenix-plugin/.claude-plugin/plugin.json → version
   • back-end/pages/api/marketplace.ts → PLUGIN_VERSION
3. Publish: cd fenix-plugin && npm publish (unscoped public package — no scope/org needed).
4. Deploy the back-end so /marketplace.json and the /api/plugin connector are live.

Verify the npm contents before publishing with npm pack --dry-run.

Commands

• /fenix-setup — guided API-key configuration.
• /fenix-install — pull the latest, firm-customized skills from the server.

How the skills stay in sync

The bundled skills/ snapshot is generated from the same base files the server serves (back-end/skills/…) — it is never hand-edited. Editing a base file and regenerating updates both the server's dynamic install and this static snapshot, so the two never drift. See back-end/skills/README.md for the source of truth and the regeneration script.