plugin-local

Swap Bryllen's plugin marketplace and npm package to local sources for testing.

2|Updated Feb 9, 2026

Search Tags:#npm #claude-code #development-workflow #plugin-marketplace #local-testing #testing-environment #bryllen

Ready to run

npx skills add https://github.com/madebynoam/bryllen --skill plugin-local

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-local
Source: https://github.com/madebynoam/bryllen/tree/main/.claude/skills/plugin-local
Command: npx skills add https://github.com/madebynoam/bryllen --skill plugin-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This approach lets developers test Bryllen changes in isolation by swapping the plugin marketplace and npm package to local sources, eliminating the need to publish or install from GitHub during development.

Core Features & Use Cases

Local testing of plugin functionality and CLI workflows before releasing to production.
End-to-end validation of project scaffolding, runtime behavior, and integration with Claude Code.
Use Case: Validate that changing the Bryllen runtime or CLI templates works in a consumer project without pushing changes.

Quick Start

Run the local plugin swap steps to point Claude Code to the local Bryllen repository and test with /bryllen-new

Frequently Asked Questions about plugin-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I test local plugin changes in a consumer project before publishing to npm?▼

Testing local npm package changes involves swapping the plugin marketplace to local sources. This lets you validate runtime behavior in a consumer project without needing to publish or install from GitHub during development.

What is local plugin swapping for development workflows?▼

Local plugin swapping is a testing mechanism that redirects the plugin marketplace and npm package to local sources. It enables developers to validate project scaffolding and runtime behavior in isolation before pushing changes to production.

Do I need to restart Claude Code after swapping to a local plugin?▼

Yes, restarting Claude Code is required for the local plugin swap to take effect. The swap updates consumer projects to point to the local repository, and the restart ensures the new configuration loads properly.

Can I validate Bryllen CLI template changes without pushing to a remote repository?▼

Yes, swapping to local sources lets you validate Bryllen runtime or CLI template changes directly in a consumer project. This eliminates the need to push changes or install from GitHub during your development and testing workflow.

What prerequisites are needed for local testing of plugin functionality?▼

Local testing of plugin functionality requires a consumer project path and a local repository. These components allow the swap mechanism to redirect the marketplace and package sources for isolated validation.