Stats
Actions
Tags
Always-on conventions for TypeScript monorepos covering code style, JSDoc, markdown structure, security, and Vitest testing rules.
How this skill is triggered — by the user, by Claude, or both
Slash command
/toolkit:conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill ships the always-on rules that the template repo uses under
This skill ships the always-on rules that the template repo uses under
.claude/rules/. When the plugin is installed in another project, the same
files load on demand from here instead.
Read the file that matches what you are doing:
rules/code-style.md for ESM conventions, naming, imports, and exports.rules/jsdoc.md for the always-on JSDoc essentials. The full reference
lives in the separate jsdoc skill.rules/markdown.md for markdown structure. The documentation and
humanizer skills cover writing voice and SEO.rules/security.md for secrets, input validation at trust
boundaries, and safe shell use.rules/testing.md for Vitest patterns and what to test.rules/usa-english.md for the USA English spelling
convention used across code, comments, and docs.If a rule conflicts with a project-specific instruction in AGENTS.md or
CLAUDE.md, the project instruction wins.
npx claudepluginhub stijnvanhulle/template --plugin toolkitApplies language-specific style guides for TypeScript, Python, Go, JavaScript, and HTML/CSS when writing, reviewing, refactoring, or setting up code files to ensure consistency and best practices.
Guides ESLint built-in rule configuration, severity levels, and disabling strategies for JavaScript projects. Useful for linting setup and code quality enforcement.
Sets up ast-grep in TypeScript codebases with rules detecting anti-patterns, enforcing best practices, and preventing bugs. Creates sgconfig.yml, rule files, and tests for structural linting, legacy bans, and ratchet gates.