azaion/gps-denied-onboard
1
0
Fork 0
mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-04-23 01:46:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revise coding standards and testing guidelines in .cursor/rules/coderule.mdc and .cursor/rules/testing.mdc. Update descriptions for clarity, adjust coverage thresholds to 75%, and enhance comments on test data requirements. Improve sound notification rules in .cursor/rules/human-attention-sound.mdc and refine tracker operations in .cursor/rules/tracker.mdc to ensure better user interaction and error handling. Incorporate completeness audit steps in research documentation for improved quality assurance.

Browse Source
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-04-17 20:29:12 +03:00
parent fa17185f82
commit 229188acbf
17 changed files with 275 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/skills/research/references/comparison-frameworks.md
+14
View File
@@ -32,3 +32,17 @@
6. Applicable scenarios
7. Team capability requirements
8. Migration difficulty
## Decomposition Completeness Probes (Completeness Audit Reference)
Used during Step 1's Decomposition Completeness Audit. After generating sub-questions, ask each probe against the current decomposition. If a probe reveals an uncovered area, add a sub-question for it.
| Probe | What it catches |
|-------|-----------------|
| **What does this cost — in money, time, resources, or trade-offs?** | Budget, pricing, licensing, tax, opportunity cost, maintenance burden |
| **What are the hard constraints — physical, legal, regulatory, environmental?** | Regulations, certifications, spectrum/frequency rules, export controls, physics limits, IP restrictions |
| **What are the dependencies and assumptions that could break?** | Supply chain, vendor lock-in, API stability, single points of failure, standards evolution |
| **What does the operating environment actually look like?** | Terrain, weather, connectivity, infrastructure, power, latency, user skill level |
| **What failure modes exist and what happens when they trigger?** | Degraded operation, fallback, safety margins, blast radius, recovery time |
| **What do practitioners who solved similar problems say matters most?** | Field-tested priorities that don't appear in specs or papers |
| **What changes over time — and what looks stable now but isn't?** | Technology roadmaps, regulatory shifts, deprecation risk, scaling effects |