القائمة
Create a new skill with guided setup. Use when the user wants to create a custom skill for pi-go.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skill-create |
| description | Create a new skill with guided setup. Use when the user wants to create a custom skill for pi-go. |
This skill is handled by the internal /skill-create command.
After the template is created, follow these steps:
Do fast research on how similar tools/skills work:
.pi-go/skills/ for referenceBased on research, ask the user 1-3 focused questions:
A. What should this skill do and when? (one sentence) B. What are the key steps? (or confirm the steps you found in research) C. Anything specific to add or change?
Update the SKILL.md with answers mapped to this structure:
---
name: <skill-name>
description: <answer A>
---
# <Skill Name>
<answer A expanded into clear instructions>
## Steps
<answer B or researched steps, confirmed by user>
## Examples
<concrete usage examples based on research + answers>
## Guidelines
<answer C + best practices from research>
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for semantic search". Covers the full flow: model download, mempalace.yaml room configuration, mining, and verification via search. Also trigger when the user says "memory index", "index memory of folder", or asks how to make a project's code semantically searchable with pi-go's MemPalace.
Lazy senior dev mode — always pick the simplest solution that works. Use this skill whenever writing, refactoring, or reviewing code to keep changes minimal: prefer the standard library, native platform features, and already-installed dependencies over new code or dependencies. Trigger when the user says "ponytail", "keep it simple", "simplest thing that works", "don't over-engineer", "lazy mode", or asks to avoid unnecessary abstractions, boilerplate, or premature complexity. The best code is the code never written.
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass
Go 1.24–1.26 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2 configuration, slog logging, and manual dependency injection with functional options. Always consult this skill before generating Go code for pi-go, even for small snippets, to ensure every output is idiomatic and modern.
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.