Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

$pwd:

pi-primitive-check

Name: Pi Primitive Check
Author: spences10

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

Exécuter dans Manus

$ git log --oneline --stat

stars:37

forks:7

updated:25 mai 2026 à 09:02

SKILL.md

readonly

name	pi-primitive-check
description	Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.
compatibility	Requires the Pi coding-agent monorepo docs and source tree.

Pi Primitive Check

Use this before implementing speculative Pi customisation ideas. The goal is to avoid building a parallel abstraction when Pi already has a primitive.

Workflow

Restate the underlying user need, separate from the proposed solution.
Search local Pi docs for overlapping primitives, especially commands, session features, SDK APIs, extension events, tools, skills, and TUI APIs.
Search this repo for existing built-ins and packages/pi-* that already address the need.
Classify the proposal:
- use existing Pi primitive
- document or wrap existing primitive
- compose existing primitives
- implement new feature
If overlap exists, pause and ask the user to confirm before coding.

Required local sources

Read relevant files from the installed Pi docs before deciding:

README: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/README.md
Docs directory: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/docs
Examples directory: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/examples

Prefer targeted rg over broad reading, then read the relevant docs fully enough to verify behavior.

Output format

Primitive check:

- User need:
- Existing Pi primitives:
- Existing Pi customisation pieces:
- Overlap/risk:
- Recommendation:
- Confirm before build:

Keep the recommendation direct. If the answer is “do not build this”, say so.

related-skills.json

même dépôt

pi-extension-development.md

from "spences10/my-pi"

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.

2026-05-2337

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"

Ouvrir le dépôt GitHub Voir les dépôts du créateur

$ install --global

$ download --local

Exécuter dans Manus

$ useful --forSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

name	pi-primitive-check
description	Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.
compatibility	Requires the Pi coding-agent monorepo docs and source tree.

Pi Primitive Check

Use this before implementing speculative Pi customisation ideas. The goal is to avoid building a parallel abstraction when Pi already has a primitive.

Workflow

Restate the underlying user need, separate from the proposed solution.
Search local Pi docs for overlapping primitives, especially commands, session features, SDK APIs, extension events, tools, skills, and TUI APIs.
Search this repo for existing built-ins and packages/pi-* that already address the need.
Classify the proposal:
- use existing Pi primitive
- document or wrap existing primitive
- compose existing primitives
- implement new feature
If overlap exists, pause and ask the user to confirm before coding.

Required local sources

Read relevant files from the installed Pi docs before deciding:

README: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/README.md
Docs directory: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/docs
Examples directory: /home/scott/repos/my-pi/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.75.4_ws@8.20.1_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/examples

Prefer targeted rg over broad reading, then read the relevant docs fully enough to verify behavior.

Output format

Primitive check:

- User need:
- Existing Pi primitives:
- Existing Pi customisation pieces:
- Overlap/risk:
- Recommendation:
- Confirm before build:

Keep the recommendation direct. If the answer is “do not build this”, say so.

pi-primitive-check

Pi Primitive Check

Workflow

Required local sources

Output format

Plus depuis ce dépôt

Plus depuis ce dépôt

Pi Primitive Check

Workflow

Required local sources

Output format