{"owner":"huangsam","repo":"ultimate-python","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Quick orientation for AI coding agents\n\n## Key facts an agent must know (short):\n\n- The runner: `runner.py` dynamically imports every module under `ultimatepython` and runs any callable named `main` with zero parameters. Keep `main()` functions parameterless, idempotent, and side-effect safe for CI.\n- Single-file runs are supported: modules are runnable with `python ultimatepython/<category>/<module>.py`. Most modules already include `if __name__ == \"__main__\": main()`.\n- Examples use plain Python stdlib only. Avoid adding new third-party dependencies without updating `requirements.txt` and `pyproject.toml`.\n- Assertions are used as the primary verification mechanism inside examples (not pytest tests). Preserve their intent and messages when editing.\n\n## Patterns and conventions\n\n- `main()` must be parameterless and not raise exceptions when run. Examples: `ultimatepython/fundamentals/function.py`, `ultimatepython/oop/basic_class.py`.\n- Module structure: docstring, helpers, `main()` demonstrating usage via asserts, `if __name__ == \"__main__\": main()`.\n- Avoid long-running or destructive operations. For filesystem interactions, keep them local to ephemeral files and clean up after running.\n- Use `ruff` and `isort` (configured in `pyproject.toml`) for consistency with existing modules.\n\n## Before committing\n\n- New modules go under the appropriate folder—the runner discovers them automatically.\n- If a change requires a new dependency, update `requirements.txt` and `pyproject.toml`.\n- When updating `README.md`, consider updating translations or note why they were skipped.\n\n## Quick reference\n\n- Run all examples: `python runner.py`\n- Run single example: `python ultimatepython/<category>/<module>.py`\n- Coverage target: 80% (in `pyproject.toml`)\n\n## Integration points & CI notes\n\n- CI expects that running `runner.py` and executing each `main()` will succeed. Avoid adding code that requires network access, long sleeps, or interactive input.\n- Do not introduce external services or config files; this repo intentionally uses only the Python standard library.\n\n## Key files\n\n- `runner.py` — discovery and execution (pkgutil.walk_packages + `main` lookups)\n- `pyproject.toml` — formatting, linting, coverage rules\n\n## Category Charter\n\nHelpful guidance on where to place new Python module lessons:\n\n- `fundamentals/`: Core syntax and structural constructs of the language (variables, expressions, strings, lists, loops, functions, basic comprehensions).\n- `oop/`: Object-Oriented Programming concepts (classes, inheritance, encapsulation, abstract base classes, exception handling, custom iterators, mixins, MRO).\n- `stdlib/`: Python standard library modules (file handling, regular expressions, json/csv formats, date/time manipulation).\n- `advanced/`: Metaprogramming and advanced runtime behaviors (decorators, context managers, metaclasses, weak references, walrus operator, pattern matching).\n- `concurrency/`: Multitasking and non-blocking models (threading, async/await, multiprocessing, subinterpreters).\n- `engineering/`: Code quality, benchmarking, algorithm utilities, and data structures (mocking, benchmarking, deque, namedtuple, defaultdict, itertools, heaps).\n\n"},"files":{"AGENTS.md":"# Quick orientation for AI coding agents\n\n## Key facts an agent must know (short):\n\n- The runner: `runner.py` dynamically imports every module under `ultimatepython` and runs any callable named `main` with zero parameters. Keep `main()` functions parameterless, idempotent, and side-effect safe for CI.\n- Single-file runs are supported: modules are runnable with `python ultimatepython/<category>/<module>.py`. Most modules already include `if __name__ == \"__main__\": main()`.\n- Examples use plain Python stdlib only. Avoid adding new third-party dependencies without updating `requirements.txt` and `pyproject.toml`.\n- Assertions are used as the primary verification mechanism inside examples (not pytest tests). Preserve their intent and messages when editing.\n\n## Patterns and conventions\n\n- `main()` must be parameterless and not raise exceptions when run. Examples: `ultimatepython/fundamentals/function.py`, `ultimatepython/oop/basic_class.py`.\n- Module structure: docstring, helpers, `main()` demonstrating usage via asserts, `if __name__ == \"__main__\": main()`.\n- Avoid long-running or destructive operations. For filesystem interactions, keep them local to ephemeral files and clean up after running.\n- Use `ruff` and `isort` (configured in `pyproject.toml`) for consistency with existing modules.\n\n## Before committing\n\n- New modules go under the appropriate folder—the runner discovers them automatically.\n- If a change requires a new dependency, update `requirements.txt` and `pyproject.toml`.\n- When updating `README.md`, consider updating translations or note why they were skipped.\n\n## Quick reference\n\n- Run all examples: `python runner.py`\n- Run single example: `python ultimatepython/<category>/<module>.py`\n- Coverage target: 80% (in `pyproject.toml`)\n\n## Integration points & CI notes\n\n- CI expects that running `runner.py` and executing each `main()` will succeed. Avoid adding code that requires network access, long sleeps, or interactive input.\n- Do not introduce external services or config files; this repo intentionally uses only the Python standard library.\n\n## Key files\n\n- `runner.py` — discovery and execution (pkgutil.walk_packages + `main` lookups)\n- `pyproject.toml` — formatting, linting, coverage rules\n\n## Category Charter\n\nHelpful guidance on where to place new Python module lessons:\n\n- `fundamentals/`: Core syntax and structural constructs of the language (variables, expressions, strings, lists, loops, functions, basic comprehensions).\n- `oop/`: Object-Oriented Programming concepts (classes, inheritance, encapsulation, abstract base classes, exception handling, custom iterators, mixins, MRO).\n- `stdlib/`: Python standard library modules (file handling, regular expressions, json/csv formats, date/time manipulation).\n- `advanced/`: Metaprogramming and advanced runtime behaviors (decorators, context managers, metaclasses, weak references, walrus operator, pattern matching).\n- `concurrency/`: Multitasking and non-blocking models (threading, async/await, multiprocessing, subinterpreters).\n- `engineering/`: Code quality, benchmarking, algorithm utilities, and data structures (mocking, benchmarking, deque, namedtuple, defaultdict, itertools, heaps).\n\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Quick orientation for AI coding agents\n\n## Key facts an agent must know (short):\n\n- The runner: `runner.py` dynamically imports every module under `ultimatepython` and runs any callable named `main` with zero parameters. Keep `main()` functions parameterless, idempotent, and side-effect safe for CI.\n- Single-file runs are supported: modules are runnable with `python ultimatepython/<category>/<module>.py`. Most modules already include `if __name__ == \"__main__\": main()`.\n- Examples use plain Python stdlib only. Avoid adding new third-party dependencies without updating `requirements.txt` and `pyproject.toml`.\n- Assertions are used as the primary verification mechanism inside examples (not pytest tests). Preserve their intent and messages when editing.\n\n## Patterns and conventions\n\n- `main()` must be parameterless and not raise exceptions when run. Examples: `ultimatepython/fundamentals/function.py`, `ultimatepython/oop/basic_class.py`.\n- Module structure: docstring, helpers, `main()` demonstrating usage via asserts, `if __name__ == \"__main__\": main()`.\n- Avoid long-running or destructive operations. For filesystem interactions, keep them local to ephemeral files and clean up after running.\n- Use `ruff` and `isort` (configured in `pyproject.toml`) for consistency with existing modules.\n\n## Before committing\n\n- New modules go under the appropriate folder—the runner discovers them automatically.\n- If a change requires a new dependency, update `requirements.txt` and `pyproject.toml`.\n- When updating `README.md`, consider updating translations or note why they were skipped.\n\n## Quick reference\n\n- Run all examples: `python runner.py`\n- Run single example: `python ultimatepython/<category>/<module>.py`\n- Coverage target: 80% (in `pyproject.toml`)\n\n## Integration points & CI notes\n\n- CI expects that running `runner.py` and executing each `main()` will succeed. Avoid adding code that requires network access, long sleeps, or interactive input.\n- Do not introduce external services or config files; this repo intentionally uses only the Python standard library.\n\n## Key files\n\n- `runner.py` — discovery and execution (pkgutil.walk_packages + `main` lookups)\n- `pyproject.toml` — formatting, linting, coverage rules\n\n## Category Charter\n\nHelpful guidance on where to place new Python module lessons:\n\n- `fundamentals/`: Core syntax and structural constructs of the language (variables, expressions, strings, lists, loops, functions, basic comprehensions).\n- `oop/`: Object-Oriented Programming concepts (classes, inheritance, encapsulation, abstract base classes, exception handling, custom iterators, mixins, MRO).\n- `stdlib/`: Python standard library modules (file handling, regular expressions, json/csv formats, date/time manipulation).\n- `advanced/`: Metaprogramming and advanced runtime behaviors (decorators, context managers, metaclasses, weak references, walrus operator, pattern matching).\n- `concurrency/`: Multitasking and non-blocking models (threading, async/await, multiprocessing, subinterpreters).\n- `engineering/`: Code quality, benchmarking, algorithm utilities, and data structures (mocking, benchmarking, deque, namedtuple, defaultdict, itertools, heaps).\n\n","category":"root","tokens":801}]}