Files
ai-training/.cursor/rules/cursor-meta.mdc
T
Oleksandr Bezdieniezhnykh 243b69656b Update test results directory structure and enhance Docker configurations
- Modified `.gitignore` to reflect the new path for test results.
- Updated `docker-compose.test.yml` to mount the correct test results directory.
- Adjusted `Dockerfile.test` to set the `PYTHONPATH` and ensure test results are saved in the updated location.
- Added `boto3` and `netron` to `requirements-test.txt` to support new functionalities.
- Updated `pytest.ini` to include the new `pythonpath` for test discovery.

These changes streamline the testing process and ensure compatibility with the updated directory structure.
2026-03-28 00:13:08 +02:00

28 lines
1.2 KiB
Plaintext

---
description: "Enforces naming, frontmatter, and organization standards for all .cursor/ configuration files"
globs: [".cursor/**"]
---
# .cursor/ Configuration Standards
## Rule Files (.cursor/rules/)
- Kebab-case filenames, `.mdc` extension
- Must have YAML frontmatter with `description` + either `alwaysApply` or `globs`
- Keep under 500 lines; split large rules into multiple focused files
## Skill Files (.cursor/skills/*/SKILL.md)
- Must have `name` and `description` in frontmatter
- Body under 500 lines; use `references/` directory for overflow content
- Templates live under their skill's `templates/` directory
## Agent Files (.cursor/agents/)
- Must have `name` and `description` in frontmatter
## User Interaction
- Use the AskQuestion tool for structured choices (A/B/C/D) when available — it provides an interactive UI. Fall back to plain-text questions if the tool is unavailable.
## Execution Safety
- Never run test suites, builds, Docker commands, or other long-running/resource-heavy/security-risky operations without asking the user first - unlsess it is explicilty stated in skill or agent, or user already asked to do so.
## Security
- All `.cursor/` files must be scanned for hidden Unicode before committing (see cursor-security.mdc)