Amr Gharbeia
6a6f4479ac
- NEW: org-skill-utils-lisp (consolidated from org-skill-lisp-utils) * 3-phase validation: structural, syntactic, semantic * Sandboxed eval, AST extraction/injection/wrapping * Format, list-definitions utilities - NEW: org-skill-utils-org (consolidated from org-skill-emacs-edit) * Read/update/delete org headlines * Property management, TODO state handling * ID-link and internal link support - DELETE: org-skill-lisp-utils (merged into utils-lisp) - DELETE: org-skill-emacs-edit (merged into utils-org) - RENAME: run-all-tests.lisp -> run-tests.lisp - HARDEN: Skill loader with improved lisp keyword handling - FIX: Package jailing issues with def-cognitive-tool macro conflicts - ADD: Setup wizard (opencortex setup) and doctor (opencortex doctor) - ADD: TUI client with Croatoan for native terminal rendering - REMOVE: Dynamic loading from opencortex.asd (use :force t instead) - CLEANUP: Test file consolidation (removed duplicate test suites) Co-authored-by: Agent <agent@memex>
1.7 KiB
1.7 KiB
OpenCortex Agent Mandates
This file defines mandatory workflows and technical standards for the Gemini CLI agent operating within the OpenCortex environment. These mandates supersede general defaults.
Lisp Integrity Mandates
- Validation: Before applying any change to a
.lispfile or a Lisp block in an.orgfile, you MUST useutils-lisp-validateto ensure structural and semantic integrity. - Formatting: All generated Lisp code MUST be piped through
utils-lisp-formatto maintain project-standard indentation before being saved. - Structural Editing: When modifying complex Lisp forms (nested macros or large functions), prefer using
utils-lisp-structural-extractandutils-lisp-structural-wrapto avoid manual parenthesis errors. - Verification: For new or non-trivial logic, use
utils-lisp-evalto test the behavior of the isolated S-expression in a live REPL environment before tangling.
Literate Org Mandates
- AST Integrity: When modifying Org files, utilize
utils-org-set-property,utils-org-set-todo, andutils-org-add-headlineto manipulate the document structure programmatically whenever possible. - ID Management: Every new headline intended for tracking or tangling MUST have a unique ID generated via
utils-org-generate-id.
Engineering Workflow
- Commit-Before-Modify: Verify the git state is clean before starting a multi-file refactor.
- Tangle Sync: After modifying any
.orgfile, you MUST ensure the corresponding.lispartifacts are tangled and in sync. - Validation: Run the project-specific test suite (
sbcl --load opencortex.asd) after every significant change to verify system stability.