Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More โ†’
Socket
Sign inDemoInstall
Socket

@promptbook/utils

Package Overview
Dependencies
Maintainers
1
Versions
470
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@promptbook/utils

Supercharge your use of large language models

  • 0.67.0-1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
387K
decreased by-18.35%
Maintainers
1
Weekly downloads
ย 
Created
Source

Promptbook logo - cube with letters P and B Promptbook

Supercharge your use of large language models

NPM Version of Promptbook logo - cube with letters P and B Promptbook Quality of package Promptbook logo - cube with letters P and B Promptbook Known Vulnerabilities Issues

๐Ÿ“ฆ Package @promptbook/utils

  • Promptbooks are divided into several packages, all are published from single monorepo.
  • This package @promptbook/utils is one part of the promptbook ecosystem.

To install this package, run:

# Install entire promptbook ecosystem
npm i ptbk

# Install just this package to save space
npm i @promptbook/utils

Utility functions used in the library but also useful for individual use in preprocessing and postprocessing LLM inputs and outputs

Here is a overview of the functions which are exported from the @promptbook/utils package and can be used in your own projects:

Postprocessing

Sometimes you need to postprocess the output of the LLM model, every postprocessing function that is available through POSTPROCESS command in promptbook is exported from @promptbook/utils. You can use:

Very often you will use unwrapResult, which is used to extract the result you need from output with some additional information:

import { unwrapResult } from '@promptbook/utils';

unwrapResult('Best greeting for the user is "Hi Pavol!"'); // 'Hi Pavol!'

Templating

There is a function replaceParameters which is used to replace the parameters in given template optimized to LLM prompt templates.

import { replaceParameters } from '@promptbook/utils';

replaceParameters('Hello, {name}!', { name: 'world' }); // 'Hello, world!'

And also multiline templates with blockquotes

import { replaceParameters, spaceTrim } from '@promptbook/utils';

replaceParameters(
    spaceTrim(`
        Hello, {name}!

        > {answer}
    `),
    {
        name: 'world',
        answer: spaceTrim(`
            I'm fine,
            thank you!

            And you?
        `),
    },
);

// Hello, world!
//
// > I'm fine,
// > thank you!
// >
// > And you?

Counting

Theese functions are usefull to count stats about the input/output in human-like terms not tokens and bytes, you can use countCharacters, countLines, countPages, countParagraphs, countSentences, countWords

import { countWords } from '@promptbook/utils';

console.log(countWords('Hello, world!')); // 2

Splitting

Splitting functions are similar to counting but they return the splitted parts of the input/output, you can use splitIntoCharacters, splitIntoLines, splitIntoPages, splitIntoParagraphs, splitIntoSentences, splitIntoWords

import { splitIntoWords } from '@promptbook/utils';

console.log(splitIntoWords('Hello, world!')); // ['Hello', 'world']

Normalization

Normalization functions are used to put the string into a normalized form, you can use kebab-case PascalCase SCREAMING_CASE snake_case kebab-case

import { normalizeTo } from '@promptbook/utils';

console.log(normalizeTo['kebab-case']('Hello, world!')); // 'hello-world'
  • There are more normalization functions like capitalize, decapitalize, removeDiacritics,...
  • Theese can be also used as postprocessing functions in the POSTPROCESS command in promptbook

Misc

See also the documentation for all the functions in the @promptbook/utils package, every function is documented by jsdoc, typed by typescript and tested by jest.

assertsExecutionSuccessful, checkExpectations, executionReportJsonToString, isPassingExpectations, isValidJsonString, parseNumber


Rest of the documentation is common for entire promptbook ecosystem:

๐Ÿค The Promptbook Whitepaper

When you have a simple, single prompt for ChatGPT, GPT-4, Anthropic Claude, Google Gemini, Llama 2, or whatever, it doesn't matter how it is integrated. Whether it's the direct calling of a REST API, using the SDK, hardcoding the prompt in the source code, or importing a text file, the process remains the same.

If you need something more advanced or want to extend the capabilities of LLMs, you generally have three ways to proceed:

  1. Fine-tune the model to your specifications or even train your own.
  2. Prompt-engineer the prompt to the best shape you can achieve.
  3. Use multiple prompts in a pipeline to get the best result.

In any of these situations, but especially in (3), the Promptbook library can make your life easier and make orchestraror for your prompts.

  • Separation of concerns between prompt engineer and programmer; between code files and prompt files; and between prompts and their execution logic.
  • Set up a common format for prompts that is interchangeable between projects and language/technology stacks.
  • Preprocessing and cleaning the input data from the user.
  • Use default values - Jokers to bypass some parts of the pipeline.
  • Expect some specific output from the model.
  • Retry mismatched outputs.
  • Combine multiple models together.
  • Interactive User interaction with the model and the user.
  • Leverage external sources (like ChatGPT plugins or OpenAI's GPTs).
  • Simplify your code to be DRY and not repeat all the boilerplate code for each prompt.
  • Versioning of promptbooks
  • Reuse parts of promptbooks in/between projects.
  • Run the LLM optimally in parallel, with the best cost/quality ratio or speed/quality ratio.
  • Execution report to see what happened during the execution.
  • Logging the results of the promptbooks.
  • (Not ready yet) Caching calls to LLMs to save money and time.
  • (Not ready yet) Extend one prompt book from another one.
  • (Not ready yet) Leverage the streaming to make super cool UI/UX.
  • (Not ready yet) A/B testing to determine which prompt works best for the job.

๐Ÿง” Promptbook (for prompt-engeneers)

Prompt book markdown file (or .ptbk.md file) is document that describes a pipeline - a series of prompts that are chained together to form somewhat reciepe for transforming natural language input.

  • Multiple pipelines forms a collection which will handle core know-how of your LLM application.
  • Theese pipelines are designed such as they can be written by non-programmers.

Sample:

File write-website-content.ptbk.md:

๐ŸŒ Create website content

Instructions for creating web page content.

  • PIPELINE URL https://promptbook.studio/webgpt/write-website-content.ptbk.md
  • PROMPTBOOK VERSION 0.0.1
  • INPUTโ€ฏโ€ฏPARAM {rawTitle} Automatically suggested a site name or empty text
  • INPUTโ€ฏโ€ฏPARAM {rawAssigment} Automatically generated site entry from image recognition
  • OUTPUTโ€ฏPARAM {websiteContent} Web content
  • OUTPUTโ€ฏPARAM {keywords} Keywords

๐Ÿ‘ค Specifying the assigment

What is your web about?

  • PROMPT DIALOG
{rawAssigment}

-> {assigment} Website assignment and specification

โœจ Improving the title

  • MODEL VARIANT Chat
  • MODEL NAME gpt-4
  • POSTPROCESSING unwrapResult
As an experienced marketing specialist, you have been entrusted with improving the name of your client's business.

A suggested name from a client:
"{rawTitle}"

Assignment from customer:

> {assigment}

## Instructions:

-   Write only one name suggestion
-   The name will be used on the website, business cards, visuals, etc.

-> {enhancedTitle} Enhanced title

๐Ÿ‘ค Website title approval

Is the title for your website okay?

  • PROMPT DIALOG
{enhancedTitle}

-> {title} Title for the website

๐Ÿฐ Cunning subtitle

  • MODEL VARIANT Chat
  • MODEL NAME gpt-4
  • POSTPROCESSING unwrapResult
As an experienced copywriter, you have been entrusted with creating a claim for the "{title}" web page.

A website assignment from a customer:

> {assigment}

## Instructions:

-   Write only one name suggestion
-   Claim will be used on website, business cards, visuals, etc.
-   Claim should be punchy, funny, original

-> {claim} Claim for the web

๐Ÿšฆ Keyword analysis

  • MODEL VARIANT Chat
  • MODEL NAME gpt-4
As an experienced SEO specialist, you have been entrusted with creating keywords for the website "{title}".

Website assignment from the customer:

> {assigment}

## Instructions:

-   Write a list of keywords
-   Keywords are in basic form

## Example:

-   Ice cream
-   Olomouc
-   Quality
-   Family
-   Tradition
-   Italy
-   Craft

-> {keywords} Keywords

๐Ÿ”— Combine the beginning

  • SIMPLE TEMPLATE

# {title}

> {claim}

-> {contentBeginning} Beginning of web content

๐Ÿ–‹ Write the content

  • MODEL VARIANT Completion
  • MODEL NAME gpt-3.5-turbo-instruct
As an experienced copywriter and web designer, you have been entrusted with creating text for a new website {title}.

A website assignment from a customer:

> {assigment}

## Instructions:

-   Text formatting is in Markdown
-   Be concise and to the point
-   Use keywords, but they should be naturally in the text
-   This is the complete content of the page, so don't forget all the important information and elements the page should contain
-   Use headings, bullets, text formatting

## Keywords:

{keywords}

## Web Content:

{contentBeginning}

-> {contentBody} Middle of the web content

๐Ÿ”— Combine the content

  • SIMPLE TEMPLATE
{contentBeginning}

{contentBody}

-> {websiteContent}

Following is the scheme how the promptbook above is executed:

%% ๐Ÿ”ฎ Tip: Open this on GitHub or in the VSCode website to see the Mermaid graph visually

flowchart LR
  subgraph "๐ŸŒ Create website content"

      direction TB

      input((Input)):::input
      templateSpecifyingTheAssigment(๐Ÿ‘ค Specifying the assigment)
      input--"{rawAssigment}"-->templateSpecifyingTheAssigment
      templateImprovingTheTitle(โœจ Improving the title)
      input--"{rawTitle}"-->templateImprovingTheTitle
      templateSpecifyingTheAssigment--"{assigment}"-->templateImprovingTheTitle
      templateWebsiteTitleApproval(๐Ÿ‘ค Website title approval)
      templateImprovingTheTitle--"{enhancedTitle}"-->templateWebsiteTitleApproval
      templateCunningSubtitle(๐Ÿฐ Cunning subtitle)
      templateWebsiteTitleApproval--"{title}"-->templateCunningSubtitle
      templateSpecifyingTheAssigment--"{assigment}"-->templateCunningSubtitle
      templateKeywordAnalysis(๐Ÿšฆ Keyword analysis)
      templateWebsiteTitleApproval--"{title}"-->templateKeywordAnalysis
      templateSpecifyingTheAssigment--"{assigment}"-->templateKeywordAnalysis
      templateCombineTheBeginning(๐Ÿ”— Combine the beginning)
      templateWebsiteTitleApproval--"{title}"-->templateCombineTheBeginning
      templateCunningSubtitle--"{claim}"-->templateCombineTheBeginning
      templateWriteTheContent(๐Ÿ–‹ Write the content)
      templateWebsiteTitleApproval--"{title}"-->templateWriteTheContent
      templateSpecifyingTheAssigment--"{assigment}"-->templateWriteTheContent
      templateKeywordAnalysis--"{keywords}"-->templateWriteTheContent
      templateCombineTheBeginning--"{contentBeginning}"-->templateWriteTheContent
      templateCombineTheContent(๐Ÿ”— Combine the content)
      templateCombineTheBeginning--"{contentBeginning}"-->templateCombineTheContent
      templateWriteTheContent--"{contentBody}"-->templateCombineTheContent

      templateCombineTheContent--"{websiteContent}"-->output
      output((Output)):::output

      classDef input color: grey;
      classDef output color: grey;

  end;

Note: We are using postprocessing functions like unwrapResult that can be used to postprocess the result.

๐Ÿ“ฆ Packages

This library is divided into several packages, all are published from single monorepo. You can install all of them at once:

npm i ptbk

Or you can install them separately:

โญ Marked packages are worth to try first

๐Ÿ“š Dictionary

The following glossary is used to clarify certain concepts:

Core concepts

Advanced concepts

๐Ÿ”Œ Usage in Typescript / Javascript

โž•โž– When to use Promptbook?

โž• When to use

  • When you are writing app that generates complex things via LLM - like websites, articles, presentations, code, stories, songs,...
  • When you want to separate code from text prompts
  • When you want to describe complex prompt pipelines and don't want to do it in the code
  • When you want to orchestrate multiple prompts together
  • When you want to reuse parts of prompts in multiple places
  • When you want to version your prompts and test multiple versions
  • When you want to log the execution of prompts and backtrace the issues

โž– When not to use

  • When you are writing just a simple chatbot without any extra logic, just system messages

๐Ÿœ Known issues

๐Ÿงผ Intentionally not implemented features

โ” FAQ

If you have a question start a discussion, open an issue or write me an email.

Why not just use the OpenAI SDK / Anthropic Claude SDK / ...?

Different levels of abstraction. OpenAI library is for direct use of OpenAI API. This library is for a higher level of abstraction. It is for creating prompt templates and promptbooks that are independent of the underlying library, LLM model, or even LLM provider.

How is it different from the Langchain library?

Langchain is primarily aimed at ML developers working in Python. This library is for developers working in javascript/typescript and creating applications for end users.

We are considering creating a bridge/converter between these two libraries.

Promptbooks vs. OpenAI`s GPTs

GPTs are chat assistants that can be assigned to specific tasks and materials. But they are still chat assistants. Promptbooks are a way to orchestrate many more predefined tasks to have much tighter control over the process. Promptbooks are not a good technology for creating human-like chatbots, GPTs are not a good technology for creating outputs with specific requirements.

Where should I store my promptbooks?

If you use raw SDKs, you just put prompts in the sourcecode, mixed in with typescript, javascript, python or whatever programming language you use.

If you use promptbooks, you can store them in several places, each with its own advantages and disadvantages:

  1. As source code, typically git-committed. In this case you can use the versioning system and the promptbooks will be tightly coupled with the version of the application. You still get the power of promptbooks, as you separate the concerns of the prompt-engineer and the programmer.

  2. As data in a database In this case, promptbooks are like posts / articles on the blog. They can be modified independently of the application. You don't need to redeploy the application to change the promptbooks. You can have multiple versions of promptbooks for each user. You can have a web interface for non-programmers to create and modify promptbooks. But you lose the versioning system and you still have to consider the interface between the promptbooks and the application (= input and output parameters).

  3. In a configuration in environment variables. This is a good way to store promptbooks if you have an application with multiple deployments and you want to have different but simple promptbooks for each deployment and you don't need to change them often.

What should I do when I need same promptbook in multiple human languages?

A single promptbook can be written for several (human) languages at once. However, we recommend that you have separate promptbooks for each language.

In large language models, you will get better results if you have prompts in the same language as the user input.

The best way to manage this is to have suffixed promptbooks like write-website-content.en.ptbk.md and write-website-content.cs.ptbk.md for each supported language.

โŒš Changelog

See CHANGELOG.md

๐Ÿ“œ License

Promptbook by Pavol Hejnรฝ is licensed under CC BY 4.0

๐ŸŽฏ Todos

See TODO.md

๐Ÿ–‹๏ธ Contributing

I am open to pull requests, feedback, and suggestions. Or if you like this utility, you can โ˜• buy me a coffee or donate via cryptocurrencies.

You can also โญ star the promptbook package, follow me on GitHub or various other social networks.

Keywords

FAQs

Package last updated on 21 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with โšก๏ธ by Socket Inc