npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@dkolosovsky/reactor-text-tools

v0.1.0

Published

Universal text Idea-Transformers (cover-letter / vacancy-score / question-answer) for the Reactor ecosystem. Builders + Activities + Tools + typed errors.

Readme

@reactor/text-tools

Platform-agnostic text-LLM domain adapter on top of @kolosochek/reactor-core.

Provides three Idea-Triplet Activities - generateCoverLetter, scoreVacancy, answerQuestions - that operate on raw text input ({ vacancy: { title, description }, resume: { title, content } }) and return structured Solutions. No platform coupling, no DB roundtrip. Consumed by both the Chrome extension and the hh.ru @hhru/reactor-adapter (after Phase C+ migrations 4.2 and 4.3).

Status

v0.1.0 - text-tools genesis (sub-project 4.1 of the Phase C+ decoupling work).

Usage

import { Reactor, InMemoryRepositories, createOpenRouter } from '@kolosochek/reactor-core';
import {
  textToolsAdapter,
  buildCoverLetterIdea,
  buildScoreIdea,
  buildQuestionsIdea,
} from '@reactor/text-tools';

const reactor = Reactor.create({ llm: createOpenRouter({ apiKey: '...' }) });
reactor.use({ ...textToolsAdapter, repositories: new InMemoryRepositories() });

// Cover letter on a pasted vacancy:
const ideaLetter = buildCoverLetterIdea({
  vacancy: {
    title: 'Senior Frontend Engineer',
    description: 'React, TypeScript, 5+ years',
    url: 'https://hh.ru/vacancy/42',
    platform: 'hh.ru',
  },
  resume: {
    title: 'Frontend Engineer',
    content: '7 years React, TypeScript, GraphQL...',
  },
});
const sol = await reactor.execute(ideaLetter);
console.log(sol.output.letter);

The same pattern works for buildScoreIdea (returns { score, reasoning, skillMatch }) and buildQuestionsIdea (returns { qaPairs }).

Testing

The package exports a test-utils subpath for consumers:

import {
  createMockLLMProvider,
  runLLMProviderContractTests,
} from '@reactor/text-tools/test-utils';
import { describe } from 'vitest';

// Mock LLM for unit tests:
const llm = createMockLLMProvider({
  onComplete: async () => ({ content: 'mocked', model: 'mock' }),
});

// Conformance suite for any LLMProvider implementation:
runLLMProviderContractTests(describe, () => myLLMProviderFactory());

Acceptance criteria

  • All Activities accept vacancy: { title, description, url?, platform? } (no vacancyId anywhere).
  • Each Activity uses composeActivity({ llmFallback }) so future crystallization (preCheck, postValidate) is one-line addition.
  • LLMProvider reaches Activities via ctx.llm (requires @kolosochek/reactor-core >= 0.2.0).
  • Idea immutability preserved (frozen Ideas execute without throwing).
  • 80 tests passing (run via vitest).

Out of scope (post-4.1)

  • Real LLMProvider implementation tied to a specific provider (use createOpenRouter from reactor-core for OpenRouter; consumers wire their own).
  • Crystallization (Phase 1 preCheck for any tool - to be addressed once experience data accumulates).
  • Streaming output.
  • Multi-message conversational LLM flows (single-turn only at 0.1.0).

Source

  • Spec: docs/superpowers/specs/2026-04-26-text-tools-decouple-design.md
  • Plan: docs/superpowers/plans/2026-04-26-text-tools-genesis.md