gardening-skills-wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
Discover Tools skills, compare source repositories and read the instructions for each workflow.
Maintain skills wiki health - check links, naming, cross-references, and coverage
Write comments explaining WHAT and WHY, never temporal context or history
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
Use when building NuxtHub v0.10.4 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, mult...
Create a changelog entry for the kuberise.io website from RELEASE_NOTES.md
Update an existing OpenSpec change from a plan file or conversation context
Archive a completed change
Validates structural consistency, cleans up junk files (SCREAMING_TEXT.md, temp files), and performs comprehensive quality scans across codebase to identify critical bugs, logic errors, caching issues, and work...
This skill should be used when the user asks to "create web roles", "add web roles", "set up web roles", "add roles", "create roles for my site", "manage web roles", "add authenticated role", "add anonymous rol...
Supabase RLS 政策規範。Use when creating or modifying RLS policies (CREATE POLICY, ALTER POLICY), setting up Row Level Security, or working with database access control. Always use this skill for RLS design, po...
Full Windows desktop control. Mouse, keyboard, screenshots - interact with any Windows application like a human.
Use this skill when the user says 'Hetzner', 'VPS setup', 'server provisioning', 'deploy to VPS', 'hetzner-setup', 'cloud server', or needs to provision, harden, and deploy applications to a Hetzner Cloud serve...
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently...
Generate idiomatic Typst (.typ) code, edit existing Typst files, and answer Typst syntax questions. Use when working with Typst files (*.typ) or when the user mentions Typst markup, document creation, or format...
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
Create micro-commits (minimal incision) with at least one validation signal per commit.
Generate iterative `plan-N.md` files in the repo root (max N=5). Use only when asked; clarify before `plan-1.md`; stop at `plan-5.md`.
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
TRACE (Type/Readability/Atomic/Cognitive/Essential) lens for explaining code and proposing improvements (no edits applied).
Software surgery: contract → invariants → creative search → inevitable incision; minimal diff, compositional core, proof signal.
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity); requires a validation signal.
Unified shipping + TRACE self-review protocol (beads, proof, PR). Explicit-only.
Convert a project plan written in a Markdown file into a complete bd beads graph (tasks, subtasks, dependencies) using only bd for creation and edits, then review and optimize each bead. Use when asked to beadi...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.