Loading...
Loading...
Found 25 Skills
Build and publish npm packages using Bun as the primary toolchain with npm-compatible output. Use when the user wants to create a new npm library, set up a TypeScript package for publishing, configure build/test/lint tooling for a package, fix CJS/ESM interop issues, or publish to npm. Covers scaffolding, strict TypeScript, Biome + ESLint linting, Vitest testing, Bunup bundling, and publishing workflows. Keywords: npm, package, library, publish, bun, bunup, esm, cjs, exports, typescript, biome, vitest, changesets.
Generate the stable Paperclip release changelog at releases/v{version}.md by reading commits, changesets, and merged PR context since the last stable tag.
Ecto patterns for Phoenix/Elixir apps. Covers schemas, changesets, migrations, queries, Ecto.Multi, transactions, constraints, associations, pagination, tenant partitioning, performance, and testing.
CLI tool for automated changeset-based releases with AI-generated descriptions. Use when the user needs to release a package, create changesets, bump versions, or automate npm publishing workflows. Triggers include requests to "release a package", "create a changeset", "publish to npm", "bump the version", "automate releases", or any task involving version management and package publishing for repositories using the changesets workflow.
The darkmatter TypeScript toolchain contract: Bun catalogs, Effect 4, effect-orpc, Postgres-first data, tsgo, Vitest, oxlint/oxfmt, changesets, Alchemy deploys, and required checks. Use when writing, fixing, building, or shipping TypeScript in a darkmatter repo. Use codebase-design for module boundaries and effect-typescript for deep Effect patterns.
This skill should be used when the user asks to "add a database table", "create a new context", "query the database", "add a field to a schema", "validate form input", "fix N+1 queries", "preload this association", "separate these concerns", or mentions Repo, changesets, migrations, Ecto.Multi, has_many, belongs_to, transactions, query composition, or how contexts should talk to each other.
Ecto schemas, changesets, queries, migrations, and database patterns for Elixir applications
Evaluate changesets, task breakdowns, or code diffs for scope bloat, architectural drift, and regression risks.
Guide for testing workflows and code generation commands in Biome. Use when running tests, managing snapshots, creating changesets, or generating code. Examples:<example>User needs to run snapshot tests for a lint rule</example><example>User wants to create a changeset for a PR</example><example>User needs to regenerate analyzer code after changes</example>
Scaffolds a production-ready TypeScript CLI project with ESM, tsdown, vitest, oxlint, oxfmt, changesets, GitHub Actions, and an agent skill definition. Use when creating a new CLI tool, bootstrapping a TypeScript project, scaffolding a node CLI, starting a new npm package, or asking "scaffold a CLI project."
Decompose settled changesets into a verifiable DAG and persist tasks to the configured tracker via split-tasks and tracking-tasks.
Use when packaging Spree 6 React dashboard customizations as a redistributable npm plugin (optionally paired with a Rails extension gem) that other Spree stores install — scaffolding with `npx @spree/cli plugin new`, file routes and route collisions, peerDependencies against `@spree/dashboard-core`/`-ui`, prebuilt vs source publishing, `sideEffects`, the `spree.dashboard.plugin` package.json marker, auto-discovery via `virtual:spree-dashboard-plugins` vs an explicit whitelist, Tailwind class scanning, `definePlugin(config)` factories, Changesets, and the backend gem half. Common phrasings include "publish a dashboard plugin", "npm package for the Spree admin", "spree plugin new", "share admin screens across stores", "plugin not showing up", "Dashboard route collision", "plugin styles missing", "marketplace extension with admin UI".