@micka33/pi-karpathy-skill 1.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 pi-karpathy-skill contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,62 @@
+# pi-karpathy-skill
+
+Pi package that provides the `karpathy-guidelines` skill to coding agents.
+
+The skill contains behavioral guidelines inspired by [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on common LLM coding pitfalls: think before coding, keep solutions simple, make surgical changes, and define verifiable success criteria.
+
+## Install
+
+From npm:
+
+```bash
+pi install npm:@micka33/pi-karpathy-skill
+```
+
+From this repository:
+
+```bash
+pi install git:git@github.com:Micka33/pi-karpathy-skill.git@latest
+```
+
+For project-local installation: Use the `-l` flag:
+
+```bash
+pi install -l npm:@micka33/pi-karpathy-skill@latest
+```
+
+## Usage
+
+Pi auto-discovers the skill from this package. You can also force-load it in a pi session:
+
+```text
+/skill:karpathy-guidelines
+```
+
+## Package contents
+
+```text
+skills/
+└── karpathy-guidelines/
+    └── SKILL.md
+```
+
+## Publishing
+
+Releases are published automatically by GitHub Actions when a semver tag is pushed:
+
+```bash
+git tag v0.1.0
+git push origin v0.1.0
+```
+
+The release workflow for an agent publishing the next version:
+
+1. Run `git fetch --tags --force && git tag --list 'v[0-9]*.[0-9]*.[0-9]*' --sort=-v:refname | head -n 1` to get the highest existing `vX.Y.Z` git tag in the repo.
+2. Choose the next semver version by bumping it according to the requested changes.
+3. Ask the user to confirm the next version you chose.
+4. Create and push a matching tag, for example `git tag v0.0.1 && git push origin main v0.0.1`.
+5. Verify the GitHub Actions release run succeeds.
+
+## Attribution
+
+Skill content is adapted from [`multica-ai/andrej-karpathy-skills`](https://github.com/multica-ai/andrej-karpathy-skills) and is licensed MIT.

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "@micka33/pi-karpathy-skill",
+  "version": "1.2.0",
+  "description": "Pi package providing the Karpathy Guidelines skill for safer, simpler coding-agent behavior.",
+  "license": "MIT",
+  "type": "module",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Micka33/pi-karpathy-skill.git"
+  },
+  "bugs": {
+    "url": "https://github.com/Micka33/pi-karpathy-skill/issues"
+  },
+  "homepage": "https://github.com/Micka33/pi-karpathy-skill#readme",
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [
+    "pi-package",
+    "pi-skill",
+    "agent-skills",
+    "coding-agent",
+    "karpathy"
+  ],
+  "files": [
+    "README.md",
+    "LICENSE",
+    "skills"
+  ],
+  "pi": {
+    "skills": [
+      "./skills"
+    ]
+  }
+}

package/skills/karpathy-guidelines/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: karpathy-guidelines
+description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
+---
+
+# Karpathy guidelines
+
+Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
+
+**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
+
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+
+```text
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.