killerpdf-portable-editor
KillerPDF is a portable, single-EXE Windows PDF editor built with C#/WPF and PDFium — supports viewing, annotating, merging, splitting, signing, and printing PDFs with no installer, account, or telemetry.
What this skill does
# KillerPDF Portable PDF Editor Skill
> Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection.
KillerPDF is a single-EXE (~6 MB zipped), portable Windows PDF editor for .NET Framework 4.8. It renders PDFs via PDFium (Docnet.Core), supports inline text editing, annotations, freehand drawing, highlights, signatures, merge/split, full-text search, and printing — all without Adobe, accounts, or telemetry.
---
## What KillerPDF Does
| Capability | Details |
|---|---|
| Rendering | High-quality PDFium rendering via Docnet.Core |
| Annotation | Text boxes, freehand draw, highlight overlays |
| Editing | Inline text editing with font matching |
| Pages | Merge multiple PDFs, split selected pages, drag-and-drop reorder |
| Signatures | Draw/save reusable signatures, click to place |
| Search | Full-text search with highlighting, drag-select to copy |
| Print | Annotations flattened into output |
| Distribution | Single EXE, no runtime, no admin rights |
---
## Getting the Binary
```powershell
# Download latest prebuilt release
Invoke-WebRequest -Uri "https://github.com/SteveTheKiller/KillerPDF/releases/latest/download/KillerPDF.zip" -OutFile "KillerPDF.zip"
Expand-Archive -Path "KillerPDF.zip" -DestinationPath ".\KillerPDF"
.\KillerPDF\KillerPDF.exe
```
No installer, no admin rights required. Just unzip and run.
---
## Building from Source
### Requirements
- Windows 10/11 x64
- .NET 8 SDK or later (to build; output targets .NET Framework 4.8)
- Git
### Clone and Build
```powershell
git clone https://github.com/SteveTheKiller/KillerPDF.git
cd KillerPDF
dotnet publish -c Release
```
Output lands in `bin/Release/net48/publish/`. The publish step produces:
- `KillerPDF.exe` — single Costura-bundled executable
- `KillerPDF-<version>-src.zip` — GPL3 corresponding source archive
### Project Structure
```
KillerPDF/
├── App.xaml / App.xaml.cs # Application entry, theming
├── MainWindow.xaml / .cs # Primary WPF window, toolbar, page canvas
├── PdfDocument.cs # PDFium wrapper (Docnet.Core), load/save/render
├── PageViewModel.cs # Page data binding, annotation layer
├── AnnotationCanvas.cs # Custom Canvas for drawing/annotation
├── SignatureManager.cs # Save/load/place signatures
├── MergeWindow.xaml / .cs # Merge multiple PDFs UI
├── SplitWindow.xaml / .cs # Page selection and split UI
├── SearchPanel.xaml / .cs # Full-text search UI
├── PrintHelper.cs # Flatten annotations and print
├── Models/
│ ├── Annotation.cs # Base annotation model
│ ├── TextBoxAnnotation.cs
│ ├── DrawingAnnotation.cs
│ └── HighlightAnnotation.cs
└── Resources/
└── Icons/ # SVG/PNG toolbar icons
```
---
## Key Dependencies
```xml
<!-- KillerPDF.csproj (simplified) -->
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>net48</TargetFramework>
<UseWPF>true</UseWPF>
<AssemblyName>KillerPDF</AssemblyName>
</PropertyGroup>
<ItemGroup>
<!-- PDFium rendering -->
<PackageReference Include="Docnet.Core" Version="2.6.0" />
<!-- Single-EXE bundling -->
<PackageReference Include="Costura.Fody" Version="5.7.0" />
<PackageReference Include="Fody" Version="6.8.0" />
</ItemGroup>
</Project>
```
---
## Core Patterns and Code Examples
### Opening and Rendering a PDF Page
```csharp
using Docnet.Core;
using Docnet.Core.Models;
using System.Windows.Media.Imaging;
using System.Runtime.InteropServices;
public class PdfDocument : IDisposable
{
private IDocLib _docLib;
private IDocReader _docReader;
private readonly string _filePath;
public int PageCount { get; private set; }
public void Open(string filePath, string password = "")
{
_filePath = filePath;
_docLib = DocLib.Instance;
_docReader = string.IsNullOrEmpty(password)
? _docLib.GetDocReader(filePath, new PageDimensions(1080, 1920))
: _docLib.GetDocReader(filePath, password, new PageDimensions(1080, 1920));
PageCount = _docReader.GetPageCount();
}
public BitmapSource RenderPage(int pageIndex, double dpi = 150)
{
using var pageReader = _docReader.GetPageReader(pageIndex);
int width = pageReader.GetPageWidth();
int height = pageReader.GetPageHeight();
var rawBytes = pageReader.GetImage(); // BGRA byte array
var bitmap = new WriteableBitmap(width, height, dpi, dpi,
System.Windows.Media.PixelFormats.Bgra32, null);
bitmap.WritePixels(
new System.Windows.Int32Rect(0, 0, width, height),
rawBytes, width * 4, 0);
bitmap.Freeze();
return bitmap;
}
public string GetPageText(int pageIndex)
{
using var pageReader = _docReader.GetPageReader(pageIndex);
return pageReader.GetText();
}
public void Dispose()
{
_docReader?.Dispose();
_docLib?.Dispose();
}
}
```
### Annotation Model Hierarchy
```csharp
// Models/Annotation.cs
public abstract class Annotation
{
public Guid Id { get; } = Guid.NewGuid();
public int PageIndex { get; set; }
public System.Windows.Rect Bounds { get; set; }
public double Opacity { get; set; } = 1.0;
public abstract UIElement ToUIElement();
public abstract void FlattenToPdfPage(PdfPage page);
}
// Models/TextBoxAnnotation.cs
public class TextBoxAnnotation : Annotation
{
public string Text { get; set; } = "";
public string FontFamily { get; set; } = "Arial";
public double FontSize { get; set; } = 12;
public System.Windows.Media.Color Color { get; set; }
= System.Windows.Media.Colors.Black;
public override UIElement ToUIElement()
{
var tb = new TextBox
{
Text = Text,
FontFamily = new System.Windows.Media.FontFamily(FontFamily),
FontSize = FontSize,
Foreground = new System.Windows.Media.SolidColorBrush(Color),
Background = System.Windows.Media.Brushes.Transparent,
BorderThickness = new Thickness(0),
AcceptsReturn = true,
Width = Bounds.Width,
Height = Bounds.Height,
Opacity = Opacity,
};
Canvas.SetLeft(tb, Bounds.X);
Canvas.SetTop(tb, Bounds.Y);
return tb;
}
public override void FlattenToPdfPage(PdfPage page)
{
// Write text at PDF coordinates using PdfSharp or iTextSharp
// KillerPDF uses PDFium for reading and a lightweight writer for output
}
}
// Models/HighlightAnnotation.cs
public class HighlightAnnotation : Annotation
{
public System.Windows.Media.Color HighlightColor { get; set; }
= System.Windows.Media.Colors.Yellow;
public override UIElement ToUIElement()
{
var rect = new System.Windows.Shapes.Rectangle
{
Fill = new System.Windows.Media.SolidColorBrush(
System.Windows.Media.Color.FromArgb(
(byte)(Opacity * 128),
HighlightColor.R, HighlightColor.G, HighlightColor.B)),
Width = Bounds.Width,
Height = Bounds.Height,
};
Canvas.SetLeft(rect, Bounds.X);
Canvas.SetTop(rect, Bounds.Y);
return rect;
}
public override void FlattenToPdfPage(PdfPage page) { /* flatten */ }
}
```
### Freehand Drawing on the Annotation Canvas
```csharp
// AnnotationCanvas.cs — custom WPF Canvas
public class AnnotationCanvas : Canvas
{
private Polyline _currentStroke;
private List<Point> _points = new();
public System.Windows.Media.Color PenColor { get; set; }
= System.Windows.Media.Colors.Red;
public double PenThickness { get; set; } = 2.0;
public bool IsDrawingMode { get; set; }
protected override void OnMouseLeftButtonDown(MouseButtonEventArgs e)
{
if (!IsDrawingMoRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.