| 1 |
initialize_command: ./setup.py build |
| 2 |
initialize_command: ./setup.py gui |
| 3 |
copy_resource: .build-cache |
| 4 |
copy_resource: .cache |
| 5 |
copy_resource: .ruff_cache |
| 6 |
copy_resource: .venv |
| 7 |
copy_resource: translations |
| 8 |
copy_resource: resources |
| 9 |
copy_resource: ~/.local/share/calibre-dbin |
| 10 |
copy_resource: ~/.local/lib/python3.14/site-packages/apify_fingerprint_datapoints |
| 11 |
env PODOFO_PREFIX /opt/podofo-1 |
| 12 |
prepend_to_path: develop |
| 13 |
pre_commit: ./setup.py fmt |
| 14 |
|
| 15 |
# System Instructions & Project Context |
| 16 |
|
| 17 |
## Project Architecture & Stack |
| 18 |
This is a multi-language repository. Adhere strictly to the idiomatic styling, patterns, and type safety of each respective language ecosystem present in the codebase. Do not mix patterns across language boundaries. |
| 19 |
|
| 20 |
## Rules for Code Generation |
| 21 |
- **Type Safety**: Enforce strict typing. Never use `any` or loose types. |
| 22 |
- **Error Handling**: Implement explicit error handling. Avoid silent failures or empty catch blocks. |
| 23 |
- **Dependency Minimization**: Use existing project utilities and native standard libraries before suggesting new external packages. |
| 24 |
- **Local Context**: Search the codebase for existing patterns before writing boilerplate structure from scratch. |
| 25 |
|
| 26 |
## Project Execution Workflows |
| 27 |
You must always use the following custom scripts to build, verify, and test changes. Do not use generic toolchains such as `pytest`. |
| 28 |
|
| 29 |
### 🛠️ Build Commands |
| 30 |
Execute this command to compile all modules and check for syntax or type errors: |
| 31 |
```bash |
| 32 |
./setup.py build |
| 33 |
``` |
| 34 |
|
| 35 |
### 🧪 Test Commands |
| 36 |
Execute this command to run the test suite across all language domains: |
| 37 |
```bash |
| 38 |
./setup.py test |
| 39 |
``` |
| 40 |
|
| 41 |
To isolate testing to a specific test use, use the test name without the leading |
| 42 |
"test" prefix. For example, to run a python test named test_my_function, use |
| 43 |
```bash |
| 44 |
./setup.py test my_function |
| 45 |
``` |
| 46 |
|
| 47 |
To test changes to recipes for news download, you can run them as: |
| 48 |
|
| 49 |
```bash |
| 50 |
ebook-convert recipes/filename.recipe output.epub --test |
| 51 |
``` |
| 52 |
|
| 53 |
## Verification Pipeline |
| 54 |
Before declaring a task complete, you must follow this exact verification lifecycle: |
| 55 |
1. Run the local **Build Command** to guarantee zero compilation or compilation-stage type errors. |
| 56 |
2. Run the local **Test Command** |
| 57 |
3. If errors occur, analyze the output logs completely before writing a fix. Do not guess. |
| 58 |
4. Run `/setup.py check --fix --no-editor && ./setup.py type_check` to ensure all files pass quality checks |