Files
detections/.cursor/rules/cursor-meta.mdc
T
Oleksandr Bezdieniezhnykh ad5530b9ef Enhance coding guidelines and autopilot workflows
- Updated `.cursor/rules/coderule.mdc` to include new guidelines on maintaining test environments and avoiding hardcoded workarounds.
- Revised state file rules in `.cursor/skills/autopilot/state.md` to ensure comprehensive updates after every meaningful state transition.
- Improved existing-code workflow in `.cursor/skills/autopilot/flows/existing-code.md` to automate task re-entry without user confirmation.
- Added requirements for test coverage in the implementation process within `.cursor/skills/implement/SKILL.md`, ensuring all acceptance criteria are validated by tests.
- Enhanced new-task skill documentation to include test coverage gap analysis, ensuring all new requirements are covered by tests.

These changes aim to strengthen project maintainability, improve testing practices, and streamline workflows.
2026-03-29 05:30:00 +03:00

22 lines
829 B
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
## Security
- All `.cursor/` files must be scanned for hidden Unicode before committing (see cursor-security.mdc)