← Browse

@rainerblind/atrainingtracker

B

Project Vision & AI Instructions: aTrainingTracker

rulescursor

Install

agr install @rainerblind/atrainingtracker --target cursor

Writes 1 file into .cursor/rules/, pinned to git-6876dfaa.

  • .cursorrules

Document

Project Vision & AI Instructions: aTrainingTracker

The Goal

The primary objective of this project is to build an awesome, world-class, professional application for tracking training activities. Every contribution must aim for the highest standards of performance, visual design, and user experience.

Quality Standards for AI

As an AI agent working on this project, you must adhere to the following quality pillars:

  1. Requirement-Based Engineering: You are strictly bound by the workflow in docs/project_protocol.md. No code change is allowed without a corresponding requirement in docs/requirements.md. Always prioritize reading these files and the main README.md to understand the current project state.
  2. Code Excellence: Produce clean, idiomatic, and highly readable Kotlin/Java code. Avoid "quick fixes"; prefer robust, well-architected solutions that respect existing patterns.
  3. UI/UX Sophistication: All UI contributions must be "very good looking," modern, and consistent. Follow the established clean, white-themed design language with minimalist, professional accents.
  4. Clarity & Precision: If the user's instructions are ambiguous, incomplete, or unclear, you must ask for clarification before making any assumptions or changes.
  5. Robustness: All hardware communication (ANT+, BLE, GPS) must be treated as potentially unstable. Always implement null-safety, error handling, and lifecycle-aware logic.

Mandatory Workflow

Before performing any task, you must:

  1. Sync Requirements: Read docs/requirements.md and docs/project_protocol.md. Update the requirements list with the current task before writing any code.
  2. Traceability: Every item in your implementation plan must reference a Requirement ID.
  3. Verification: Confirm requirements are met and update their status to "Verified" upon completion.

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicensecopyleft/unknown — index-and-link only

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-6876dfaa630c2026-08-06