What Digital Art Guide Quick Actually Does
I stumbled across Digital Art Guide Quick about three years ago when I was trying to streamline my illustration pipeline for client work. The concept is straightforward: it provides a set of procedural brush presets, layer templates, and workflow shortcuts designed to speed up the digital painting process, especially for concept art and character design. It's not a software replacement. It sits on top of programs like Krita, Clip Studio Paint, or Photoshop and gives you pre-configured tools that would otherwise take you twenty minutes to set up from scratch. The download page is a single repository at sapience-arts.net/downloads. You grab the latest release, unzip it into your application's resource folder, and restart your program. On Krita, that's ~/.local/share/krita/brushes/. On Photoshop, it's Program Files/Adobe/Adobe Photoshop 2024/Presets/Brushes. The installer script handles most of the path mapping automatically now, but if you're running a portable install or a flatpak version of Krita, you'll need to point it manually. Once installed, you get access to a new brush category called DQG. Within that category are six sub-sections: blocking brushes, rendering brushes, texture generators, perspective helpers, layer template packs, and export scripts. The blocking brushes are the bread and butter. They use low-opacity smudge-and-layer approaches that let you throw down rough shapes without committing to hard edges. The rendering brushes add controlled noise and gradient falloff that you'd normally have to paint by hand. Texture generators apply things like wood grain, fabric weave, or concrete scuffing through procedural masks rather than stamp images. The perspective helpers are a grid overlay system that snaps to custom vanishing points. Layer templates come pre-routed for standard tasks like base color, shadow pass, highlight pass, and final composite.
Here is where it gets useful. Instead of building a new canvas setup for every commission, you load a DQG template, which gives you five layers with proper naming, blending modes, and clipping masks already configured. That saves about ten to fifteen minutes per project. Over a week of work, that compounds. My typical client turnaround went from roughly two hours per piece down to about forty-five minutes for the initial blocking and rendering phase. I ran into a real problem early on though. I was working on a character sheet for a fantasy RPG and the perspective helpers kept snapping to a default one-point grid even after I repositioned the vanishing points. The issue was that DQG reads the last-used grid settings from the application's global preferences, and if you switch between projects quickly, those settings don't reset per-file. The workaround is to use the dedicated scene file template included in the download rather than starting from a blank canvas. Those templates lock the perspective metadata to the file itself instead of pulling it from global state. It cost me about three debugging sessions before I figured that out. The export scripts are another area people overlook. There is a batch exporter that takes your final composite and spits out web-optimized PNGs, print-ready TIFFs with embedded color profiles, and compressed JPEG versions all at once. For someone who delivers three format types to every client, this replaces what used to be a twenty-minute manual export routine with a single click. It handles ICC profile embedding correctly too, which is rare for third-party export tools.
When It Falls Apart
It is not a universal fix. The brush engine integration relies on whatever API the host application exposes, and Photoshop's scripting support is significantly more limited than Krita's. If you are primarily a Photoshop user, you will get the brushes and templates but the automation pieces are spotty. A few of the layer templates use features that only exist in Krita 5.0 and above, so if you are on an older version those layers will either fail to load or default to rasterized copies, which defeats the whole point of having editable masks. There is also a dependency on OpenColorIO for color management. If your studio pipeline uses a custom color space or a non-standard gamut like Display P3 without proper profile embedding, some of the export scripts will quietly produce files with incorrect color. I caught this once on a print job where the client returned proofs that were noticeably more saturated than the screen version. The fix was running the export through a manual color space conversion step before the batch script, but that adds time back into the workflow. If your team already has a mature internal brush library and custom template system, Digital Art Guide Quick might duplicate work rather than replace it. It is designed for people who either do not have a configured pipeline yet or who want a standardized baseline they can build on. The presets are opinionated in places, which means you will spend some time disabling or reassigning shortcuts to match your own habits. Factor in about two hours of initial customization before it feels native to how you actually work.
What Beginners Should Know Before Installing
Don't treat the presets as final output. They are starting points. The DQG brushes are deliberately aggressive on opacity and pressure curve sensitivity, which is useful for getting quick coverage but will look muddy if you don't build up layers gradually. I see people using the rendering brushes at full opacity on the first pass and then wondering why the paint looks flat. Start at thirty percent opacity and layer up. The texture generators work best when applied to separate layers with multiply or overlay blending rather than directly on your base color layer. Also, save your own modified versions. The default config files ship read-only in the installation folder, so any changes you make get wiped when you update. Copy the entire DQG folder to your own resource path before editing anything, then update your application's resource directories to point there. This way you keep your custom brush modifications intact across version updates.
