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

@ckyong826/prompt-engineering

v1.0.0

Published

Reusable prompt skills for software work. Installs one SKILL.md source into every major coding agent (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, Copilot, and more).

Readme

Prompt Engineering Library

This library stores reusable prompts for software work. Each prompt solves one clear task in the software flow. One source file feeds every major coding agent, as a skill or as a plain prompt.

What Is This Library For

You use this library to build software faster and with fewer errors. It gives you ready prompts for common engineering tasks. Each prompt tells the AI tool what role to take and what steps to follow. You do not need to write a long prompt from scratch.

Skill or Prompt

Each entry ships in two forms. Both forms hold the same text.

  • Use the skill form when your tool supports skills. The agent finds it by name and loads it on its own. Files live in skills/<name>/SKILL.md.
  • Use the prompt form when your tool takes pasted text. Copy the file, or print it and pipe it into a CLI. Files live in prompts/<name>.md.

Rule: edit the skill file only. Then run export to rebuild the prompt file. This keeps both forms in sync.

Install

Pick one method. All three copy the same skills/ source into your agents.

Option 1: npm (Node 16 or newer)

No clone needed. Run from any folder.

npx @ckyong826/prompt-engineering install --global

Install into one project, for two agents only:

npx @ckyong826/prompt-engineering install --project --agent claude-code,cursor

Other commands:

npx @ckyong826/prompt-engineering list
npx @ckyong826/prompt-engineering doctor
npx @ckyong826/prompt-engineering show autonomous-project-build-orchestrator
npx @ckyong826/prompt-engineering uninstall --global

Note: npx pulls from the npm registry. The owner must run npm publish --access public once before the commands above work for other users. Until then, clone the repo and use Option 2 or 3.

Option 2: PowerShell (Windows, Linux, macOS)

Works in Windows PowerShell 5.1 and PowerShell 7+.

git clone https://github.com/ckyong826/prompt-engineering.git
cd prompt-engineering
.\install.ps1 -Global

Project install, two agents only:

.\install.ps1 -Project -Agent claude-code,cursor

Print one entry as a plain prompt:

.\install.ps1 -Show autonomous-project-build-orchestrator

No clone, straight from GitHub:

& ([scriptblock]::Create((Invoke-RestMethod https://raw.githubusercontent.com/ckyong826/prompt-engineering/main/install.ps1))) -Remote -Global

If Windows blocks the script, run it with:

powershell -NoProfile -ExecutionPolicy Bypass -File install.ps1 -Global

Option 3: Bash (Linux, macOS)

git clone https://github.com/ckyong826/prompt-engineering.git
cd prompt-engineering
chmod +x install.sh
./install.sh --global

Project install, two agents only:

./install.sh --project --agent cursor,opencode

Check status:

./install.sh --doctor --global

Print one entry as a plain prompt:

./install.sh show autonomous-project-build-orchestrator

How to Use

After install, restart your agent. Then use one of these ways.

Slash command (fastest)

In OpenCode or Claude Code, type / and pick the command:

/autonomous-project-build-orchestrator finish the API

Skill (agent loads it)

Tell the agent to use the skill by name:

Use the autonomous-project-build-orchestrator skill.

The agent reads SKILL.md when the task matches. No copy and paste needed.

Copy and paste (any AI tool)

Open the prompt file in prompts/. Copy the full text. Paste the text into your AI tool.

Pipe into a CLI (any terminal tool)

Print the prompt and feed it to another command:

npx @ckyong826/prompt-engineering show autonomous-project-build-orchestrator | codex exec -
.\install.ps1 -Show autonomous-project-build-orchestrator | codex exec -
./install.sh show autonomous-project-build-orchestrator | codex exec -

Replace codex exec - with the CLI you use.

Agent Coverage

--global writes to the home paths. --project writes to the project paths. .agents/skills is the shared standard. Most new tools read it.

| Agent | Flag | Project path | Home path | |-------|------|--------------|-----------| | Universal | agents | .agents/skills/ | ~/.agents/skills/ | | Claude Code | claude-code | .claude/skills/ | ~/.claude/skills/ | | Cursor | cursor | .cursor/skills/ | ~/.cursor/skills/ | | Codex | codex | .codex/skills/ | ~/.codex/skills/ | | OpenCode | opencode | .opencode/skills/ | ~/.config/opencode/skills/ | | Gemini CLI | gemini-cli | .gemini/skills/ | ~/.gemini/skills/ | | GitHub Copilot | github-copilot | .github/skills/ | ~/.copilot/skills/ | | Windsurf | windsurf | .windsurf/skills/ | ~/.codeium/windsurf/skills/ | | Kilo Code | kilocode | .kilocode/skills/ | ~/.kilocode/skills/ | | Roo Code | roo | .roo/skills/ | ~/.roo/skills/ | | Kiro CLI | kiro | .kiro/skills/ | ~/.kiro/skills/ | | Trae | trae | .trae/skills/ | ~/.trae/skills/ | | Goose | goose | .goose/skills/ | ~/.config/goose/skills/ | | Droid | droid | .factory/skills/ | ~/.factory/skills/ | | Antigravity | antigravity | .agent/skills/ | ~/.gemini/antigravity/skills/ | | Clawdbot | clawdbot | skills/ | ~/.clawdbot/skills/ | | Neovate | neovate | .neovate/skills/ | ~/.neovate/skills/ |

The installer also copies OpenCode slash commands to .opencode/commands/ (project) or ~/.config/opencode/commands/ (home).

Available Prompts

Click a name to open the full prompt.

| Prompt | What It Does | When to Use It | Run It | |--------|--------------|----------------|--------| | Autonomous Project Build Orchestrator | It acts as a senior engineering lead. It inspects your repo, finds missing work, splits the work into small tasks, runs parallel workers, reviews the code, merges safe changes, and runs tests until the project is complete. | Use it when you have a started project, a spec, or a partial repo, and you want an AI team to finish it with quality gates. | /autonomous-project-build-orchestrator |

Files:

  • Skill source: ./skills/autonomous-project-build-orchestrator/SKILL.md
  • Prompt file: ./prompts/autonomous-project-build-orchestrator.md
  • OpenCode command: ./.opencode/commands/autonomous-project-build-orchestrator.md

Add a New Prompt

  1. Make a new folder: skills/<your-skill-name>/.
  2. Use only lowercase letters, numbers, and single hyphens for the name.
  3. Add SKILL.md in that folder with name and description at the top.
  4. Run node bin/cli.js export to build prompts/<your-skill-name>.md.
  5. Add a command file in .opencode/commands/<your-skill-name>.md if you want / use.
  6. Run node bin/cli.js list to check the new skill.
  7. Add one row for it in the table above.