youlianvr
@youlianvr
Public Skills
architecture-simplicity
by youlianvr
'Use when the user wants to: design/redesign modules and layers, choose between a library and own code, understand why a project became a god-file, add an abstraction "for growth," update a DB schema without data loss, or during architecture review. Covers: YAGNI until second need, stdlib-first, modules by change reason, shared core + thin adapters, config outside repo + defaults in code, schema evolution without DROP, provider fallback chain, non-representable invalid states, dead code removal. Do not use for money (money-path-safety), hardening (hardening-observability), or refactoring (agent-refactor-safety).'
extract-design
by youlianvr
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens —
coding-style
by youlianvr
"Core principles for clean, maintainable, minimal code generation. Merged 2026-08-09 from coding-style.md + andrej-karpathy-skills.md + karpathy-coder + minimalist; extended 2026-08-15 with reviewed ponytail mechanics (DietrichGebert/ponytail, MIT) and the code-simplifier over-simplification guard (Anthropic claude-plugins-official). Enforces Karpathy's 4 principles (think before coding, simplicity first, surgical changes, goal-driven execution), the Minimalist Efficiency Ladder (YAGNI → reuse → stdlib → native → existing deps → one-liner → minimum code), clean-deletion rules, lazy-senior intensity levels (lite/full/ultra), trade-off markers, compressed output format, and a clarity-over-brevity guard against over-simplification. Use when writing, reviewing, or committing code; when the user asks for efficient code, fewer dependencies, YAGNI, 'don't overcomplicate', a 'karpathy check', or before claiming a diff is good."
documentation-writer
by youlianvr
"Diátaxis Documentation Expert. Write high-quality docs following Diátaxis framework (Tutorials, How-to, Reference, Explanation). Use when: write documentation, write docs, README, API docs, document something, document this, create tutorial, how-to guide."
epic-design
by youlianvr
Build immersive, cinematic 2.5D interactive websites using scroll storytelling,
dembrandt
by youlianvr
'
git-worktree-manager
by youlianvr
"Run parallel feature work safely with Git worktrees. Standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app. Optimized for multi-agent workflows where each agent or terminal session owns one worktree. Use when running multiple feature branches simultaneously, isolating experimental work, or coordinating multi-agent development across the same repo."
error-memory
by youlianvr
MUST USE after ANY command error, ANY failure, ANY mistake — auto-logging errors in ERROR_LOG.md. Trigger: error, fail, crash, broken, 403, 500, timeout, refused, ENOENT, command not found. On session start loads ERROR_LOG.md — knows what broke before and how to fix it.
gestalt-ui-organisation
by youlianvr
UI layout and grouping should follow Gestalt principles so users immediately understand which controls, commands,
brand-visual-language
by youlianvr
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements.
code-critic
by youlianvr
MUST USE when user asks to review code, find bugs, check for issues, audit code, code review, find bugs, check code, review, re-review, critique this, review this file, is this code good, what's wrong with, check for bugs, find problems. Sends code to proxy:4000 (deepseek-v4-flash) for merciless review. Returns structured report: score (0-10), critical count, each issue with severity/file/line/description/suggestion.
debug-incident-protocol
by youlianvr
Use when the user says: "doesn't work", "still broken", "hung/frozen", "disappeared after update", "used to work", "metric is zero but UI OK" — or when you need to investigate an incident, find the hang root cause, verify a process was actually restarted. Covers: facts before theories (storage/logs/PID), symptom vs root cause, silent failure by metrics, single consumer, restart ritual, hang localization via progress marker, timeouts, cache masking. Do not use for test writing (testing-discipline) and refactoring (agent-refactor-safety).
dataviz
by youlianvr
Choose and produce an appropriate chart/dashboard/visual explanation from data, with legible encodings and source/assumption notes.
grill-me
by youlianvr
"Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions 'grill me', 'grill with docs', 'stress-test against docs'. Two modes: plain grill (one question at a time, recommended answers) and docs-anchored grill (challenges the plan against CONTEXT.md glossary and docs/adr/ records, updating them inline)."
dolphin-windows-theme
by youlianvr
Make the Dolphin file manager (flatpak on GNOME/Fedora) look like Windows 11 File Explorer — dark gray #1F1F1F background, white text, blue #0078D4 selection. Use when the user says "dolphin dark theme", "dolphin like on Windows", "like Windows Explorer", "white text dolphin", "dolphin not dark", "theme dolphin dark", "windows 11 dark dolphin", or a flatpak Qt/KDE app ignores ~/.config/kdeglobals and stays light. Covers kdeglobals/color-scheme placement inside the flatpak sandbox, QT_QPA_PLATFORMTHEME=kde, flatpak overrides, and pixel-verification without seeing the screen.
disk-formatting
by youlianvr
Format, repartition and mount disks/partitions on Fedora Linux (ext4, btrfs, NTFS, FAT32, exFAT). Use when the user asks to format a disk, create a partition, fix a read-only NTFS drive, wipe a disk, make a USB stick, or mount a formatted disk with fstab.
android-adb-automation
by youlianvr
Dump+parse UI hierarchy, tap/type/swipe, handle MIUI security restrictions, read SMS from inbox, open incognito tabs. Use when the user wants to automate, control, or drive an Android phone/tablet via USB (form filling, app flows, SMS codes, signup flows), or when adb shell input fails with SecurityException/INJECT_EVENTS on MIUI/Xiaomi devices.
fable-domain
by youlianvr
Discuss a domain with the user, research it from real sources, then generate a trusted skill bundle for it - a step-by-step workflow with a flowchart, a domain adapter, a trap fixture, and a smoke eval. Use when the user says "/fable-domain <sector>", "make a skill for <domain>", "add a domain to the fable method", or "give a lesser model Fable's workflow for <domain>". The bundle is the deliverable; a workflow without its flowchart, sources, and trap is not done.
api-security
by youlianvr
Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication, authorization, rate-limit, and CI/CD testing.
explain-fingers
by youlianvr
Explain in simple terms — mode of maximum simplicity for a NON-technical audience. Use when: asked to "explain in simple terms", "like to a dinosaur/mammoth", "explain simply", "ELI5", "I don't understand", "try explaining again", or when context shows the person is lost (complex topic, lots of jargon, repeated "what?"). Mandatory: everyday analogy first line, steps one at a time, real example, short summary, comprehension check at the end. NOT for: technical breakdown for a developer (normal style there), short fact answers, when "briefly" was requested.
challenge
by youlianvr
"Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources. Use when before significant resource commitment, before presenting to a board or investors, when feedback has been one-sidedly positive, or when there is pressure to move fast and figure it out later."
changelog-discipline
by youlianvr
"Load when the user asks to maintain/update/create a CHANGELOG as a decision log: after code changes, when setting up changelog in a new project, when preparing a release, when asking 'why was it done this way' without an answer in code, or when a taken decision and rejected alternatives need to be documented — even if they don't call the file CHANGELOG but ask 'record what we decided / why this way / what we rejected'. Do not use for commit messages, PR descriptions, and user-facing release notes."
form-design
by youlianvr
'Forms have three layers of guidance: helper text below the input explains what to enter, placeholder shows the
button-states
by youlianvr
Every interactive element needs a complete set of visual states — rest, hover, active/pressed, focus, disabled,