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
Copy file name to clipboardExpand all lines: CODEX_COMMANDS.md
+29-80Lines changed: 29 additions & 80 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,89 +7,38 @@ MODEL: GPT-5.4-codex
7
7
REASONING: high
8
8
9
9
COMMAND:
10
-
Create BUILD_PR_SPRITE_EDITOR_FROM_SCRATCH.
11
-
12
-
Hard requirements:
13
-
1. Assume there is NO usable sprite editor in the repo.
14
-
2. DO NOT review, assess, refactor, migrate, or depend on any existing sprite editor implementation.
15
-
3. DO NOT delete, rename, overwrite, or clean up any current sprite-editor-related files or folders, even if they appear broken, old, duplicate, or unused.
16
-
4. Build a NEW sprite editor from scratch as an isolated tool under:
17
-
tools/Sprite Editor/
18
-
5. Keep the PR small and surgical, focused only on the new tool and its supporting docs.
19
-
6. Follow repo rules:
20
-
- PLAN_PR -> BUILD_PR -> APPLY_PR
21
-
- docs-first
22
-
- one PR per purpose
23
-
- no destructive changes
24
-
- update docs with the change
25
-
7. All NEW files must include the required file header standard at the top, using the file creation date.
26
-
8. Preserve current repo structure and public/internal boundaries.
27
-
28
-
Deliverables to create:
29
-
- docs/pr/BUILD_PR_SPRITE_EDITOR_FROM_SCRATCH.md
10
+
Create BUILD_PR_SPRITE_EDITOR_USABILITY_POLISH.
11
+
12
+
Goal:
13
+
Implement a small, surgical usability-polish PR for the isolated Sprite Editor now that core features are working.
14
+
15
+
Scope rules:
16
+
1. Do not review, modify, migrate, or delete any pre-existing sprite editor outside tools/Sprite Editor/
17
+
2. Keep scope limited to tools/Sprite Editor/, tools/index.html only if needed, and docs/reports
18
+
3. Do not expand into engine or unrelated tools
19
+
4. Docs-first
20
+
5. One PR per purpose
21
+
6. Preserve required file headers
22
+
7. No destructive changes
23
+
24
+
Polish targets:
25
+
- Better tool-state visibility for active tool / active color / active frame
0 commit comments