pikku-addon

Package, wire, and distribute reusable Pikku function addons across projects.

56|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/pikkujs/pikku --skill pikku-addon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pikku-addon
Source: https://github.com/pikkujs/pikku/tree/main/.claude/skills/pikku-addon
Command: npx skills add https://github.com/pikkujs/pikku --skill pikku-addon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reusable Pikku function addons enable teams to package, version, and share functionality across projects, reducing duplication and accelerating development.

Core Features & Use Cases

  • Wire and wire HTTP/RPC integrations with wireAddon, addon(), pikkuAddonServices, and pikkuAddonWireServices
  • Define addon package structure and cross-project sharing, with consistent typing and exports
  • Scaffold, build, and consume addons in consuming apps with generated types and metadata

Quick Start

Create a Pikku addon scaffold and wire it for consumption in another project.

Frequently Asked Questions about pikku-addon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share TypeScript function addons across multiple projects?

To reuse addons across projects, you package them into a Pikku addon scaffold and use wireAddon to wire HTTP or RPC integrations, generating consistent types and metadata for consuming applications.

What is a Pikku addon scaffold and when do I need it for cross-project reuse?

A Pikku addon scaffold is a package structure with .pikku configuration and TypeScript sources for services and functions that you need when defining, building, and distributing shared addons across consuming projects.

How do I wire a shared addon into a consuming application?

You wire a shared addon into a consuming application by applying the addon() function alongside pikkuAddonServices and pikkuAddonWireServices to integrate HTTP or RPC services and generate required metadata.

Can I define HTTP and RPC integrations for reusable addon packages in TypeScript?

Yes, you can define HTTP and RPC integrations for reusable addon packages in TypeScript by using the wireAddon mechanism to apply consistent typing and exports across consuming projects.

Do I need a .pikku configuration file to generate types for shared addons?

Yes, a .pikku configuration file within your addon scaffold is required to generate the consistent types and metadata needed for cross-project distribution and consumption.

What is the best way to structure a TypeScript addon package for cross-project sharing?

The best way to structure a cross-project addon package is creating a Pikku addon scaffold containing .pikku configuration, TypeScript service sources, and wiring definitions for consistent exports.