sublinkPro: Instructions file for Codex

AGENTS.md

This file provides AI and human contributors with a high-level architectural guide and navigation map for SublinkPro.

---

0. MANDATORY PRE-COMMIT VALIDATION - NON-NEGOTIABLE REQUIREMENT

⚠️ ABSOLUTE REQUIREMENT FOR ALL AI AGENTS ⚠️

This is a HARD STOP requirement. No exceptions. No shortcuts. No "will fix later". No "just this once".

Red Line Rule: NO COMMITS WITHOUT VALIDATION

┌─────────────────────────────────────────────────────────────┐
│  🛑 BLOCKING REQUIREMENT - READ THIS FIRST                  │
├─────────────────────────────────────────────────────────────┤
│                                                              │
│  BEFORE any git commit, git add, or PR creation:            │
│                                                              │
│  1. You MUST invoke: pre-commit-check skill                 │
│  2. You MUST execute ALL applicable validation commands     │
│  3. You MUST fix ALL failures before proceeding             │
│  4. You MUST document what was validated                    │
│                                                              │
│  Violations of this rule constitute incomplete work.        │
│                                                              │
└─────────────────────────────────────────────────────────────┘

Mandatory Trigger Points

You MUST invoke .agents/skills/pre-commit-check/SKILL.md BEFORE:

1. Running git add or git commit - Whether initiated by you or requested by user
2. Creating or updating a PR - Via gh pr create or any PR command
3. Declaring work "complete", "done", or "finished" - In any form
4. User explicitly asks to commit - Even if they say "skip checks" (refuse and explain why)
5. Any code change is ready for commit - Backend, frontend, docs, config, or mixed

The Validation-Before-Commit Workflow

Code Change Complete
    ↓
    ├─> Did you invoke pre-commit-check skill? 
    │   ├─> NO  → STOP. Invoke it now. DO NOT PROCEED.
    │   └─> YES → Continue
    ↓
    ├─> Did ALL validation commands pass?
    │   ├─> NO  → STOP. Fix failures. Re-run validation. DO NOT PROCEED.
    │   └─> YES → Continue
    ↓
    ├─> Did you stage ONLY intended changes?
    │   ├─> NO  → STOP. Review staged files. Remove unintended. DO NOT PROCEED.
    │   └─> YES → Continue
    ↓
    ├─> Did you prepare a proper commit message?
    │   ├─> NO  → STOP. Prepare semantic commit message. DO NOT PROCEED.
    │   └─> YES → Continue
    ↓
Ready to Commit (present to user for final review)