my-coder v0.2: feed a style anchor so generated code meets house standards

[lorenzoliuzzo]

Second iteration of the self-improvement loop — raising the standards bar, as requested.

The gap this closes

The my-raytracer#10 review had to hand-fix the generated tests: they lacked -> None and from __future__ import annotations, diverging from the repo's own test_smoke.py. Root cause: my-raytracer has no CLAUDE.md, so the session had no stated conventions and guessed. Polishing in review doesn't scale — the tool should meet the standard the first time.

Change

• _style_anchor() — inject the target repo's existing code into the session prompt: the file tree + the largest src//tests/ .py files (capped at 3 files × 6 KB). A repo's house style lives in its code even without a CLAUDE.md.
• Stronger standards rule in the prompt: match the shown code's module layout, import style, type hints on every signature (tests included), naming, and test style — imitate the nearest file rather than inventing a style.

Why this is the right depth

It generalizes: every target repo benefits, CLAUDE.md or not. And it doubles as correctness grounding — for my-raytracer#3 (camera), the session now sees the merged vec.py/ray.py, so it uses Vec3/Ray correctly, not just stylistically.

Tests

25 tests, 96% coverage. New test asserts the session prompt carries the existing code as a style anchor. .format() substitution is safe against braces in injected code (values aren't re-parsed).

Readiness

• tests green locally (pytest, ruff, ruff format)
• scope matches the goal (better standards, at the source)

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 86.66667% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/mycoder/coder.py	86.66%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!