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

@algm/fdw

v0.1.1

Published

Fiction-driven workflow CLI

Readme

fdw

Fiction-driven workflow CLI. A TypeScript CLI tool for managing fiction-driven workflows.

Prerequisites

Install

pnpm install

Build

pnpm build

Produces dist/bin/fdw.js (the compiled binary).

Test

pnpm test

Runs the Vitest test suite.

Lint

pnpm lint

Runs ESLint over src/ and test/.

Usage

node dist/bin/fdw.js --version
node dist/bin/fdw.js --help
node dist/bin/fdw.js init
node dist/bin/fdw.js init --book-markdown
node dist/bin/fdw.js update

fdw init

Initialize FDW-managed project files in the current directory. World builder skill templates are installed by default.

node dist/bin/fdw.js init

Expected successful output includes a deterministic summary line:

FDW_INIT_RESULT status=initialized created=<n> unchanged=<n> managed=<n>

Installed files include base framework assets, world builder output stubs, and world builder skill files:

  • openspec/config.yaml
  • schemas/fictionspec/spec.md
  • templates/story-outline.md
  • templates/world-builder/world-overview.md
  • templates/world-builder/magic-system.md
  • templates/world-builder/factions.md
  • templates/world-builder/timeline.md
  • .github/skills/world-builder/overview.md
  • .github/skills/world-builder/timeline.md
  • .github/skills/world-builder/factions.md
  • .github/skills/world-builder/magic-system.md

If run again in an already initialized project, it is idempotent and reports:

FDW_INIT_RESULT status=already_initialized created=0 unchanged=<n> managed=<n>

Existing projects: Run fdw update after upgrading the package to receive updated world builder templates and skill files.

Scaffold markdown book assets

Install baseline markdown book directories and a deterministic Makefile:

node dist/bin/fdw.js init --book-markdown

This mode requires a previously initialized project (fdw init).

Expected successful output includes:

FDW_INIT_RESULT status=book_markdown_initialized created=<n> unchanged=<n> skipped=<n> conflicts=<n> managed=<n>

Generated scaffold assets include:

  • templates/book-markdown/scenes/index.md
  • templates/book-markdown/chapters/chapter-01.md
  • templates/book-markdown/chapters/chapter-02.md
  • templates/book-markdown/compiled/manuscript.md
  • Makefile

Quickstart build commands:

make chapters
make book

fdw update

Refresh FDW-managed project files previously installed by init.

node dist/bin/fdw.js update

Expected successful output includes:

FDW_UPDATE_RESULT status=updated created=<n> updated=<n> unchanged=<n> managed=<n>

If the project is not initialized, update exits non-zero with:

FDW_UPDATE_ERROR reason=not_initialized message=No FDW project found. Run "fdw init" first.

World Builder Skills

fdw init installs two sets of world builder assets into every project:

| Asset type | Install location | Purpose | |---|---|---| | Output stubs | templates/world-builder/ | Markdown templates for author-populated world documents | | Skill files | .github/skills/world-builder/ | Agent instruction files defining per-aspect commands |

Agent Commands

Each skill file defines a canonical agent command that authors invoke inside their AI agent (GitHub Copilot, Claude, Cursor, etc.). The agent reads the skill file and follows its execution instructions.

| Command | Skill file | Output artifact | |---|---|---| | /world:overview | .github/skills/world-builder/overview.md | world/world-overview.md | | /world:timeline | .github/skills/world-builder/timeline.md | world/timeline.md | | /world:factions | .github/skills/world-builder/factions.md | world/factions.md | | /world:magic-system | .github/skills/world-builder/magic-system.md | world/magic-system.md |

How Skills Work

Each skill follows a three-step execution pattern:

  1. Fill-then-ask — the agent extracts facts from the author's input and populates all directly mappable fields in the output stub before asking any questions. Only unresolved required fields trigger follow-up questions.
  2. Continuity check — before finalising output, the agent compares candidate content against existing world files and reports hard contradictions or weak continuity links, each with a source-citation link to the referenced file.
  3. Guidance-based conflict resolution — when a contradiction is detected the agent asks the author which version is correct rather than silently overwriting existing content.

Receiving Updated Skill Files

Skill files are managed assets. Run fdw update in an existing project to refresh them:

node dist/bin/fdw.js update

If you have customised a skill file at its target path, fdw update skips that file and reports it as skipped/conflicts to avoid data loss.