Welcome to my personal Skills Repository.
This repository is a growing collection of reusable technical knowledge, implementation guides, and proven workflows that I create while building software, troubleshooting systems, contributing to open source, and experimenting with new technologies.
The goal is to capture solutions that have been tested in real-world scenarios so they can be quickly reused by both humans and AI coding assistants.
Each skill documents a complete process rather than just a collection of notes. Whenever possible, a skill should include:
- A clear overview of the problem being solved
- Prerequisites
- Step-by-step implementation instructions
- Copy-and-paste commands
- Architecture or workflow diagrams (when useful)
- Troubleshooting tips
- Validation and testing procedures
- References to official documentation
skills/
├── swift-nio-ssh-keyboard-interactive-testing/
│ ├── README.md
│ └── SKILL.md
├── ...
Over time this repository will grow to include topics such as:
- SSH and OpenSSH
- Docker and containers
- Swift development
- Networking
- Authentication and Identity
- macOS automation
- Linux administration
- Cloud infrastructure
- AI engineering
- Local LLM deployment
- Voice and TTS pipelines
- Development tooling
- Debugging techniques
Every skill should be practical, reproducible, well documented, easy to follow, tested before being added, and valuable enough to reuse in future projects.
If a workflow isn't repeatable, it isn't ready to become a skill.
- Solve the problem first.
- Verify the solution from a clean environment.
- Document every important step.
- Include troubleshooting notes and common pitfalls.
- Add reusable scripts or configuration where appropriate.
- Keep the documentation current as improvements are discovered.
Instead of rediscovering the same solutions, this repository serves as a long-term knowledge base for future projects and as a reference library that AI assistants can use to accelerate development and troubleshooting.
As new technologies evolve, this repository will continue to grow with new skills, updated best practices, and lessons learned from real implementations.
Build once. Document well. Reuse forever.