Claude Code
Turn on the zynactra-ui and zynactra-access plugins in a product with one settings file.
Each library ships a Claude Code plugin whose skill loads when Claude works in its area: zynactra-ui for screens, zynactra-access for anything to do with permissions. A product that uses both commits one .claude/settings.json:
{
"extraKnownMarketplaces": {
"zynactra-ui": {
"source": { "source": "github", "repo": "zynactra/ui" },
"autoUpdate": true
},
"zynactra-access": {
"source": { "source": "github", "repo": "zynactra/access" },
"autoUpdate": true
}
},
"enabledPlugins": {
"zynactra-ui@zynactra-ui": true,
"zynactra-access@zynactra-access": true
}
}Everyone who opens the repo in Claude Code gets both after trusting the folder. The repos are private, so each person needs read access to them on GitHub.
What each plugin brings
| Plugin | Loads for | Holds Claude to |
|---|---|---|
zynactra-ui | building or reviewing UI | the house rules, the right component for the job, setup, patterns, and zynactra-ui check before it's done |
zynactra-access | endpoints, permissions, roles, admin, reviews of access code | the manifest workflow, the three checks, strict mode, the admin rules and the tests to write |
Both read the library's docs as markdown (the plugin's references, or the package's docs/ folder), so Claude follows the same pages you read here.
Cloud sessions
Claude Code on the web doesn't load marketplaces declared in a repository's settings. There, ask Claude to read node_modules/@zynactra/ui/docs and node_modules/@zynactra/access/docs before it starts, and to run npx zynactra-ui check before it finishes.