What problem does it solve? It prevents recurring project failures caused by hardcoded paths, IPs, and device numbers in code, and by banned contrastive phrasing in technical documents, by enforcing a growing set of hard conventions with mandatory mechanical lint checks after every draft or revision. ## Core Features & Use Cases - Coding Convention Enforcement: Requires relative paths derived from the script's own location and parameterizes variables like IPs, ports, device nodes, and model paths via CLI arguments, environment variables, or config files. - Documentation Phrasing Rules: Bans contrastive sentence patterns (e.g., "not A but B", rhetorical questions) in user-facing technical docs, including revision histories, and mandates running lint-phrasing.sh and lint-format.sh after every draft until no hits remain. - Feishu Document Editing Discipline: Prescribes refetching full documents and rebuilding block IDs each round, whole-table block_replace for table edits, correct rich-text tags (<b>, <code>, <), and block-structure-based verification instead of grep/wc counts. - Use Case: When writing a deployment script or revising a Feishu technical design doc for the project, apply these conventions, run the lint scripts, then do a final AI pass over the full text before delivery. ## Quick Start Apply the changfengpro project conventions to review my script and technical document draft, then run the phrasing and format lint checks.
