You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**60 LOC exemptions**: Do not add CRITICAL markers to machine-generated or schema-constrained files where comments would break parsing. Common examples:
193
+
-`**/package-lock.json`, `**/bun.lock`
194
+
-`**/*.pbxproj`
195
+
-`LICENSE`
196
+
-**Shebang files**: For executable scripts that require a shebang on line 1 (e.g. `#!/usr/bin/env bun`, `#!/bin/bash`), keep the shebang as the first line and put the CRITICAL marker on line 2.
187
197
-**20 files per directory**: Create subdirectories when exceeded
188
198
-**kebab-case naming**: ALL files/directories use kebab-case
189
199
-**No camelCase/PascalCase in filenames**: `my-component.tsx` NOT `MyComponent.tsx`
@@ -195,7 +205,7 @@ bun test # Run test suite
195
205
-[ ] All Swift files compile without errors
196
206
-[ ] Xcode project regenerated with `./setup.sh`
197
207
-[ ] Test build succeeds: `xcodebuild ... clean build`
198
-
-[ ] No files exceed 60 LOC without `// CRITICAL` marker
208
+
-[ ] No source/docs files exceed 60 LOC without a CRITICAL marker (see conventions above)
0 commit comments