zrosenbauer
- 8 skills
- 0 followers
- 10 hours ago last updated
- ▌ NPM Namer · zrosenbauer bundleThis skill should be used when the user wants to find an available npm package name, check whether one or more names are taken on the npm registry, brainstorm name ideas for a package, or pre-flight a name against the moniker (similar-name) collision rule before publishing. Common triggers include "find me an npm name for", "is <name> available on npm", "check if these package names are taken", "brainstorm a name for my package", "help me name this npm package", and "will <name> hit moniker collision". Bundles a Node script that permutes seeds, validates syntax (via the official validate-npm-package-name package), checks the registry in parallel, and reproduces npm's moniker normalization client-side. Skip when the user wants names for crates/gems/PyPI packages (npm only — the moniker rule and registry are npm-specific), or when they want to actually publish a package (use `npm publish`).
- ▌ Svg Creator · zrosenbauer bundleThis skill should be used when the user wants to create, fix, or convert SVG assets in any project — banners, badges, icons, logos, window/IDE mockups, terminal screenshots, or diagram nodes. Common triggers include "create an SVG", "make a banner", "design an icon", "draw a logo", "fix the viewBox", "convert SVG to PNG", and "preview this SVG". Bakes in edge-to-edge viewBox discipline (`viewBox="0 0 W H"` — no padding, no offsets), hardcoded hex colors (SVG cannot read CSS variables), a Node- based local preview server for browser + chrome-devtools MCP screenshot verification, and sharp-based conversion to PNG / JPEG / WebP / AVIF. Skip when the asset is purely raster (no SVG source) or when only an existing PNG needs editing.
- ▌ Code Reviewer · zrosenbauer bundleThis skill should be used when the user wants to review code, audit a diff, get a second opinion on changes, or run an adversarial review of files in the current working tree. Common triggers include "review this code", "audit this diff", "find issues in", "second opinion on this", "harsh review of", "adversarial review", and "security review of". Picks one or more reviewer personas (adversarial, security, architecture, performance). Reviews local files, `git diff`, or `git diff --staged` only — does not fetch external content. Runs in one of four modes: single-agent (one persona in the current agent), cross-model handoff (independent second opinion via another local AI CLI, with secret-shield preflight + prompt-shield wrap), multi-bg-agent (one persona per parallel background subagent), or agent-team (Claude Code Teams or equivalent on supporting agents). Skip when the user wants formatting fixes (use a linter) or refactoring patterns (use ts-best-practices or ts-best-practices-functional).
- ▌ Skill Creator · zrosenbauer bundleThis skill should be used when the user wants to create a new agent skill, scaffold a SKILL.md, validate an existing skill against repo rules, or refactor a skill to match this monorepo's conventions. Common triggers include "build a skill for X", "create a new skill", "scaffold a skill", "add a skill that does Y", "make me a skill", "audit this skill against our rules", and "refactor this skill to match repo conventions". Enforces kebab-case naming, verbatim trigger phrases, and selective XML for example boundaries. Skip when modifying source code, debugging an existing skill, or writing non-skill markdown.
- ▌ Skill Reviewer · zrosenbauer bundleThis skill should be used when the user wants to review, audit, or sanity-check an existing agent skill in this repo against authoring conventions. Common triggers include "review the X skill", "audit this skill", "check skill X against repo conventions", "is this skill any good", "second opinion on skill X", "sanity check skill X", and "review skill X before publishing". Produces a severity-tiered report (error / warn / info) with a Clean section even on pass, and classifies the skill type. Skip when authoring a brand-new skill (use skill-creator) or running general code review (use code-reviewer).
- ▌ Skill Portability · zrosenbauer bundleThis skill should be used when the user wants to check whether an agent skill is portable across providers. Common triggers include "is this skill cross-provider safe", "will my skill work in cursor", "audit skill compatibility", "check if this loads in codex", and "which providers support this skill". Spawns one agent per provider in parallel using bundled provider-doc snapshots (refreshed on cadence — never fetched at runtime) and produces a compatibility matrix plus a COMPAT.md report. Skip when authoring a new skill (use skill-creator) or rerunning baselines (use skill-eval).
- ▌ TS Best Practices · zrosenbauer bundleThis skill should be used when the user wants to write, review, or refactor TypeScript code to follow industry best practices. Common triggers include "follow ts best practices", "review this typescript", "fix the typescript style", "make this idiomatic typescript", "apply typescript conventions", and "audit this ts file". Bakes in branded types, discriminated unions, ts-pattern for multi-branch logic, JSDoc on exports, kebab-case file naming, and *Params/*Options object-arg conventions. Skip when the user wants pure functional refactors (use ts-best-practices-functional) or is writing framework components (React/Vue/Svelte have different conventions).
- ▌ TS Best Practices Functional · zrosenbauer bundleThis skill should be used when the user wants to refactor TypeScript code to functional patterns or write new code following functional doctrine. Common triggers include "make this functional", "remove the class", "use Result instead of throw", "stop mutating this", and "refactor to factory function". Bakes in factory functions over classes, Result<T,E> over exceptions, immutable state via spread/map/filter, and pure functions composed in pipelines. Skip when the user wants general TS hygiene (use ts-best-practices), the class wraps a stateful SDK (PrismaClient, Octokit, WebSocket), or a framework requires a class.