From 3480f6d4d46cc78761b65ee43dc92e7d1adb99e7 Mon Sep 17 00:00:00 2001
From: syntaxbullet <syntaxbullet@protonmail.com>
Date: Thu, 21 May 2026 18:41:44 +0200
Subject: [PATCH] Initial skills collection

---
 .gitignore                    |  8 +++++
 README.md                     | 64 +++++++++++++++++++++++++++++++++++
 skills/example-skill/SKILL.md | 19 +++++++++++
 3 files changed, 91 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 README.md
 create mode 100644 skills/example-skill/SKILL.md

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..25bc044
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,8 @@
+.DS_Store
+.env
+.direnv/
+node_modules/
+dist/
+build/
+.venv/
+__pycache__/
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..e2ac5ce
--- /dev/null
+++ b/README.md
@@ -0,0 +1,64 @@
+# LLM Agent Skills
+
+A personal collection of reusable skills for LLM coding agents.
+
+Skills are small, focused instruction packs that teach an agent how to perform a
+specific workflow consistently. A good skill captures the judgment, conventions,
+commands, file layout, and verification steps that should be reused across
+projects.
+
+## Goals
+
+- Keep useful agent workflows portable across machines and projects.
+- Capture repeatable setup, debugging, writing, and automation patterns.
+- Prefer concise instructions over large prompt dumps.
+- Make skills easy to inspect, edit, and version.
+- Treat skills as living documentation for how I like agents to work.
+
+## Repository Layout
+
+```text
+skills/
+  README.md
+  skills/
+    example-skill/
+      SKILL.md
+```
+
+Each skill should live in its own directory and include a `SKILL.md` file.
+Supporting scripts, templates, references, or assets can live next to that file
+when they make the skill easier to use.
+
+## Skill Format
+
+A minimal skill should include:
+
+- A short name and description.
+- When the skill should be used.
+- The workflow the agent should follow.
+- Any commands, scripts, or files the agent should prefer.
+- Verification steps, if the skill changes files or system state.
+
+## Example
+
+```text
+skills/
+  macos-setup/
+    SKILL.md
+    scripts/
+      apply-defaults.sh
+```
+
+## Writing Principles
+
+- Be specific about triggers.
+- Keep instructions operational.
+- Prefer checklists and concrete commands.
+- Avoid vague personality guidance.
+- Include safety notes for destructive or irreversible steps.
+- Keep generated artifacts and scratch work out of the repo unless they are part
+  of the skill.
+
+## License
+
+Unlicensed for now. Add a license later if these skills become public or shared.
diff --git a/skills/example-skill/SKILL.md b/skills/example-skill/SKILL.md
new file mode 100644
index 0000000..eb1217b
--- /dev/null
+++ b/skills/example-skill/SKILL.md
@@ -0,0 +1,19 @@
+# Example Skill
+
+Use this directory as a template for new skills.
+
+## When To Use
+
+Use this skill when you want to demonstrate the expected shape of a skill in this
+repository.
+
+## Workflow
+
+1. State why the skill applies.
+2. Read only the files needed for the current task.
+3. Follow the documented workflow.
+4. Verify the outcome before reporting completion.
+
+## Notes
+
+Replace this example with real skills over time, or keep it as a reference.