ascii-chat-python-development
Skill203 starsChanged 8 days agoMITView on GitHub
Develop and test ascii-chat's Python tooling, test harnesses, native ctypes probes, and build-time Python helpers.
In this repository11 other files it gives its agents.
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ascii-chat-c-developmentSkill
- ascii-chat-cli-releaseSkill
- ascii-chat-cross-platform-development-and-or-testingSkill
- ascii-chat-documentationSkill
- ascii-chat-mcp-devSkill
- ascii-chat-testingSkill
- ascii-chat-wasm-developmentSkill
- ascii-chat-web-deploySkill
- sentry-commit-messagesSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use the repository's uv projects and test harnesses.
- Very specific: line 16
Use the latest repository-pinned Python minor version through uv.
- Very specific: line 18
Run test-suite Python from the test project: uv run --project tests/ascii_chat_tests --frozen python ....
- Very specific: line 22
Keep dependency declarations in tests/ascii_chat_tests/pyproject.toml and its lockfile synchronized.
- Distinctive: line 31
Prefer the narrowest relevant pytest command, then the corresponding CTest label or test when the change crosses the CMake integration …
- Very specific: line 35
Keep terminal/network/media tests deterministic and use their existing fixtures and command-line options rather than adding ad-hoc sleeps.
- Very specific: line 42
Follow the repository's Python formatting and lint configuration.
- Very specific: line 44
Run Ruff and ty for the affected Python projects and resolve their errors before committing.
- Very specific: line 50
Keep reusable test fixtures in tests/ascii_chat_tests.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ascii-chat Python development
Use the repository's uv projects and test harnesses. Python is used for
pytest/CTest integration tests, native ctypes probes, standalone utilities,
coverage/report generation, CMake helpers, and code-generation/build helpers.
Python runtime and dependencies
- Use the latest repository-pinned Python minor version through
uv; do not create a separate virtualenv or install project packages withpip. - Run test-suite Python from the test project:
uv run --project tests/ascii_chat_tests --frozen python .... - Synchronize it with:
uv sync --project tests/ascii_chat_tests --frozen. - Keep dependency declarations in
tests/ascii_chat_tests/pyproject.tomland its lockfile synchronized. Update the lockfile withuv lock. - CMake must receive the interpreter from the
uvenvironment when configuring Python-backed tests (for example,-DPython3_EXECUTABLE=.../.venv/bin/python). CTest launches the generated Python tests throughuv; do not bypass that environment with a systempython.
Test and probe workflow
- Prefer the narrowest relevant pytest command, then the corresponding CTest label or test when the change crosses the CMake integration boundary.
- Native probes load the built shared library with
ctypes; verify exported signatures, ownership, error paths, and platform library loading. - Keep terminal/network/media tests deterministic and use their existing fixtures and command-line options rather than adding ad-hoc sleeps.
- For C/Python boundary changes, inspect both the Python call site and the exported C API/header, then run the focused probe and test suite.
Style and tooling
- Follow the repository's Python formatting and lint configuration. Use
uv runforpytest,ruff, andty. - Run Ruff and ty for the affected Python projects and resolve their errors before
committing. The defer tool has its own project under
src/tooling/defer. - Consult the ascii-chat testing skill for Python test placement and test commands.
- Python scripts should use structured exceptions and actionable failures; do not hide subprocess failures or silently accept malformed native data.
- Keep reusable test fixtures in
tests/ascii_chat_tests; keep repository utilities and build helpers in their existingscripts/,cmake/, or.github/scripts/locations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

