Menü
Use for extending Pi with skills, extensions, templates, or packages.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create, redesign, and validate polished terminal-native slide decks for Presenterm from a topic, outline, notes, codebase, or existing Markdown. Use for Presenterm presentations, Markdown slides, technical talks, live-code demos, speaker notes, custom themes, diagrams, exports, or visual and narrative review of a terminal deck.
Best practices for writing Remotion React Markup
Manage Jira projects programmatically: create epics, user stories, subtasks, sprints, and assign issues. Use when the user asks to create/update Jira issues in bulk, set up a project backlog in Jira, migrate planning from documents to Jira, or automate Jira administration.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
Use when designing, implementing, refactoring, testing, or reviewing Java, Spring Boot, Hibernate/JPA, REST APIs, batch jobs, or JVM production code with emphasis on maintainability, clean architecture, security, observability, and performance.
Build polished terminal UIs with pi-tui: overlays, dashboards, widgets, dialogs, animated components, or data visualizations. Use for any interactive terminal UI work in pi extensions or custom tools.
| name | extending-pi |
| description | Use for extending Pi with skills, extensions, templates, or packages. |
Help the user decide what to build, scaffold the right files, and point to detailed guidance.
| Goal | Build a… | Key files to create | Where |
|---|---|---|---|
| Teach Pi a workflow or how to use a tool/API/CLI | Skill | SKILL.md with YAML frontmatter + markdown body | Read skill-creator/SKILL.md for detailed guidance |
| Give Pi a new tool, command, or runtime behavior | Extension | manifest.json + src/index.ts entry point | Read Pi docs: docs/extensions.md |
| Reuse a prompt pattern with variables | Prompt template | .md file with {{variable}} placeholders | Read Pi docs: docs/prompt-templates.md |
| Set project-wide coding guidelines | Context file | AGENTS.md in project root or .pi/agent/ — just markdown | No extra docs needed |
| Change Pi's appearance | Theme | theme.json with color and font definitions | Read Pi docs: docs/themes.md |
| Add a model or provider | Custom model | models.json or extension with provider registration | Read Pi docs: docs/models.md (JSON) or docs/custom-provider.md (extension) |
| Share any of the above | Package | manifest.json with dependencies and entry points | Read Pi docs: docs/packages.md |
If bash + instructions can do it, prefer a Skill (simpler, no code to maintain). If you need event hooks, typed tools, UI components, or policy enforcement, use an Extension.
Examples:
rm -rf" → Extension (event interception)db_query tool" → Extension (registerTool)Skill — place in .pi/skills/my-skill/SKILL.md:
---
name: my-skill
description: Does X when the user asks to Y.
---
# My Skill
Step 1: ...
Step 2: ...
Extension — create manifest.json + src/index.ts:
{ "name": "my-extension", "version": "0.1.0", "entry": "src/index.ts" }
import { registerTool } from "@anthropic/pi-sdk";
registerTool("my_tool", { description: "..." }, async (input) => { /* ... */ });
SKILL.md in .pi/skills/<name>/ and invoke the skill — if it doesn't trigger, check that name and description in frontmatter are set correctly.pi ext install . — if it fails with "missing entry", verify the entry path in manifest.json points to an existing file.docs/packages.md to bundle and publish.