github.com/Stirling-Tools/Stirling-PDF (link)

AGENTS.md

---
name: feature-walkthrough
description: >-
  Explain the full logic and process of the current branch end-to-end so someone
  with no prior knowledge of the task can understand, review, and reproduce it.
  Scopes the change from the branch diff, traces the flow across every layer it
  touches (frontend tool/hook/component, Java controller/service/endpoint, Python
  engine, config, i18n, tests), and produces a self-contained walkthrough document
  with Mermaid diagrams (sequence/flow/architecture), annota

---
name: pr-quiz
description: >-
  Quiz the PR author on their own branch before they request review, to prove they
  actually understand the change - especially code an AI wrote for them. Scopes the
  branch diff vs its base, reads the changed code, then asks graded questions about
  what changed, why, how it works, what it could break, and which edge cases it must
  handle. Presents all questions first, waits for the author's answers, then grades
  each honestly against the real code (Correct / Partial /

---
name: ui-walkthrough
description: >-
  Full UI investigation of the current branch's feature. Enumerates every view
  and state (empty, populated, loading, error, each dialog/menu/panel, responsive
  breakpoints, light + dark + RTL), captures them with the stubbed Playwright
  harness, assembles a single-image HTML walkthrough with a global light/dark
  toggle slider, then runs two review passes: visual/consistency (alignment,
  spacing, professionalism, dark/light parity, contrast, truncation) and
  UX

---
name: ui-before-after
description: >-
  Analyse a branch or PR and automatically capture before/after screenshots of
  every UI surface its changes touch, then pixel-diff the pairs to surface what
  actually changed and assemble PR-ready before/after montage images. Generic and
  diff-driven: it derives the capture targets from the diff (changed tools/routes →
  URLs) instead of hand-listing screens, captures "before" from the base branch and
  "after" from the head, then keeps only the views that vis

# AGENTS.md

This file provides guidance to AI Agents when working with code in this repository.

## Taskfile (Recommended)

This project uses [Task](https://taskfile.dev/) as a unified command runner. All build, dev, test, lint, and docker commands can be run from the repo root via `task <command>`. Run `task --list` to see all available commands.

Task `desc:` fields should describe **what** the task does, not **how** it does it. Keep them generic and stable: don't reference implementation details like al