Use to review a diff in the eNabizMCP repo for two things at once — PHI/secret leakage (real health data, TC kimlik/phone/email, session or .env content, ungitignored raw HTML) and read-only invariant violations (new write endpoints, missing/wrong readOnlyHint, reintroduced table fallback, values coerced off string…
Use when discovering or probing E-Nabız portal endpoints to find new read-only data sources — running scripts/discover.py safely, respecting the write-endpoint denylist, capturing raw HTML without leaking PHI, and understanding that endpoint→tool promotion is manual. Invoke before adding a tool for an endpoint not…
Use after any feature/phase change (adding, removing, or renaming a tool or data area) to keep docs/STATUS.md, README.md tool counts and list, and the commit message consistent. Invoke as the final step of yeni-tool-ekle, or whenever tool/field counts change.
Use when writing or refactoring an HTML→model parser in src/enabizmcp/parsers.py — the standard table skeleton, the exact-id/no-fallback rule, rows()/cell()/text() helpers, string-only values, the independent outofrange safety check, and the trlower slug trap. Invoke this whenever touching parsing logic.
Use when adding a new read-only E-Nabız MCP tool (a new data endpoint surfaced as enabiz ) to this repo — walks endpoint→parser→tool module→server registration→fixture+test→docs, end to end. Covers the read-only invariant, readOnlyHint policy, and the two-file server registration trap.
Instructions for UmutKDev/enabiz-mcp, covering claude.md — enabizmcp, değişmez invaryantlar (bunları asla ihlal etme), komutlar, mimari, bir bakışta and en sık tuzaklar (detay skill'lerde).
Repo-aware code reviewer for the MyAnimeList MCP server. Use to review changed/uncommitted code against this project's specific invariants — token safety, stdout purity, MCP tool hints, the mandatory fields param, packaging/release integrity, and test registration. Invoke after implementing a tool or bug fix, before…
Use when adding a new MCP tool to the MAL server — the lockstep checklist covering the MAL client method, server helpers, tool decorator/hints, UI view, and test registration.
Use when cutting a release of myanimelist-mcp — bumps the single version source, runs tests, commits, and pushes the tag that triggers the PyPI publish workflow.
Use before coding against a MyAnimeList API behavior that isn't already recorded in NOTES.md — check the verified-facts log first, confirm against the live API, then record the observation.