When edit fails due to whitespace/indentation, propose line-based editing
When file changes between read and write are detected, propose stale-file guarding
When bash output is noisy, propose structured output parsing
When edits apply blindly, propose preview diffs
Each extension must solve exactly one problem
Prefer ~/.pi/extensions/name.ts over folders

Extension Patterns

Edit by Line: Replace exact-text matching with line numbers

edit_line({ path: "foo.tsx", start: 45, end: 52, replacement: "..." })

Edit Preview: Intercept edit tool, show unified diff in TUI overlay

Bash Summarize: Parse known tools (vp check, npm test), return structured errors

File Stale Guard: Store mtime on read, warn on write if changed

When to Propose

After 2+ failed edit attempts due to formatting
When user manually pipes bash output through grep/head
When user discovers wrong edit only after running checks
When formatter modifies files between read and write

Más de este repositorio

mismo repositorio

teach

elianiva/dotfiles

Teach the user a new skill or concept, within this workspace.

2026-07-05201

commit

elianiva/dotfiles

Conventional commit message generator for jj and git repos. Analyzes diffs and produces scoped, well-formed commit messages. Use whenever the user says "commit", "make a commit", "write commit message", or similar.

2026-05-28201

deslop

elianiva/dotfiles

Remove all AI-generated slop like useless comments, try/catch blocks, and casts

2026-05-28201

opentui

elianiva/dotfiles

Build terminal UIs with OpenTUI. Covers the core API, keymaps, React and Solid bindings, components, layout, keyboard input, plugins, and testing.

2026-05-18201

prototype

elianiva/dotfiles

Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

2026-05-18201

elianiva/dotfiles

Generate test cases in standard QA format.

2026-05-18201

name	pi-improvements
description	When encountering pi tool limitations, propose focused extensions that solve one problem each.

Rules

When edit fails due to whitespace/indentation, propose line-based editing
When file changes between read and write are detected, propose stale-file guarding
When bash output is noisy, propose structured output parsing
When edits apply blindly, propose preview diffs
Each extension must solve exactly one problem
Prefer ~/.pi/extensions/name.ts over folders

Extension Patterns

Edit by Line: Replace exact-text matching with line numbers

edit_line({ path: "foo.tsx", start: 45, end: 52, replacement: "..." })

Edit Preview: Intercept edit tool, show unified diff in TUI overlay

Bash Summarize: Parse known tools (vp check, npm test), return structured errors

File Stale Guard: Store mtime on read, warn on write if changed

When to Propose

After 2+ failed edit attempts due to formatting
When user manually pipes bash output through grep/head
When user discovers wrong edit only after running checks
When formatter modifies files between read and write