Skip to content

add(plugin): imax-view skill - #37

Merged
anistark merged 1 commit into
mainfrom
add-imax-view
Aug 26, 2026
Merged

anistark merged 1 commit into
mainfrom
add-imax-view

Conversation

@anistark

Copy link
Copy Markdown
Contributor

Add Plugin

Plugin name:
Source: https://github.com/anistark/imax-view
License: MIT
Category: design
Type / tags: ["skills", "design-system", "design-tokens", "css"]

Using other? If you set the category or a type tag to other because nothing else fits, please briefly explain why in the description below — it helps us decide whether to add a new category/type later.

Checklist

Uncheck any item that does not apply or has not been completed.

  • I have read and understood the contributing guidelines
  • Plugin has a valid .claude-plugin/plugin.json manifest
  • Plugin has a README.md
  • Plugin has a LICENSE
  • Plugin name is kebab-case
  • category is set to one of the allowed values
  • tags includes at least one component type (skills/agents/hooks/commands/mcp-servers/lsp-servers/integration/other)
  • Plugin file added to plugins/ directory (do not edit marketplace.json)
  • Tested locally with /plugin marketplace add and /plugin install

What does this plugin do?

It treats the canvas the way IMAX 15/70 treats the screen: taller than you expect, larger than you expect, and quiet everywhere except one place.

@github-actions

Copy link
Copy Markdown
Contributor

Plugin Validation ❌

Check Status
Duplicate check ✅ success
Schema validation ❌ failure
Marketplace build ⏭️ skipped

Errors

  • plugins/llm-box.json: Invalid or missing source type git. Must be one of: github, url, git-subdir, npm

@anistark
anistark merged commit 0172183 into main Aug 26, 2026
1 check failed
@anistark
anistark deleted the add-imax-view branch August 26, 2026 07:25
anistark added a commit that referenced this pull request Aug 26, 2026
#38)

## Summary

`plugins/llm-box.json` declares `"source": "git"`, which is not one of
the source types the validator accepts.
`.github/workflows/validate-plugin.yml` allows `github`, `url`,
`git-subdir` and `npm`, so the schema step fails with:

```
plugins/llm-box.json: Invalid or missing source type `git`. Must be one of: github, url, git-subdir, npm
```

The catch is that the schema step loops over every file in `plugins/`,
not just the ones a PR touches:

```bash
for f in plugins/*.json; do
```

So this single entry fails validation on **every** PR that touches
`plugins/`, no matter what that PR changes. It is currently blocking
#37, and it is the only one of 305 entries with an invalid source type
(the rest are 226 `git-subdir`, 74 `github`, 3 `url`, 2 `npm`).

It landed in #34, where this same check was already in place and already
failing. There is no required status check on the repo, so it merged
anyway.

### The fix

Switch the entry to a `github` source, matching the 74 other
GitHub-hosted entries and the shape documented in `CONTRIBUTING.md`.

The repo has also been renamed from `alib8b8/llm-box` to
`alib8b8/aflare` since the entry was added. GitHub's redirect still
resolves the old name, but pointing at the canonical one avoids a break
if the old name is ever reclaimed.

### Verified locally

- Replayed the full schema validation over all 305 entries: 0 errors.
- `./scripts/build-marketplace.sh` succeeds (305 plugins, 96 authors).
- `marketplace.json` deliberately not committed, since the
build-marketplace workflow regenerates it on push to `main`.

### Follow-ups, not in this PR

- The entry pins `"version": "0.3.0"`, but upstream is on `v0.11.0`
(released 2026-08-26). Per `CONTRIBUTING.md`, `/plugin update` compares
the installed version against the registry, so anyone who installed
`llm-box` is stuck and gets "already at the latest version". The
`llm-box` name and description are also stale branding after the rename
to `aflare`.
- The validation loop is worth scoping to changed files, or the check
made required, so one broken entry cannot merge and then block every PR
behind it.

### Type of change

- [ ] Add a plugin
- [ ] Update a plugin
- [ ] Remove a plugin
- [x] Marketplace / registry change (schema, validation, `plugins/`
tooling)
- [ ] Site / docs change (landing page, README, content)
- [ ] CI / workflow / repo tooling
- [x] Bug fix
- [ ] Other

### Checklist

- [x] I have read and understood the [contributing
guidelines](../CONTRIBUTING.md)
- [x] Changes are scoped and focused on a single concern
- [x] Tested locally where applicable
- [ ] Updated relevant docs (README, site content, etc.) if behavior
changed
- [x] Did **not** hand-edit `marketplace.json` (it is generated)

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant