- 14 skills
- 0 followers
- 2 days ago last updated
- ▌ Safe Commands · viktor-ferenczi bundleCollection of safe, read-only CLI commands for 149 tools. Environment variables and parameters for running command line programs reliably without modifying system state. Includes query-only modes, dry-run options, and non-destructive alternatives.
- ▌ Consistency Check · viktor-ferencziFinds and fixes internal inconsistencies in a software project — code vs configuration vs documentation drift, plus linter findings. Use after a larger change or refactoring, before a release, or when the user asks to check/clean up the consistency of the project.
- ▌ Python Guidelines · viktor-ferencziGuiding principles for writing clear, concise, human readable and maintainable Python code. Use whenever writing, refactoring, or reviewing Python code.
- ▌ Stabilization Loop · viktor-ferencziIterates on a locally runnable project (typically a server with a test suite) until it builds, runs, and passes all tests cleanly, fixing failures between runs. Use when tests or the running application are failing or flaky after changes and the user wants to loop until green. Requires a local development setup — never run against production.
- ▌ Dotnet CLI Fix Loop · viktor-ferencziIterates on a .NET CLI project buildable with `dotnet build` until it builds and runs without errors.
- ▌ GCP Batch Inference · viktor-ferencziRun Gemini batch inference on Google Cloud Vertex AI. Use when the user wants to process a large number of prompts asynchronously and cheaply (50% discount) on GCP — bulk classification, annotation, extraction, or generation — from Cloud Storage JSONL files or BigQuery tables.
- ▌ Godot Documentation · viktor-ferencziInstalls and serves an offline copy of the official Godot Engine documentation (getting started guides, tutorials, API class reference, engine details). Use when working on a Godot project or GDScript code and you need authoritative API or engine reference. On first use it downloads the docs by cloning godotengine/godot-docs (requires network access and a few hundred MB of disk).
- ▌ Swdev Best Practices · viktor-ferenczi bundleBest practices to follow and principles to adhere to during software development. Use when designing, writing, refactoring, or reviewing code in any language, or when the user asks which principle applies to a design decision.
- ▌ Token Saving Techniques · viktor-ferencziA list of techniques for reducing token usage while working on complex tasks. Use this skill when the task at hand involves working with a significant number of documents or resources.
- ▌ Recursive Language Model · viktor-ferenczi bundleRecursive Language Model workflow for processing documents that exceed context window limits. Uses a persistent Python REPL and subordinate agents to chunk, search, and analyze large context files.
- ▌ Structured Documentation · viktor-ferencziGenerate a verified, modular handbook from a large source-code or document tree, then keep it cheap to refresh as the inputs change. Use when the documents are numerous, relate to each other in intricate ways, or their total size exceeds the context window — and you need a navigable TOC/Index with verified cross-references rather than an ad-hoc summary.
- ▌ Bizzfactory Document Downloader · viktor-ferenczi bundleDownload all of a client's documents from the Bizz Factory portal (portal.bizzfactory.se) into a local folder tree that mirrors the page, without converting files or causing any side effects. Use when the user wants to back up, archive, or bulk-download documents from their BizzFactory / Bizz Factory portal account, or mentions a portal.bizzfactory.se/documents/<uuid> URL.
- ▌ Silent CLI · viktor-ferenczi bundleEnvironment variables and parameters for running command line programs reliably in non-interactive environments (unattended). Includes silent modes, color/disable TTY, and reduced output options for 155 CLI tools.
- ▌ Sdl3 Wiki · viktor-ferenczi bundleComplete offline copy of the SDL3 (Simple DirectMedia Layer 3) wiki in CommonMark format. Use this skill whenever the user is working with SDL3 — writing or porting code that calls SDL_*, asking about SDL subsystems (audio, video, GPU, input, events, render, surface, gamepad, joystick, haptic, threads, file I/O, etc.), looking up an SDL function/struct/enum/macro signature, migrating from SDL2 to SDL3, or referencing SDL3 hints/properties/keycodes/scancodes. Prefer this skill over guessing API shapes from memory — SDL3 changed many SDL2 names and signatures.