domain-scheduling-engine-rules

Enforce pure, deterministic scheduling rules for the Hifz Companion engine.

Updated Jun 17, 2026

Search Tags:#code review #scheduling #determinism #Hifz Companion #scheduling engine

Ready to run

npx skills add https://github.com/zakariaf/Hifz-Companion --skill domain-scheduling-engine-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-scheduling-engine-rules
Source: https://github.com/zakariaf/Hifz-Companion/tree/main/.claude/skills/domain-scheduling-engine-rules
Command: npx skills add https://github.com/zakariaf/Hifz-Companion --skill domain-scheduling-engine-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the scheduling engine of the Hifz Companion app remains pure, deterministic, and honest, preventing silent decay of memorized content.

Core Features & Use Cases

Pure Functions: Ensures all functions within the engine/ package are stateless and pure, with no external dependencies.
Deterministic Updates: Guarantees identical inputs result in identical outputs, crucial for reproducibility.
Trust Clamp: Enforces the algorithm can only pull a page forward, never let it drift past the cycle, and never marks a memorized page "done."
Use Case: When updating the scheduling logic or reviewing code that touches scheduling math, track/phase transitions, or engine output, this Skill provides a checklist to ensure adherence to the scheduling engine's principles.

Quick Start

Use the 'domain-scheduling-engine-rules' skill when modifying the engine/ package or any part of the scheduling logic in the Hifz Companion app.

Frequently Asked Questions about domain-scheduling-engine-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain deterministic scheduling logic in a memorization app?▼

Deterministic scheduling logic requires pure functions where identical inputs always yield identical outputs. You must ensure all functions in the scheduling engine are stateless with no external dependencies to maintain reproducibility and prevent silent decay of memorized content.

Why does a scheduling engine need a trust clamp algorithm?▼

A trust clamp algorithm prevents scheduling drift by enforcing strict invariants. It ensures the algorithm can only pull a page forward, never lets it drift past the cycle, and never marks a memorized page as done, maintaining the integrity and honesty of the scheduling process.

How do I update track and phase transitions without breaking scheduling invariants?▼

Updating track and phase transitions safely requires checking specific rules and invariants governing the scheduling engine. You must verify that modifications to the scheduling logic, transitions, and engine output adhere to purity and determinism principles to preserve integrity.

What are the limitations of pure functions in a scheduling engine?▼

Pure functions in a scheduling engine cannot rely on external state or dependencies, limiting their ability to directly mutate application state. They are restricted to deterministic calculations where identical inputs must produce identical outputs, requiring state management to happen externally.

When do I need to review code for scheduling engine determinism?▼

You need to review code for scheduling engine determinism whenever modifying the engine package or any logic touching scheduling math, track/phase transitions, or engine output. This review ensures adherence to required principles and prevents silent decay of memorized content.