القائمة
Use for implementing production-grade Rulesgen features or non-trivial code changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding, renaming, reordering, or linking Rulesgen public docs that flow to the tdm-docs Docusaurus site and tdspora.ai. Covers the import pipeline, sidebar/.order mechanics, the "link locally until published" rule, and the lychee link-check and docs-contract validation battery.
Use for authoring or updating Rulesgen documentation — public docs (`docs/public/`), repo-root design docs, contributor docs, sample READMEs, and the glossary. Produces testable, glossary-aligned, link-integral docs.
Use for testing Rulesgen documentation — executes Markdown code fences via Sybil, validates link integrity, lints glossary usage, and cross-checks docs against Settings, schemas, and routes.
Use for authoring, reviewing, or correcting natural-language → Python generation DSL rules for Rulesgen.
Use for Pydantic v2 validation errors, DSL parser/validator rejections, and API request validation issues in Rulesgen.
Use for FastAPI route, middleware, lifespan, dependency injection, or Problem Details response issues in Rulesgen.
| name | rulesgen-implement-feature |
| description | Use for implementing production-grade Rulesgen features or non-trivial code changes. |
Use the names defined in docs/agent-harness/glossary.md — the single authoritative dictionary for both business and technical vocabulary. If a draft uses an undefined term, add it to the glossary in the same change rather than inventing a synonym.
main, switched branches, or any subsequent uv run … produces ModuleNotFoundError, invoke the rulesgen-bootstrap skill before continuing.rulesgen.library), HTTP API (rulesgen/api/v1/), compiler, execution backend, services, infra (LLM gateway, semantic cache, OSSFS), auth, middleware, schemas, DSL contract.rulesgen-codebase-researcher agent (or targeted grep/Read) to locate the relevant files, schemas, and existing tests.requirements/NL-to-Python-Generation-DSL.md and requirements/NL-to-Python-Generation-Overview.md in full.tests/unit/, plus tests/contract/ or tests/integration/ if applicable), and any backward-compatibility risk (per the glossary definition of [[backward compatibility]]).python-quality.md and project-architecture.md.testing-contract.md:
cd "$(git rev-parse --show-toplevel)"):
uv run --no-sync pytest tests/unit/test_<target>.py -q
uv run --no-sync ruff check <touched paths>
uv run --no-sync ruff format --check <touched paths>
uv run --no-sync mypy src
uv run --no-sync pytest -q # full suite before handoff
--no-sync form is preferred because the harness denies bare uv sync; if --no-sync reports a missing module, run rulesgen-bootstrap.uv lock --check must pass and pyproject.toml + uv.lock must be committed together. Adding/removing a dependency is an escalation (see CLAUDE.md "Escalation triggers" + "Approval contract").semantic-release derives versions from them. Mark breaking changes explicitly with ! and a BREAKING CHANGE: footer.pyproject.toml:project.version, [tool.semantic_release], the release CI job, or secrets.DEPLOY_KEY handling.