lsFusion AI skills

Agent Skills for working with lsFusion, packaged as a Claude Code plugin and bundled with the official ai.lsfusion.org MCP server.

What's inside

Skill	Purpose
lsfusion-dev	Set up, run, and verify lsFusion applications locally (Windows). Writing/editing .lsf, scaffolding, starting the app server, diagnosing startup/form issues.
lsfusion-deploy	Deploy an lsFusion app to a remote Linux server: provisioning, packaging the jar, systemd units, HTTPS via certbot, pulling the prod PostgreSQL DB locally.
lsfusion-eval	Run lsFusion code against a running server over HTTP (/eval, /exec, /eval/action) and inspect what's actually deployed.

ai-skills/
├── .claude-plugin/
│   ├── marketplace.json     # marketplace manifest (repo root → /plugin marketplace add)
│   └── plugin.json          # plugin definition
├── .mcp.json                # bundles the ai.lsfusion.org MCP server
└── skills/
    ├── lsfusion-dev/
    ├── lsfusion-deploy/
    └── lsfusion-eval/

Install in Claude Code (interactive)

/plugin marketplace add lsfusion/ai-skills
/plugin install lsfusion-ai-skills

This installs all three skills and registers the lsfusion-ai MCP server (https://ai.lsfusion.org/mcp). On first use Claude Code may prompt you to authenticate with the server.

Install when /plugin is unavailable (CLI)

Some environments (embedded clients, Cowork, etc.) don't expose the interactive /plugin command — you'll see "/plugin isn't available in this environment." The claude CLI does exactly the same thing non-interactively:

claude plugin marketplace add lsfusion/ai-skills
claude plugin install lsfusion-ai-skills@lsfusion

Verify and manage:

claude plugin list                                  # confirm it's enabled
claude plugin details lsfusion-ai-skills@lsfusion   # show skills + MCP inventory
claude plugin marketplace update lsfusion           # pull the latest commit later

Uninstall / remove:

claude plugin uninstall lsfusion-ai-skills@lsfusion
claude plugin marketplace remove lsfusion

Skills and the lsfusion-ai MCP server become available in new Claude Code sessions (the MCP server may prompt for authentication on first use).

After claude plugin update / marketplace update: a session that is already open keeps the old SKILL.md it loaded at startup — instructions refresh only in a new session. The updated scripts (e.g. scripts/lsfdev.ps1) are available immediately, though: they are resolved from the plugin cache by path at call time, and the cache path changes with the version (...\lsfusion-ai-skills\<version>\skills\...) — so re-resolve the script path instead of reusing one cached earlier in the conversation.

Use the skills without the plugin

The skills/ folder follows the open Agent Skills format, so it works anywhere:

• Claude Code (manual): copy a skill folder into ~/.claude/skills/ (global) or .claude/skills/ (per project). Add the MCP server separately with claude mcp add --transport http lsfusion-ai https://ai.lsfusion.org/mcp.
• Claude.ai / Claude Desktop: zip a skill folder and upload it under Settings → Capabilities → Skills.
• Claude API / Agent SDK: mount the skill folder into the agent's working directory.

The MCP server in other tools

Bundling MCP via the plugin is a Claude Code feature. Elsewhere, add https://ai.lsfusion.org/mcp manually:

• Claude.ai / Desktop — Settings → Connectors → add a custom connector.
• ChatGPT — connector settings.
• Codex — add an [mcp_servers.lsfusion-ai] section to ~/.codex/config.toml.

License

Apache-2.0