khaneliman/khanelinix - Page 2

why

Investigate motivation, design rationale, and historical decisions behind code. Queries source control, issue trackers, docs, chat, observability, and error logs in parallel. Use for 'why does X work this way', 'why we picked Y', design rationale,…

Langue du texte source : anglais

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Langue du texte source : anglais

jj-toolkit

Use for working with Jujutsu (jj) history workflows, including hunk-level split/squash/diffedit/restore via `jj-hunk-tool`.

Langue du texte source : anglais

lua-toolkit

Neovim Lua plugin architecture, lazy loading, configuration APIs, commands, keymaps, health checks, type-aware tooling, tests, and LuaRocks distribution. Use when creating, refactoring, validating, or releasing a Neovim Lua plugin.

Langue du texte source : anglais

nix-toolkit

Nix operational workflows for package diffs, build failures, closure analysis, dependency forensics, flake maintenance, and evaluation performance. Use for diagnosing Nix builds or outputs; use writing-nix for expression and module authoring.

Langue du texte source : anglais

rust-toolkit

Rust and Cargo architecture, correctness, toolchain, concurrency, unsafe-code, testing, migration, and performance workflows for crates and workspaces. Use for Rust libraries, services, or CLIs; use bevy-toolkit for engine-specific Bevy work.

Langue du texte source : anglais

writing-nix

Write idiomatic and maintainable Nix code. Use when creating or refactoring Nix expressions, Home Manager or NixOS modules, overlays, packages, and flake outputs, especially when deciding module merge semantics, binding locality, option defaults, and…

Langue du texte source : anglais

pi-planning-with-files

Optional persistent file-based planning for multi-phase or long-running work that benefits from recovery across sessions or compaction. Use when requested or when persistence materially improves continuity; do not activate merely due to tool count or existing…

Langue du texte source : anglais

planning-with-files

Persistent file-based planning for complex or long-running work. Use when asked to plan, organize, research, or execute work requiring multiple phases or roughly 5+ tool calls. Keeps task_plan.md, findings.md, and progress.md recoverable across sessions and…

Langue du texte source : anglais

planning-with-files

Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+…

Langue du texte source : anglais

planning-with-files

Manus-style persistent file-based planning for AI coding agents: keeps task_plan.md, findings.md, and progress.md on disk so work survives context loss and /clear. Use when asked to plan out, break down, or organize a multi-step project, research task, or any…

Langue du texte source : anglais