Jahanson Cc Plugins
Jahanson CC Plugins is a Claude Code plugin for the Build phase that adds Deno, JSR, and TypeScript publishing integrations with audit and LSP-aware workflows.
by jahanson · github.com/jahanson/cc-plugins
Install when you ship Deno and TypeScript to JSR and want Claude Code skills for publishing readiness, LSP-aware edits, and compliance checks.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install jahanson-cc-plugins@jahanson/cc-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:jahanson/cc-plugins") and the paste-ready config with skillselion.get_install_config("plugin:jahanson/cc-plugins").
What it does
Jahanson CC Plugins is a compact Claude Code plugin pair aimed at developers who regularly work in Deno and publish TypeScript/JavaScript packages to JSR. The bundle emphasizes integration with the Deno toolchain—LSP-aligned assistance, publishing readiness, and audit or compliance framing before modules go public—rather than generic SaaS scaffolding. Solo builders maintaining small Deno libraries or internal packages get agent behaviors that match how they already ship: validate package metadata, respect JSR conventions, and catch compliance gaps early without standing up a separate doc stack. With only two plugins, the scope is intentionally narrow compared to mega-toolboxes; it rewards builders already committed to Deno who want their Claude Code setup to mirror personal habits. Pair it with your existing deno task and CI scripts so the agent reinforces gates you would run manually before `deno publish` or JSR upload.
Highlights
- 2 plugins focused on Deno and TypeScript/JavaScript workflows
- JSR package publishing and readiness-oriented checks
- Audit and compliance hooks for Deno ecosystem releases
- LSP-aware development integration for editor-aligned agent edits
- Personal daily-driver skills rather than a broad marketplace catalog
Why builders use it
Deno developers publishing to JSR repeat the same readiness and compliance checks manually because their agent does not understand Deno-specific packaging and audit expectations.
After install, Claude Code can guide JSR publishing readiness and Deno-integrated edits so releases fail less often at the registry gate.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is jahanson-cc-plugins for?
Developers who use Deno and TypeScript daily and publish packages to JSR, wanting custom Claude Code skills and hooks they rely on regularly.
When should I use jahanson-cc-plugins?
Use it while preparing JSR releases, running audit or compliance checks, and when you want LSP-aligned Deno edits inside Claude Code.
How do I add jahanson-cc-plugins to my agent?
Add jahanson/cc-plugins as a Claude Code plugin source and enable the Deno and publishing-related plugins in your workspace settings.
Comments
Share how you use jahanson-cc-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.