domain-specific-documentation
General rules
Optimize for token efficiency
- Use sub-agents to process documents (code, configuration, or other content) required for the task.
- Prefer programmatic extraction and classification over reading full document contents.
- Store hashes to detect changes programmatically, enabling caching of prior results.
- Generate and reuse utility scripts to avoid duplicate AI inference.
Don't reinvent the wheel
The domain may already have established programmatic ways to map system state or generate a documentation index. If such solutions exist, evaluate whether they fit your situation. Building on an existing, well-tested domain-specific solution is usually better than rolling your own, unless it requires significant changes or has unacceptable limitations.
Preparation
Establish detailed domain-specific documentation before working on actual tasks to improve token efficiency down the line.
More from viktor-ferenczi/skills
python-guidelines
Guiding principles for writing clear, concise, human readable and maintainable Python code.
20gcp-batch-inference
Running batch inference on Google Cloud (also known as Vertex AI)
18silent-cli
Environment 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.
12busybox-on-windows
How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
11recursive-language-model
Recursive 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.
9stabilization-loop
Stabilizes a software project by repeatedly running and testing it in a loop, fixing any issues.
6