First commit

Author: ericdallo

.eca-plugin/marketplace.json

@@ -0,0 +1,44 @@
+{
+  "plugins": [
+    {
+      "name": "clojure-review",
+      "description": "Principal Clojure(Script) code reviewer subagent with structured feedback on design, state management, idioms, and testing",
+      "source": "plugins/clojure-review",
+      "category": "Development",
+      "tags": ["clojure", "review", "subagent", "quality"],
+      "author": "zikajk",
+      "icon": "🔍",
+      "featured": true
+    },
+    {
+      "name": "fp-style",
+      "description": "Coding style skill enforcing functional-leaning, idiomatic conventions with lightweight data structures across any language",
+      "source": "plugins/fp-style",
+      "category": "Development",
+      "tags": ["style", "functional", "skill", "conventions"],
+      "author": "davidvujic",
+      "icon": "λ",
+      "featured": true
+    },
+    {
+      "name": "agent-orchestration",
+      "description": "Subagent-based workflow for implementing planned changes with consistent, functional-leaning coding style",
+      "source": "plugins/agent-orchestration",
+      "category": "Workflow",
+      "tags": ["subagent", "implementation", "orchestration", "refactoring"],
+      "author": "davidvujic",
+      "icon": "🎭",
+      "featured": true
+    },
+    {
+      "name": "notify-hooks",
+      "description": "Desktop sound notifications when ECA finishes responding or needs tool call approval",
+      "source": "plugins/notify-hooks",
+      "category": "Productivity",
+      "tags": ["hooks", "notifications", "sound", "desktop"],
+      "author": "ericdallo",
+      "icon": "🔔",
+      "featured": false
+    }
+  ]
+}

.github/workflows/deploy.yml

@@ -0,0 +1,53 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+          cache-dependency-path: website/package-lock.json
+
+      - name: Install dependencies
+        working-directory: website
+        run: npm ci
+
+      - name: Build
+        working-directory: website
+        run: npm run build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: website/dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -0,0 +1,21 @@
+# Dependencies
+node_modules/
+
+# Build output
+website/dist/
+dist/
+
+# Environment
+.env
+.env.*
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Editor
+.vscode/
+.idea/
+*.swp
+*.swo
+*~

CONTRIBUTING.md

@@ -0,0 +1,106 @@
+# Contributing to ECA Plugins
+
+Thank you for your interest in contributing to the ECA plugin marketplace! This guide walks you through the process of submitting a new plugin.
+
+## Plugin structure
+
+Each plugin lives under `plugins/<plugin-name>/` and can provide any combination of:
+
+```
+plugins/my-plugin/
+├── skills/              # Skill directories (each subfolder is a skill)
+│   └── my-skill/
+│       └── my-skill.md
+├── agents/              # Agent definitions (Markdown files)
+│   └── my-agent.md
+├── commands/            # Custom commands (Markdown files)
+│   └── my-command.md
+├── rules/               # Rule files applied to conversations
+│   └── my-rule.md
+├── hooks/               # Hook definitions
+│   └── hooks.json
+├── .mcp.json            # MCP server definitions
+├── eca.json             # Arbitrary config overrides
+└── README.md            # Documentation (displayed on the marketplace website)
+```
+
+You don't need all of these — include only the components your plugin provides.
+
+## Adding a plugin
+
+### 1. Create the plugin directory
+
+```bash
+mkdir -p plugins/my-plugin
+```
+
+### 2. Add your plugin components
+
+Add the files for your plugin (skills, agents, rules, etc.) following the structure above.
+
+### 3. Add a README
+
+Create `plugins/my-plugin/README.md` describing what your plugin does, how to use it, and any configuration options.
+
+### 4. Register in the marketplace
+
+Add an entry to `.eca-plugin/marketplace.json`:
+
+```json
+{
+  "name": "my-plugin",
+  "description": "A short description of what your plugin does",
+  "source": "plugins/my-plugin",
+  "category": "Development",
+  "tags": ["relevant", "tags"],
+  "author": "Your Name",
+  "icon": "🔧"
+}
+```
+
+**Fields:**
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `name` | Yes | Unique plugin identifier (kebab-case) |
+| `description` | Yes | Short description (one sentence) |
+| `source` | Yes | Path to the plugin directory (relative to repo root) |
+| `category` | Yes | One of: `Development`, `Productivity`, `Documentation`, `DevOps`, `Data`, `Design` |
+| `tags` | Yes | Array of relevant tags for search/filtering |
+| `author` | Yes | Author name or organization |
+| `icon` | No | Emoji icon for the plugin card |
+| `featured` | No | Set to `true` for featured plugins (maintainers only) |
+
+### 5. Open a pull request
+
+Submit a PR with your plugin. We'll review it for:
+
+- **Usefulness** — Does it provide value to ECA users?
+- **Quality** — Are the skills/agents/rules well-written?
+- **Safety** — Does it follow responsible AI practices?
+- **Documentation** — Is the README clear and helpful?
+
+## Guidelines
+
+- Keep plugin names short and descriptive (kebab-case)
+- Write clear, concise skill/agent prompts
+- Include examples in your README
+- Test your plugin locally before submitting (add it as a local source in your ECA config)
+- One plugin per PR unless they're closely related
+
+## Testing locally
+
+You can test your plugin by pointing ECA to your local clone:
+
+```json
+{
+  "plugins": {
+    "local": { "source": "/path/to/eca-plugins" },
+    "install": ["my-plugin"]
+  }
+}
+```
+
+## Questions?
+
+Open an issue or reach out on [Slack](https://join.slack.com/t/eca-dev/shared_invite/zt-34p6n16s1-_MwEJMr2F~gD2ol4gzntqw).