bacnh85
- 21 skills
- 0 followers
- 3 hours ago last updated
- ▌ Agy Delegate · bacnh85Delegate bulk implementation, scaffolding, repetitive refactors, and exhaustive test generation to the Antigravity CLI (agy).
- ▌ Cron · bacnh85Use when the user wants scheduled, recurring, or periodic tasks in Pi — cron jobs, reminders, jobs at a specific time ("every morning at 9", "weekly monday", "in 30 minutes"), or automation that should run without being asked each time.
- ▌ Pi Web · bacnh85Web search, content extraction, site crawling, page capture, real-browser interaction (trusted click/type/evaluate in headless Chrome), Gemini web-tier research, image generation, and one-off ChatGPT-web/gateway chat via the pi-web extension. Use when the user needs current web search results, documentation lookup, factual research, AI-synthesized research with sources (Gemini Deep Research), image generation from text, one-off ChatGPT/gateway chat, source discovery, URL-to-markdown extraction, JSON extraction from websites, site URL discovery, site crawling, page screenshots/PDFs, or clicking buttons/typing/verifying UI behavior in a real browser. Use when the user mentions searching the web, finding docs, looking something up, researching deeply, generating/creating an image, asking another model, ChatGPT chat/images, scraping/extracting content from a URL, capturing a page, or interacting with a page (click a button, submit a form).
- ▌ Kicad · bacnh85Design KiCad schematics and PCB layouts via the Konnect bridge. Use when the user wants to create/edit KiCad schematics or PCBs, place and wire components, route traces, run ERC/DRC, export Gerbers/BOM/PDF/3D, search JLCPCB parts, use reference circuits, or do manufacturing prep. Trigger on "KiCad", "schematic", "PCB", "layout", "route traces", "ERC", "DRC", "Gerber", "BOM", "footprint", "design rule check", "pick-and-place", or any CAD/EDA design task.
- ▌ Munin · bacnh85Use Munin long-term memory before non-trivial repo work, bug fixes with recurring symptoms, architecture/dependency/setup changes, and when storing durable verified knowledge for future sessions. Search, retrieve, verify, list, store, or share project knowledge across sessions. Use munin_search for pre-work context, munin_store for post-work storage. Use when the user mentions memory, recall, remember, past work, previously, store this, document this, or when work could benefit from prior project knowledge.
- ▌ UX Design · bacnh85Anti-slop UI/UX design discipline for AI-generated interfaces. Enforces industrial-design principles (Dieter Rams: honest, thorough to the last detail, as little design as possible) so output is a defensible system, not statistical-default slop (purple glow, shadow-as-texture, missing states) — and equally not the correct-but-forgettable default (Inter, blue accent, timid sizes). Covers the Constraint-First method: own the system via a lintable DESIGN.md, write a 5-field brief, DERIVE A DIRECTION from the subject (mood, type voice, color mood, signature element), generate inside constraints, normalise, render-and-inspect with vision, pass a measurable slop-audit gate. Works deterministically with text-only models (DeepSeek-v4, GLM-5.2, Kimi K3); agy/Gemini/Claude is optional polish, never the review gate. Use when designing or building any UI — web, mobile, or desktop. Active via /ux lite|strict|off.
- ▌ Evolve · bacnh85Trajectory-based self-learning loop for Pi. Automatically captures tool-call trajectories, reflects on them to extract transferable learnings (strategy/recovery/optimization), persists to Munin or local JSONL, and injects recent learnings into future sessions. Use evolve_reflect after fixing a bug or recovering from an error; use evolve_save to persist each learning. Triggered when the user mentions self-learning, self-improvement, learning from experience, trajectory analysis, or when a multi-step task reveals a transferable lesson.
- ▌ UX Capture · bacnh85Capture playbook for the pi-ux render-and-inspect loop: screenshotting a UI you just built via local headless Chrome vs web_screenshot, daemon reachability (localhost vs LAN IP vs host.docker.internal), SSRF-protected daemons, and cloudflared tunnels. Load when setting up render inspection or when a UI screenshot capture fails.
- ▌ UX Presets · bacnh85Reference design-system presets for ux-design. Anti-slop shortcuts: instead of inventing tokens, elevation, and state contracts from scratch, reuse one of these battle-tested systems (shadcn/ui, Material 3, Radix), drop in a medium-tuned DESIGN.md starter (Web or Mobile), or adopt a style-direction starter (Editorial print, Ledger, Warm consumer) that already carries a point of view. Use when starting a new UI project with no existing design system, when Step 0 (Own the system) of the ux-design method has nothing to reuse, or when asked for a starter token set. These are REFERENCES only — pi-ux never bundles CSS.
- ▌ UX Routing · bacnh85Reference table for dividing UX work across models in the Pi ecosystem — who defines the DESIGN.md scaffold, who generates variants, who renders and inspects, what reviews. Consult when delegating design work to other models (agy/Gemini, Claude, DeepSeek, Kimi) or when deciding whether the main model should do a step itself. Not injected into every turn by design; the always-true core rule lives in ux-design: the deterministic gate reviews, a multimodal model looks at its own render, and taste lives in the direction brief, not in the model choice.
- ▌ Ponytail · bacnh85Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
- ▌ Notebooklm · bacnh85Google NotebookLM — notebooks, sources, grounded chat, research, and Studio artifacts (Audio Overviews, video, slides, reports, quizzes, etc.) via the notebooklm-py CLI bridge (v0.7.3).
- ▌ Selfskills · bacnh85Use when improving pi skills with skill_manage (list/read/patch/create/restore). Patch gaps same-turn with minimal diffs; create only recurring procedures.
- ▌ Ponytail Debt · bacnh85Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/skill:ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
- ▌ Ponytail Gain · bacnh85Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /skill:ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
- ▌ Ponytail Help · bacnh85Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /skill:ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
- ▌ Ponytail Audit · bacnh85Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/skill:ponytail-audit". One-shot report, does not apply fixes.
- ▌ Ponytail Review · bacnh85Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /skill:ponytail-review. Complements correctness-focused review, this one only hunts complexity.
- ▌ Pi Windows Tools · bacnh85Provides Windows-native tool manipulation: shell profiles, path conversion, command execution, WSL bridge, safety policy, and developer tool discovery. Enables Pi to work correctly with PowerShell, cmd, Git Bash, and WSL.
- ▌ Obsidian Vault Discipline · bacnh85 bundleEnforce using the Obsidian tool (not bash) for all vault file operations. Trigger whenever the user mentions Obsidian, vault, notes, moving files in the vault, archiving notes, or any file operation inside an Obsidian vault path. Also trigger when the agent is about to use bash mv/cp/rm/rename on paths containing "obsidian", "hermes", "vault", ".obsidian", or similar vault indicators. Agents commonly default to bash for file operations — this skill prevents that mistake. Use BEFORE any file operation when vault paths are involved.
- ▌ A2a · bacnh85A2A (Agent2Agent) Protocol v1.0 bidirectional communication. Distribute tasks to remote agents (Hermes, ADK, LangChain, CrewAI, any A2A peer) and be called by them. Use when delegating work across agents/machines/frameworks, doing parallel multi-agent fan-out, or when another agent needs to call Pi. Trigger on "a2a", "agent-to-agent", "delegate to another agent", "ask agent X", "call remote agent", "multi-agent", "Hermes", "task distribution".