extension-design

Audit Pi extensions for unsafe import patterns and enforce safety checklists.

816|77|Updated Feb 17, 2026

Search Tags:#developer tools #extension development #code auditing #import paths #pi sdk

Ready to run

npx skills add https://github.com/rcarmo/piclaw --skill extension-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extension-design
Source: https://github.com/rcarmo/piclaw/tree/main/skel/.pi/skills/extension-design
Command: npx skills add https://github.com/rcarmo/piclaw --skill extension-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers create and review Pi extensions, preventing common import errors that can break functionality.

Core Features & Use Cases

Safe Extension Development: Guides users on how to correctly reference installed packages instead of workspace source code.
Import Pattern Avoidance: Explicitly warns against importing directly from the workspace, which can lead to drift and breakage.
Use Case: When building a new Pi extension, use this Skill to ensure your import paths are robust and will not fail after the extension is installed or the workspace is reloaded.

Quick Start

Use the extension-design skill to audit the workspace for unsafe import patterns.

Frequently Asked Questions about extension-design

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

FAQPage Schema

How do I prevent broken import paths when developing Pi extensions?▼

To prevent broken import paths when developing Pi extensions, reference installed package distributions instead of workspace source code. Importing directly from the workspace causes drift and breakage when the extension is installed or the workspace is reloaded.

What is a safe import pattern for Pi extension development?▼

A safe import pattern for Pi extension development involves referencing installed package distributions rather than workspace source code. This ensures robust import paths that will not fail after the extension is installed or the workspace is reloaded.

How do I audit my workspace for unsafe Pi extension imports?▼

You can audit your workspace for unsafe Pi extension imports by using auditing tools to scan for direct workspace references. These tools check against a safety checklist to identify patterns that lead to drift and functionality breakage.

What safety checks are required for reviewing Pi extensions?▼

Safety checks for reviewing Pi extensions include error handling, filesystem access guarding, and dependency management. These checks ensure safe and stable operation by preventing broken import patterns and restricting unauthorized filesystem access.

Why do my Pi extensions break after reloading the workspace?▼

Pi extensions break after reloading the workspace because of unsafe import patterns that import directly from the workspace source code. This causes drift and breakage, which can be prevented by referencing installed package distributions instead.