Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

$pwd:

pi-extension-development

Name: Pi Extension Development
Author: spences10

// Build or modify packages in this Pi monorepo. Use when creating Pi extensions, prompt shims, built-in extension wiring, package scaffolds, or packages/pi-* implementation work.

Executar no Manus

$ git log --oneline --stat

stars:37

forks:7

updated:23 de maio de 2026 às 16:44

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	pi-extension-development
description	Build or modify packages in this Pi monorepo. Use when creating Pi extensions, prompt shims, built-in extension wiring, package scaffolds, or packages/pi-* implementation work.
compatibility	Requires the Pi coding-agent monorepo and extension API.

Pi Extension Development

Use this workflow for packages/pi-* implementation work in this repo.

Workflow

Identify the package boundary first: root app, src/extensions/*, or a packages/pi-* workspace package.
For new built-ins, add a package under packages/, wire root package.json optional dependencies, and register in src/extensions/builtin-registry.ts.
Keep extension entrypoints small: export a default extension function and pure helper functions for testable trigger logic.
Put user-facing injected prompt text in one obvious template block; gate injection by selected tools/options when possible.
Update package README and Changeset when behavior changes.
Validate with the package script first, then root checks if registry/root files changed.

Project conventions

Prefer @spences10/pi-* workspace packages with workspace:* links.
Tests live beside source as *.test.ts and should cover trigger/gating helpers.
Avoid importing another package's src/* or dist/*; use public package entrypoints.
Use references/checklist.md for the exact file checklist when adding a package.

related-skills.json

mesmo repositório

pi-primitive-check.md

from "spences10/my-pi"

Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.

2026-05-2537

pi-package-sandbox-test.md

from "spences10/my-pi"

Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

2026-05-2337

pi-release-workflow.md

from "spences10/my-pi"

Prepare or verify releases for this Pi monorepo. Use for Changesets, pnpm lockfile/versioning, package preview generation, release-age policy, or published package installability checks.

2026-05-2337

pi-validation-flow.md

from "spences10/my-pi"

Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling.

2026-05-2337

package.json

"author": "spences10"

"repository": "spences10/my-pi"

Abrir repositório GitHub Ver repositórios do creator

$ install --global

$ download --local

Executar no Manus

$ useful --forSOC

Desenvolvedores de softwareInformática e Matemática15-1252L4

name	pi-extension-development
description	Build or modify packages in this Pi monorepo. Use when creating Pi extensions, prompt shims, built-in extension wiring, package scaffolds, or packages/pi-* implementation work.
compatibility	Requires the Pi coding-agent monorepo and extension API.

Pi Extension Development

Use this workflow for packages/pi-* implementation work in this repo.

Workflow

Identify the package boundary first: root app, src/extensions/*, or a packages/pi-* workspace package.
For new built-ins, add a package under packages/, wire root package.json optional dependencies, and register in src/extensions/builtin-registry.ts.
Keep extension entrypoints small: export a default extension function and pure helper functions for testable trigger logic.
Put user-facing injected prompt text in one obvious template block; gate injection by selected tools/options when possible.
Update package README and Changeset when behavior changes.
Validate with the package script first, then root checks if registry/root files changed.

Project conventions

Prefer @spences10/pi-* workspace packages with workspace:* links.
Tests live beside source as *.test.ts and should cover trigger/gating helpers.
Avoid importing another package's src/* or dist/*; use public package entrypoints.
Use references/checklist.md for the exact file checklist when adding a package.

pi-extension-development

Pi Extension Development

Workflow

Project conventions

Mais deste repositório

Mais deste repositório

Pi Extension Development

Workflow

Project conventions