s-celles-plugins-community

Claude Plugins Community

Repository: s-celles/s-celles-plugins-community

A community-maintained marketplace for Claude Code plugins.

Included Plugins

LSP plugins

Plugin	Language	Extension	LSP
julia-lsp/	Julia	.jl	LanguageServer.jl

Others marketplaces with various LSP plugins

• https://github.com/boostvolt/claude-code-lsps

Others plugins

Plugin	Description	Status

Included Commands

Commands	Description	Status

Included Skills

Skill	Description	Status
julia-devlopment/	Julia Development Skill	v0.1.0

Included Agents

Commands	Description	Status

Quick Setup

Step 1: Install LanguageServer.jl

julia --project=~/.julia/environments/claude-code-lsp -e '
using Pkg
Pkg.add(["LanguageServer", "SymbolServer", "StaticLint"])
'

Step 2: Load the Plugin

Option A: Development Mode (Recommended for Testing)

Start Claude Code with the plugin loaded:

claude --plugin-dir ./julia-lsp

Option B: Local Marketplace Installation

This repository includes a marketplace configuration. Add it as a local marketplace:

/plugin marketplace add /path/to/julia-lsp-complete
/plugin install julia-lsp@julia-lsp-marketplace

Option C: Project-Scoped Installation

claude plugin install ./julia-lsp --scope project

Step 3: Browse Available Plugins

After registering the marketplace, browse available plugins:

/plugin marketplace list julia-lsp-marketplace

This shows all plugins with their versions, descriptions, and categories.

Step 4: Verify Installation

/plugin list

You should see julia-lsp listed and enabled.

Note: The command /plugin install ./julia-lsp will show "Marketplace not found" error. This is because /plugin install expects a marketplace-registered plugin. Use the methods above.

Managing Plugins

Update a plugin to the latest version:

/plugin update julia-lsp

Remove a plugin:

/plugin remove julia-lsp

Testing LSP Features

Run the Test Project

cd julia-test-project

# Run the demo
julia --project=. src/main.jl

# Run unit tests
julia --project=. test/runtests.jl

Test LSP in Claude Code

Open files from julia-test-project/ in Claude Code and try:

Feature	Prompt
Go to Definition	"Go to the definition of Vector2D"
Find References	"Find all references to magnitude"
Hover	"What's the type signature of fibonacci?"
Document Symbols	"Show me the outline of MathUtils.jl"
Diagnostics	"Check DiagnosticsTest.jl for errors"

Package Contents

julia-lsp-complete/
├── README.md                    # This file
├── julia-lsp/                   # Claude Code Plugin
│   ├── .claude-plugin/
│   │   └── plugin.json          # Plugin metadata
│   ├── .lsp.json                # LSP server config
│   ├── hooks/
│   │   ├── hooks.json           # Hook definitions
│   │   └── check-julia-lsp.sh   # Auto-setup script
│   └── README.md                # Plugin documentation
│
└── julia-test-project/          # Test Project
    ├── Project.toml             # Julia project config
    ├── src/
    │   ├── MathUtils.jl         # Main module
    │   ├── main.jl              # Entry point
    │   ├── quick_test.jl        # LSP feature tests
    │   └── DiagnosticsTest.jl   # Error detection tests
    ├── test/
    │   └── runtests.jl          # Unit tests
    └── README.md                # Test instructions

Troubleshooting

"No LSP server available"

1. Ensure Julia is in PATH:

   which julia
   

2. Verify LanguageServer.jl works:

   julia --project=~/.julia/environments/claude-code-lsp -e 'using LanguageServer; println("OK")'
   

3. Try with feature flag:

   ENABLE_LSP_TOOL=1 claude
   

Slow Startup

Julia LSP takes 30-60 seconds on first start. For faster startup, precompile:

using PackageCompiler
create_sysimage(
    [:LanguageServer, :SymbolServer, :StaticLint],
    sysimage_path=expanduser("~/.julia/languageserver.so")
)

Then update julia-lsp/.lsp.json to use -J~/.julia/languageserver.so.

Marketplace Validation

For maintainers, validate the marketplace structure before publishing:

./scripts/validate-marketplace.sh

This checks:

• marketplace.json exists and is valid JSON
• All plugin source paths resolve to directories
• Each plugin has a plugin.json file
• All versions follow SemVer format

How to Help Fix Upstream Issues