Files
Kill_LIFE/.github/instructions/cad.instructions.md
T
Clément SAILLANT 5efb380da5 feat: automate yiacad PR review lane (#18)
* feat: automate yiacad pr review lane

* fix: stabilize yiacad review and spec gates

* fix: scope kicad exports to repo hardware

* fix: ignore kicad block library sources in exports

* feat: Add infra VPS monitoring runbook and healthcheck scripts

- Created INFRA_VPS_RUNBOOK_2026.md detailing operational procedures for monitoring VPS services.
- Added infra_vps_healthcheck.sh script for automated health checks on DNS, TLS, TCP, and HTTP for VPS services.
- Introduced infra_vps_security_audit.sh for non-intrusive security checks on external VPS services.
- Established JSON schema for infra VPS inventory in infra_vps.schema.json.
- Developed integration for runtime status reporting in the Next.js API route.
- Implemented Playwright tests for smoke testing the application and ensuring core functionalities.
- Updated Makefile for development dependencies and testing commands.
- Created various test files for unit and end-to-end testing across different components.

* feat(agentics): update mesh agents, gates, prompts, and workflows
2026-03-29 17:14:16 +02:00

991 B

description, name, applyTo
description name applyTo
Use when working on YiACAD CAD lanes, KiCad/FreeCAD integrations, backend CAD actions, manufacturing exports, or CAD MCP/runtime scripts. CAD Domain
tools/cad/**
tools/hw/**
hardware/**
specs/yiacad*
specs/contracts/yiacad*

CAD Domain Instructions

Product Boundary

  • Treat YiACAD as product shell.
  • Treat KiCad/FreeCAD/KiBot/KiAuto as integrated engines behind backend actions.

Preferred Paths

  • Service-first: tools/cad/yiacad_backend_service.py and tools/cad/yiacad_backend_client.py.
  • Keep outputs normalized through context.json and uiux_output.json.

Verify With

  • python3 tools/cad/yiacad_backend_client.py --json-output status
  • python3 tools/cad/yiacad_native_ops.py status --json-output
  • python3 tools/validate_specs.py --strict

Guardrails

  • Do not bypass backend boundary from UI/plugin/worker flows.
  • Keep engine_status and degraded_reasons coherent across contracts and examples.