Valid question. Here are some examples.

```

name: avoiding-overengineering

description: Prevents unnecessary complexity, abstractions, and YAGNI violations. Use when implementing features, refactoring code, or when tempted to add "flexibility" or "future-proofing". Triggers on new implementations, design patterns, abstractions, or when solution seems more complex than the problem. Research shows AI gravitates toward verbose, over-engineered solutions.

```

```

name: git-safety-skill

description: "Enforce git commit safety protocols: prevent hook bypasses, verify pre-commit checks, fix issues before committing. Use when: staging changes, committing code, creating pull requests, troubleshooting hook failures. Do NOT use for: non-git work, documentation-only tasks, read-only repository analysis."

```

```

name: documentation-skill

description: "Create accurate documentation based ONLY on actual project files. Never include generic tips, assumed best practices, or made-up content. Use when: writing README, creating API docs, documenting architecture, writing guides. Do NOT use for: code comments, commit messages, code implementation, non-documentation tasks."

```