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

@borgesius/openclaw-style-guide

v0.1.0

Published

OpenClaw context-engine plugin that injects writing style rules (Chicago, AP, MLA) into agent system prompts

Readme

@borgesius/openclaw-style-guide

npm version License: MIT

An OpenClaw context-engine plugin that injects writing style rules into every agent system prompt. Enforce consistent prose—Chicago, AP, MLA, or your own custom style—across all your AI outputs.

Why?

LLMs default to inconsistent, often corporate-sounding prose. They overuse em dashes, hedge constantly, and throw in phrases like "Certainly!" and "Great question!" that make your assistant sound like a chatbot.

This plugin fixes that by injecting clear, forceful style rules into every system prompt. Your agents write better because they have explicit rules to follow.

Installation

openclaw plugins install @borgesius/openclaw-style-guide

Or with npm:

npm install @borgesius/openclaw-style-guide

Then add to your openclaw.json:

{
  "plugins": {
    "entries": {
      "@borgesius/openclaw-style-guide": {}
    }
  }
}

Configuration

Configure via plugins.entries.@borgesius/openclaw-style-guide.config:

{
  "plugins": {
    "entries": {
      "@borgesius/openclaw-style-guide": {
        "config": {
          "preset": "chicago"
        }
      }
    }
  }
}

Presets

| Preset | Description | |--------|-------------| | chicago | Default. Chicago Manual of Style. Oxford comma, em dashes without spaces (used sparingly), spell out numbers 1–100. | | ap | AP Style. No Oxford comma, em dashes with spaces, spell out 1–9 only. | | mla | MLA Academic Style. Oxford comma, academic conventions. | | custom | Your own rules via the rules field. |

Custom Rules

Define your own style guide:

{
  "plugins": {
    "entries": {
      "@borgesius/openclaw-style-guide": {
        "config": {
          "preset": "custom",
          "rules": "Always use active voice. Keep sentences under 25 words. No jargon. Oxford comma required. Never start a sentence with 'I'."
        }
      }
    }
  }
}

What Gets Injected

When using chicago (the default), the plugin adds this to every system prompt:

## Writing Style: Chicago Manual of Style

You follow Chicago Manual of Style. These rules are non-negotiable:

**Em dashes:** No spaces around em dashes—like this, not like — this.
Use em dashes sparingly. Most of the time a colon, semicolon, or period
is the better choice.

**Oxford comma:** Always use the serial (Oxford) comma in lists of three
or more items: red, white, and blue.

**Quotation marks:** Double quotes for primary quotations. Single quotes
for quotations within quotations.

**Punctuation placement:** Periods and commas go inside quotation marks.
Colons and semicolons go outside.

**Numbers:** Spell out one through one hundred. Use numerals for 101 and
above. Spell out any number that begins a sentence.

**Voice:** No passive voice abuse. Prefer active constructions.

**Filler phrases to avoid:** Never write "certainly!", "great question!",
"I would be happy to", "absolutely!", or similar hollow corporate filler.
Just answer directly.

Token Cost

It's like 200–300 tokens per prompt. Basically nothing. Your conversations use thousands of tokens anyway, so this is <1% overhead for much better writing.

How well the model actually follows the rules depends on the model. Bigger models tend to be better at it.

How It Works

This is a context-engine plugin. It hooks into OpenClaw's before_prompt_build event and appends the style rules to the system context. The rules appear in every agent's system prompt, ensuring consistent style across all conversations.

TypeScript

The package exports types if you want to use the style blocks programmatically:

import { getStyleBlock, StyleGuideConfig, StylePreset } from '@borgesius/openclaw-style-guide';

const config: StyleGuideConfig = { preset: 'chicago' };
const styleBlock = getStyleBlock(config);

License

MIT