agentleFS
zfoggzfogg/ascii-chat/.agents/skills/ascii-chat-python-development/SKILL.md

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.

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
  1. Very specific:

    Use the repository's uv projects and test harnesses.

    line 10
  2. Very specific:

    Use the latest repository-pinned Python minor version through uv.

    line 16
  3. Very specific:

    Run test-suite Python from the test project: uv run --project tests/ascii_chat_tests --frozen python ....

    line 18
  4. Very specific:

    Keep dependency declarations in tests/ascii_chat_tests/pyproject.toml and its lockfile synchronized.

    line 22
  5. Distinctive:

    Prefer the narrowest relevant pytest command, then the corresponding CTest label or test when the change crosses the CMake integration …

    line 31
  6. Very specific:

    Keep terminal/network/media tests deterministic and use their existing fixtures and command-line options rather than adding ad-hoc sleeps.

    line 35
  7. Very specific:

    Follow the repository's Python formatting and lint configuration.

    line 42
  8. Very specific:

    Run Ruff and ty for the affected Python projects and resolve their errors before committing.

    line 44
  9. Very specific:

    Keep reusable test fixtures in tests/ascii_chat_tests.

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 with pip.
  • 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.toml and its lockfile synchronized. Update the lockfile with uv lock.
  • CMake must receive the interpreter from the uv environment when configuring Python-backed tests (for example, -DPython3_EXECUTABLE=.../.venv/bin/python). CTest launches the generated Python tests through uv; do not bypass that environment with a system python.

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 run for pytest, ruff, and ty.
  • 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 existing scripts/, cmake/, or .github/scripts/ locations.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.