### Installing Build Dependencies on Ubuntu/Debian Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This command installs Pandoc, XeLaTeX, and recommended LaTeX fonts on Ubuntu or Debian-based systems using `apt-get`. These packages are essential for converting Markdown to various book formats, including PDF. ```bash sudo apt-get install pandoc texlive-xetex texlive-fonts-recommended texlive-fonts-extra ``` -------------------------------- ### Installing Build Dependencies on macOS with Homebrew Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md These commands install Pandoc and MacTeX (or BasicTeX) on macOS using Homebrew. Pandoc is for document conversion, and MacTeX provides XeLaTeX for PDF generation, enabling the build system to function. ```bash brew install pandoc brew install --cask mactex # or basictex for a smaller installation ``` -------------------------------- ### Installing Additional Fonts for XeLaTeX on Ubuntu/Debian Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This command installs additional fonts (Liberation and CMU) on Ubuntu/Debian systems. These fonts are often required by XeLaTeX for proper rendering of the PDF output, especially for specific book layouts. ```bash sudo apt-get install fonts-liberation fonts-cmu ``` -------------------------------- ### Displaying Make Help Commands Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This `make` command displays a list of all available build commands and their descriptions as defined in the Makefile. It helps users discover and understand the build system's capabilities. ```bash make help ``` -------------------------------- ### Building All Book Formats with Make Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This `make` command initiates the build process for all defined book formats (HTML, digital PDF, print PDF) as configured in the Makefile. It's the recommended way to generate all outputs simultaneously. ```bash make ``` -------------------------------- ### Building All Book Formats Directly with Build Script Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This command executes the main build script directly to generate all book formats. It provides an alternative to `make` for users who prefer direct script execution. ```bash bash build/scripts/build.sh ``` -------------------------------- ### Building All Book Formats Using Docker Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This Docker command runs the `human-algorithm-builder` container to build all book formats. It mounts the current directory as `/book` inside the container, ensuring the build process uses the local project files. ```bash docker run --rm -v $(pwd):/book human-algorithm-builder make all ``` -------------------------------- ### Building Specific Book Formats Using Docker Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md These Docker commands allow building individual book formats within the containerized environment. They mount the local project and execute the specific `make` target, providing isolated and reproducible builds. ```bash docker run --rm -v $(pwd):/book human-algorithm-builder make html docker run --rm -v $(pwd):/book human-algorithm-builder make pdf-digital docker run --rm -v $(pwd):/book human-algorithm-builder make pdf-print ``` -------------------------------- ### Building Specific Book Formats Directly with Build Script Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md These commands allow building individual book formats by passing the desired format as an argument to the build script. This offers granular control over the output generation without using `make`. ```bash bash build/scripts/build.sh html bash build/scripts/build.sh pdf-digital bash build/scripts/build.sh pdf-print ``` -------------------------------- ### Displaying Make Help Commands Using Docker Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This Docker command runs the `make help` target inside the container, displaying all available build commands. It's useful for understanding the build options within the Dockerized environment. ```bash docker run --rm -v $(pwd):/book human-algorithm-builder make help ``` -------------------------------- ### Building Specific Book Formats with Make Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md These `make` commands allow building individual book formats (HTML, digital PDF, print PDF) separately. This is useful for testing specific outputs or for faster iteration during development. ```bash make html make pdf-digital make pdf-print ``` -------------------------------- ### Displaying Build Help Information (Makefile) Source: https://github.com/jaydoubleu/agentic-book/blob/main/README.md This command invokes the 'make' utility to display a list of available build targets and their descriptions, providing a quick reference for interacting with the project's build system. It's a common practice in projects using Makefiles to offer a 'help' target. ```Makefile make help ``` -------------------------------- ### Building Book Formats with Make Source: https://github.com/jaydoubleu/agentic-book/blob/main/README.md This snippet provides `make` commands to build the 'Agentic Book' into various formats (HTML, digital PDF, print PDF) and to clean the build directory. It leverages the project's `Makefile` for automation, simplifying the compilation process for different output types. ```bash # Build all formats (HTML and both PDF versions) make all # Build specific formats make html make pdf-digital make pdf-print # Clean build directory make clean ``` -------------------------------- ### Building Docker Image for Book Builder Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This command builds a Docker image named `human-algorithm-builder` from the Dockerfile in the project root. This image encapsulates all necessary dependencies for building the book in a consistent, isolated environment. ```bash docker build -t human-algorithm-builder . ``` -------------------------------- ### Standard Chapter Template for Book Manuscript (Markdown) Source: https://github.com/jaydoubleu/agentic-book/blob/main/CLAUDE.md This Markdown snippet provides a standardized template for each chapter of 'The Human Algorithm.' It defines the required sections, such as 'Opening Scene,' 'The AI Mirror,' and 'Practical Applications,' along with suggested word counts for each. This template ensures consistency in chapter structure and content across the entire book. ```Markdown # Chapter [Number]: [Title] ## Opening Scene [Relatable human scenario, 500-800 words] ## The AI Mirror [Introduce parallel LLM concept, 800-1000 words] ## What This Reveals [Deep dive into human nature insights, 1500-2000 words] ## Practical Applications [Exercises and real-world applications, 800-1000 words] ## Reflection Questions [3-5 thought-provoking questions] ## Chapter Summary [Key takeaways, 200-300 words] ``` -------------------------------- ### Defining Project Directory Structure for 'The Human Algorithm' (Markdown) Source: https://github.com/jaydoubleu/agentic-book/blob/main/CLAUDE.md This snippet illustrates the recommended directory structure for the 'agentic-book' project. It organizes the manuscript, notes, and resources into distinct folders, facilitating clear navigation and content management for authors and collaborators. This structure ensures all project assets are logically grouped and easily accessible. ```Markdown /agentic-book/ ├── CLAUDE.md (this file) ├── README.md (book overview and reading guide) ├── PROGRESS.md (detailed progress tracking) ├── /manuscript/ │ ├── 00-front-matter.md (title, credits, TOC) │ ├── 01-introduction.md │ ├── 02-chapter-1-hallucination-paradox.md │ ├── 03-chapter-2-grounding-ourselves.md │ └── ... (subsequent chapters) ├── /notes/ │ ├── chapter-outlines.md │ ├── research-notes.md │ └── revision-log.md └── /resources/ ├── references.md └── glossary.md ``` -------------------------------- ### Cleaning Output Directory with Make Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This `make` command removes all generated output files from the `output/` directory. It's used to clean up previous builds and ensure a fresh build process. ```bash make clean ``` -------------------------------- ### Progressive Prompting for Complex Understanding - Plain Text Source: https://github.com/jaydoubleu/agentic-book/blob/main/manuscript/06-chapter-5-prompting-personalities.md This snippet demonstrates the 'Prompt Scaffolding' technique, which involves breaking down a complex request into a series of progressive, smaller prompts. This approach builds understanding and buy-in incrementally, leading to more effective and collaborative outcomes. ```Plain Text 1. "What are the current pain points in customer service?" 2. "Which of these problems impact customers most?" 3. "What would ideal customer service look like?" 4. "What's one small improvement we could make this week?" 5. "How could we measure if it's working?" ``` -------------------------------- ### Documenting Task Assignment Prompt Template - Plain Text Source: https://github.com/jaydoubleu/agentic-book/blob/main/manuscript/06-chapter-5-prompting-personalities.md This snippet presents a template for consistent task assignments, another component of 'Prompt Documentation.' It ensures clarity on the specific deliverable, context, available resources, deadline, and success criteria, improving task execution and accountability. ```Plain Text Task: [specific deliverable] Context: [why this matters] Resources: [what's available] Deadline: [when needed] Success criteria: [what good looks like] ``` -------------------------------- ### Cleaning Output Directory Using Docker Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This Docker command executes the `make clean` target within the container to remove all generated output files. It ensures a clean state for subsequent builds in the Docker environment. ```bash docker run --rm -v $(pwd):/book human-algorithm-builder make clean ``` -------------------------------- ### Cleaning Output Directory Directly with Build Script Source: https://github.com/jaydoubleu/agentic-book/blob/main/build/README.md This command uses the build script to remove all generated files from the `output/` directory. It's an alternative to `make clean` for tidying up the build environment. ```bash bash build/scripts/build.sh clean ``` -------------------------------- ### Documenting Meeting Invite Prompt Template - Plain Text Source: https://github.com/jaydoubleu/agentic-book/blob/main/manuscript/06-chapter-5-prompting-personalities.md This snippet provides a template for consistent meeting invitations, part of the 'Prompt Documentation' strategy. It ensures all necessary information (purpose, pre-work, roles, duration, outcome) is clearly communicated, leading to more productive meetings. ```Plain Text Purpose: [specific goal] Pre-work: [if any] Your role: [what's expected] Duration: [time] Outcome: [what we'll have after] ``` -------------------------------- ### Meta-Prompting for Preferred Communication - Plain Text Source: https://github.com/jaydoubleu/agentic-book/blob/main/manuscript/06-chapter-5-prompting-personalities.md This snippet illustrates 'Meta-Prompting,' a technique where you ask the recipient how they prefer to be prompted or receive information. This shows respect for their processing model and often leads to better, more tailored results by understanding their needs for context, format, and timing. ```Plain Text - "What's the best way to keep you informed about this project?" - "How do you prefer to receive complex information?" - "What background do you need to make this decision?" - "What format would make this easiest to process?" ``` -------------------------------- ### Tracking Chapter Status within Markdown Files (Markdown) Source: https://github.com/jaydoubleu/agentic-book/blob/main/CLAUDE.md This Markdown comment block is used to embed metadata directly within each chapter file, providing a quick overview of its progress. It tracks essential details like word count, current status (Draft, Revision, Final), key concepts covered, and the last update date, aiding in context management and progress tracking. ```Markdown ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.