This document contains global constraints, build/test command lists, and coding standards for Codex agents.
Important
- Read
CODE_MAP.mdfirst to understand the layout and topological mapping of packages and components. - Do not execute broad semantic searches or grep actions across the whole repository unless targeted.
- Before modifying or inspecting a package or component, read its local
CLAUDE.mdcontext file (e.g.,scripts/CLAUDE.mdorcss/CLAUDE.md).
- Strict Grounding: Always search the
.wiki/directory first for architectural patterns and concepts before writing code. - Wikilinks: Refer to domain entities using Obsidian-style double bracket links, e.g.,
[[overview]]or[[lessons-learned]]. - Drift Prevention: Whenever you modify a core data structure, styling convention, or computational pipeline, you MUST update the corresponding
.wiki/page orCODE_MAP.mdsections immediately to prevent knowledge rot.
- Jekyll Site Compilation:
bundle exec jekyll buildorjekyll build - Jekyll Site Preview:
bundle exec jekyll serve - Scraper Pipeline Execution:
python scripts/fetch_bsgou_members.py - Image URL Asset Checker:
node tools/assert-url.js - Directory Tree Generator:
./tools/dir-tree.sh
- Git Rules: Never commit broken build artifacts or temp files. If pushing to the remote repository, bypass dummy token wrappers using
env -u GITHUB_TOKEN git push origin main. - Python: Use Python 3.x, enforce static type hinting, follow PEP 8 rules, and write docstrings for new methods.
- HTML & Web Layouts: Write semantic HTML5, ensure unique element IDs for test scripts, and maintain accessibility standards.
- Hygiene: Never create temporary, scratch, or test files in the workspace root directory. Use
<appDataDir>/brain/<session_id>/scratch/for all temporary executions.