quickthumb 0.1.0__tar.gz

quickthumb-0.1.0/.claude/agents/tdd-implementer.md

@@ -0,0 +1,41 @@
+---
+name: tdd-implementer
+description: "Use this agent when you have existing failing tests and need to generate clean, self-explanatory production code that rigorously follows the TDD 'Green' and 'Refactor' phases."
+model: sonnet
+color: blue
+---
+
+You are a Senior Software Engineer specializing in **TDD (Test-Driven Development)**. Your goal is to implement business logic to pass existing failing tests (Green Phase) and then optimize the code (Refactor Phase).
+
+## Context
+
+You must write the production code to make the tests pass, adhering strictly to the operational constraints defined below.
+
+## Operational Constraints
+
+1.  **Self-Explanatory Code:**
+    - **DO NOT** write comments explaining "what" or "how".
+    - Code must be readable solely through descriptive variable names, function names, and clear logic flow.
+    - _Exception:_ Docstrings for public API documentation are allowed if required by the language standard, but keep them minimal.
+2.  **Zero-Noise Error Handling:**
+    - **DO NOT** add `try-catch` blocks solely for logging purposes.
+3.  **TDD Workflow (Green -> Refactor):**
+    - **Step 1 (Green):** Write the minimum code necessary to pass the test.
+    - **Step 2 (Refactor):** Optimize stricture, eliminate duplication, and improve readability without changing behavior.
+4.  **Black-Box Testing (Encapsulation)**:
+    - DO NOT access or assert against private properties or methods in tests.
+    - Tests must verify behavior strictly through the public API/Interface.
+5.  **Implementation Volume Control:**
+    - **BEFORE** generating code, estimate the required lines of implementation code (excluding test code volume).
+    - If the implementation change requires **>300 lines** (and is NOT a simple repetitive task), **STOP** and **ASK** me to confirm.
+
+Before presenting code, verify:
+
+- [ ] All tests pass
+- [ ] No explanatory comments exist (except minimal docstrings if needed)
+- [ ] No try-catch blocks for logging only
+- [ ] All names are self-explanatory
+- [ ] Code follows TDD Green-Refactor cycle
+- [ ] User was consulted if >300 lines (non-repetitive)
+- [ ] No premature optimization
+- [ ] Code is as simple as possible, but no simpler

quickthumb-0.1.0/.claude/agents/tdd-test-writer.md

@@ -0,0 +1,50 @@
+---
+name: tdd-test-writer
+description: "Use this agent when you need to translate business requirements into structured, failing test cases to rigorously initiate the 'Red' phase of Test-Driven Development."
+model: sonnet
+color: red
+---
+
+## Role
+
+You are an expert Software QA Engineer and TDD (Test-Driven Development) Specialist. Your goal is to convert business requirements into high-quality, failing test cases (The "Red" phase of TDD).
+
+## Instructions
+
+1.  **Analyze Requirements:** deeply understand the provided requirements to identify happy paths, edge cases, and potential error states.
+2.  **Define Test Scope:** Create "Meaningful Tests" only. Avoid redundant or trivial tests.
+3.  **Draft Test Cases:** Write the test code following the constraints below.
+
+## Filtering Criteria
+
+### 1. ❌ IGNORE / DO NOT TEST
+* **Language Syntax:** Do not test if the programming language works (e.g., method chaining returning `self`, simple type instantiation).
+* **Third-Party Libraries:** Do not test if standard libraries (JSON, HTTP clients, ORMs) work. Assume they work.
+* **Trivial Data Access:** Do not test simple Getters/Setters unless they contain transformation logic.
+* **Redundant Checks:** If a "Happy Path" test already verifies a result, do not create a separate test just to check a sub-property of that same result.
+* **Parameter Variations:** Do not create multiple tests for different parameter values when one test suffices to verify the feature works.
+* **Feature Combinations:** Do not test combinations of already-tested features unless there's specific integration logic.
+* **Implementation Detail:** Do not test internal optimizations, private methods, or internal state
+
+### 2. ✅ MUST TEST
+* **Business Invariants:** Rules that must always be true (e.g., "Balance cannot be negative", "Username must be unique").
+* **State Transitions:** Verifying allowed and disallowed status changes (e.g., "Cannot refund a cancelled order").
+* **Boundary Analysis:** Edge cases at the limits of logic (e.g., 0, Max Int, Empty Lists, Leap Years).
+* **Error Handling:** Custom exceptions and fallback logic defined by the business requirements.
+* **Distinct Feature Parameters:** If a parameter changes the behavior significantly, test one variation to prove the parameter works.
+
+## Constraints & Standards
+
+1.  **TDD Red Phase Only:**
+    - All tests MUST fail initially.
+    - **DO NOT** implement the business logic or functional code.
+    - Inside the test function, simply call a failure method.
+2.  **Structure (Given-When-Then):**
+    - You must explicitly comment the sections within each test function:
+      - `Given`: Setup initial state/mocks.
+      - `When`: Execute the action.
+      - `Then`: Assert the expected result.
+3.  **Documentation:**
+    - Every test function must have a clear **Docstring** summarizing the test scenario and expected outcome.
+4.  **Naming Convention:**
+    - Use descriptive names reflecting the behavior (e.g., `test_should_return_error_when_input_is_negative`).

quickthumb-0.1.0/.claude/settings.json

@@ -0,0 +1,34 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "jq -r '.tool_input.file_path | select(endswith(\".py\"))' | xargs -r uv tool run ruff format >&2 || { [ $? -eq 1 ] && exit 2; }"
+          },
+          {
+            "type": "command",
+            "command": "jq -r '.tool_input.file_path | select(endswith(\".py\"))' | xargs -r uv tool run ruff check --fix >&2 || { [ $? -eq 1 ] && exit 2; }"
+          },
+          {
+            "type": "command",
+            "command": "jq -r '.tool_input.file_path | select(endswith(\".py\"))' | xargs -r uv tool run ty check >&2 || { [ $? -eq 1 ] && exit 2; }"
+          }
+        ]
+      }
+    ],
+    "Notification": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "terminal-notifier -title 'Claude Code' -message 'Waiting for your input' -sound Glass"
+          }
+        ]
+      }
+    ]
+  }
+}

quickthumb-0.1.0/.github/workflows/publish.yaml

@@ -0,0 +1,74 @@
+name: Automated Release Process
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      id-token: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          python-version: "3.10"
+
+      - name: Test
+        run: |
+          uv run pytest tests/ --ignore=tests/test_rendering.py
+
+      - name: Determine Version Change
+        id: version_check
+        run: |
+          VERSION="v$(uv version --short)"
+          echo "Current version: $VERSION"
+
+          LATEST_RELEASE=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            https://api.github.com/repos/${{ github.repository }}/releases/latest | jq -r '.tag_name')
+          echo "Latest release version: $LATEST_RELEASE"
+
+          if [ "$VERSION" != "$LATEST_RELEASE" ]; then
+            echo "version_changed=true" >> $GITHUB_OUTPUT
+            echo "new_version=$VERSION"  >> $GITHUB_OUTPUT
+          else
+            echo "version_changed=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Create Release
+        if: steps.version_check.outputs.version_changed == 'true'
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ steps.version_check.outputs.new_version }}
+          generate_release_notes: True
+
+      - name: mint API token
+        id: mint-token
+        run: |
+          # retrieve the ambient OIDC token
+          resp=$(curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" \
+            "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=pypi")
+          oidc_token=$(jq -r '.value' <<< "${resp}")
+
+          # exchange the OIDC token for an API token
+          resp=$(curl -X POST https://pypi.org/_/oidc/mint-token -d "{\"token\": \"${oidc_token}\"}")
+          api_token=$(jq -r '.token' <<< "${resp}")
+
+          # mask the newly minted API token, so that we don't accidentally leak it
+          echo "::add-mask::${api_token}"
+
+          # see the next step in the workflow for an example of using this step output
+          echo "api-token=${api_token}" >> "${GITHUB_OUTPUT}"
+
+      - name: Build and publish to PyPI
+        if: steps.version_check.outputs.version_changed == 'true'
+        run: |
+          uv build
+          uv publish --token ${{ steps.mint-token.outputs.api-token }}

quickthumb-0.1.0/.gitignore

@@ -0,0 +1,162 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

quickthumb-0.1.0/.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+  "recommendations": ["charliermarsh.ruff", "charliermarsh.ty"]
+}

quickthumb-0.1.0/.vscode/settings.json

@@ -0,0 +1,13 @@
+{
+  "[python]": {
+    "editor.codeActionsOnSave": {
+      "source.fixAll": "explicit",
+      "source.organizeImports": "explicit"
+    },
+    "editor.defaultFormatter": "charliermarsh.ruff"
+  },
+  "ty.importStrategy": "fromEnvironment",
+  "ruff.importStrategy": "fromEnvironment",
+  "python.testing.unittestEnabled": false,
+  "python.testing.pytestEnabled": true
+}

quickthumb-0.1.0/CLAUDE.md

@@ -0,0 +1,107 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+QuickThumb is a Python library for programmatic thumbnail generation. See [README.md](README.md) for features and examples, [DESIGN.md](DESIGN.md) for API specifications and design principles.
+
+## Project Structure
+
+```
+.
+├── CLAUDE.md
+├── DESIGN.md
+├── LICENSE
+├── README.md
+├── examples
+│   ├── README.md
+│   └── youtube_thumbnail.py
+├── pyproject.toml
+├── quickthumb
+│   ├── __init__.py
+│   ├── canvas.py
+│   ├── errors.py
+│   └── models.py
+├── tests
+│   ├── __init__.py
+│   ├── test_background_layers.py
+│   ├── test_canvas.py
+│   └── test_text_layers.py
+└── uv.lock
+```
+
+## Development Commands
+
+### Setup
+
+```bash
+# Install dependencies
+uv sync
+```
+
+### Testing
+
+```bash
+# Run all tests
+uv run pytest tests/ -v
+
+# Run single test file
+uv run pytest tests/test_canvas_creation.py -v
+
+# Run specific test
+uv run pytest tests/test_canvas_creation.py::TestCanvasCreation::test_should_create_canvas_with_explicit_dimensions -v
+
+# Run with coverage report
+uv run pytest tests/ --cov=quickthumb --cov-report=html
+```
+
+### Code Quality
+
+```bash
+# Type checking
+uv run ty check quickthumb/
+
+# Linting
+uv run ruff check quickthumb/
+
+# Auto-fix linting issues
+uv run ruff check --fix quickthumb/
+
+# Format code
+uv run ruff format quickthumb/
+```
+
+## Architecture
+
+### Module Organization
+
+- **`models.py`**: Pydantic models for validation and serialization
+  - `LinearGradient`: Gradient configuration with type, angle, stops
+  - `BackgroundLayer`: Background layer with color/gradient/image
+  - `TextLayer`: Text layer with content, styling, positioning
+  - `CanvasModel`: Canvas serialization model (width, height, layers)
+- **`canvas.py`**: Canvas class with method chaining API
+- **`errors.py`**: Custom exceptions (`ValidationError`, `QuickthumbError`)
+
+### Layer Stack Model
+
+Layers are appended to `Canvas._layers` in call order and rendered sequentially:
+
+1. Background layers (stackable with blend modes)
+2. Text layers
+3. Decoration layers
+
+### Dual API
+
+Both Python method chaining and JSON configuration map to the same internal `Canvas._layers` structure.
+
+## Testing Philosophy
+
+Follows **strict TDD** as defined in `.claude/agents/tdd-implementer.md`:
+
+- Self-explanatory code (no "what"/"how" comments)
+- Black-box testing (public API only)
+- Green → Refactor cycle
+
+Test naming: `test_should_{expected_behavior}_{optional_context}`