fragginwagon
71e89ca5c0
- Add 12 cross-project instruction files to resources/instructions/ - Add cleanup-copilot-history.mjs/.sh: quarantine-based history cleanup with dry-run and aggressive scope - Add restore-copilot-history.mjs/.sh: restore from quarantine by run, path, or filter - Add purge-copilot-history-quarantine.mjs/.sh: purge old quarantine runs with keep-latest guard - Add copilot-history-maintenance.test.mjs: 3 passing unit tests covering all three scripts
18 lines
1.0 KiB
Markdown
18 lines
1.0 KiB
Markdown
---
|
|
name: "Engineering Core Defaults"
|
|
description: "Cross-project baseline for maintainable, predictable, and secure engineering decisions."
|
|
applyTo: "**"
|
|
---
|
|
|
|
- Prioritize maintainability, readability, and predictability over novelty.
|
|
- Prefer explicit behavior and descriptive names over implicit shortcuts.
|
|
- Reuse existing project patterns and utilities before introducing abstractions.
|
|
- Keep implementations modular and scoped; avoid monolithic files and deep nesting.
|
|
- Remove dead code, unused imports, and duplicate logic when touching related areas.
|
|
- Add comments only for non-obvious intent, trade-offs, or constraints.
|
|
- Favor composition over inheritance and use early returns to simplify control flow.
|
|
- Default to secure practices: validate inputs, isolate secrets, and avoid hardcoded credentials.
|
|
- Keep dependencies minimal and add new ones only with clear justification.
|
|
- Optimize for practical performance without reducing clarity or maintainability.
|
|
- Treat project-local instructions as authoritative when they conflict with global defaults.
|