DevUtilKit Documentation
The documentation hub is organized for engineers who need implementation detail, not high-level marketing summaries. Each guide explains boundaries, examples, and failure patterns so teams can diagnose issues with less guesswork.
How To Navigate The Docs
Start with SQL Select Runner if you are working on read-only query workflows, export limits, or operational safety controls. Continue with Query Safety to understand why statement restrictions exist and how validation behaves in edge cases.
For payload and transport issues, move through JSON formatting, Base64, URL encoding, and JWT guides in that order. This sequence matches common incident flow: inspect data shape first, then auth context, then transport boundaries.
What Makes These Guides Different
Each page is tied to concrete route behavior in DevUtilKit. Instead of abstract best practices, guides describe what the platform allows, what it blocks, and what to check when output looks suspicious.
You will see practical examples, troubleshooting cues, and links to tool routes so documentation can be validated immediately with real inputs.
Recommended Reading Paths
Path 1 (SQL workflow): SQL Select Runner -> Query Safety -> Export Options -> Supported Databases. Use this when building safe inspection workflows for product and support teams.
Path 2 (API debugging): JSON Formatting -> JWT Debugging -> URL Encoding -> Browser Privacy. Use this when diagnosing payload, auth, and transport issues across frontend-backend boundaries.
Related Links
Snapshot generated for search indexing and accessibility preview.