kaizakin
Usermy dotfiles - embrace Minimalism 🥂
Categories
Indexed Skills (6)
ai-slop-humanizer
A voice translation skill that strips away sterile, overly polished, or robotic AI-slop framing and rewrites text into an engaging, natural, and authentic human developer voice. It infuses structural variety, conversational asides, real-world physical analogies, and a relaxed peer-to-peer tone. Use this skill whenever the user says "humanize this", "make this sound human", "remove the AI smell", "de-ai this", "rewrite casually", "sound like a developer", or shares an AI-generated paragraph, draft, or technical summary and asks to make it readable and authentic. The skill accepts input as pasted text, a file path, or a URL. Output is the re-voiced version of the same content, retaining all core technical facts while completely transforming the delivery into a living human style.
codebase-onboarding
Generates a single, deeply researched ONBOARDING.md at the root of an open source (or internal) codebase, written for a brand-new contributor. Use this whenever someone wants to understand, explore, ramp up on, or document an unfamiliar repository — trigger phrases include "help me understand this codebase," "explain this repo," "onboard me to this project," "I just cloned this and I'm lost," "write an ONBOARDING.md," "what's the architecture here," "how is this repo organized," or any request to explain a project's purpose, tech stack, dependencies, architecture, or module layout. Also use it proactively whenever a user opens or references a repository they haven't worked in before and asks broad "what is this / how does this work" questions. Do NOT use this for narrow single-file explanations, API reference generation, or README-writing for a project the user is authoring themselves (that's promotional copy, not onboarding).
deep-explainer
Use this skill whenever the user asks a question they want genuinely explained — especially while learning an unfamiliar codebase, repository, library, or technical concept. Trigger it for any question ending in a "?", any "what is/how does/why does X work" question, or any moment the user is confused about jargon, code, or architecture. Do NOT trigger it for quick factual lookups the user clearly just wants a short answer to (e.g. "what's the syntax for X", "what year was Go released"), for competitive-programming or DSA practice where the user wants terse answer-only responses, or when the user has explicitly asked for brevity. When in doubt about a codebase question, trigger it — under-explaining is the failure mode this skill exists to prevent.
deep-explainer
Use this skill whenever the user asks a question they want genuinely explained — especially while learning an unfamiliar codebase, repository, library, or technical concept. Trigger it for any question ending in a "?", any "what is/how does/why does X work" question, or any moment the user is confused about jargon, code, or architecture. Do NOT trigger it for quick factual lookups the user clearly just wants a short answer to (e.g. "what's the syntax for X", "what year was Go released"), for competitive-programming or DSA practice where the user wants terse answer-only responses, or when the user has explicitly asked for brevity. When in doubt about a codebase question, trigger it — under-explaining is the failure mode this skill exists to prevent.
ai-slop-humanizer
A voice translation skill that strips away sterile, overly polished, or robotic AI-slop framing and rewrites text into an engaging, natural, and authentic human developer voice. It infuses structural variety, conversational asides, real-world physical analogies, and a relaxed peer-to-peer tone. Use this skill whenever the user says "humanize this", "make this sound human", "remove the AI smell", "de-ai this", "rewrite casually", "sound like a developer", or shares an AI-generated paragraph, draft, or technical summary and asks to make it readable and authentic. The skill accepts input as pasted text, a file path, or a URL. Output is the re-voiced version of the same content, retaining all core technical facts while completely transforming the delivery into a living human style.
codebase-onboarding
Generates a single, deeply researched ONBOARDING.md at the root of an open source (or internal) codebase, written for a brand-new contributor. Use this whenever someone wants to understand, explore, ramp up on, or document an unfamiliar repository — trigger phrases include "help me understand this codebase," "explain this repo," "onboard me to this project," "I just cloned this and I'm lost," "write an ONBOARDING.md," "what's the architecture here," "how is this repo organized," or any request to explain a project's purpose, tech stack, dependencies, architecture, or module layout. Also use it proactively whenever a user opens or references a repository they haven't worked in before and asks broad "what is this / how does this work" questions. Do NOT use this for narrow single-file explanations, API reference generation, or README-writing for a project the user is authoring themselves (that's promotional copy, not onboarding).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.