Summary
Curious - why does /design setup create brief.md in root directory but all other commands like /design responsive then look for
LIST [.commandcode/design]
└ ERROR: Directory does not exist or is not accessible: .commandcode/design
Expected Behavior
I'd have expected setup to stub out those necessary directories for future design command calls.
And why would brief.md not be stored there?
Actual Behavior
Directory not created on setup.
Steps to reproduce the issue
Do /design setup see where brief is stored, then clear session and to a /design responsive`
And actually when I did:
❯ /design typeset
✻ Thought for 1 second [ctrl+o to expand]
⠶ I'll examine the current typography setup to understand what's in place before making changes.
READ [Skill(design/references/typeset.md)]
READ [.commandcode/design/brief.md]
└ ERROR: File not found or not readable: .commandcode/design/brief.md
It in fact looked for brief there -- so I'll move it.
Command Code Version
0.39.1
Operating System
macOS
Terminal/IDE
ghostty
Shell
zsh
Additional context
No response
Summary
Curious - why does
/design setupcreatebrief.mdin root directory but all other commands like/design responsivethen look forExpected Behavior
I'd have expected
setupto stub out those necessary directories for future design command calls.And why would brief.md not be stored there?
Actual Behavior
Directory not created on setup.
Steps to reproduce the issue
Do
/design setupsee where brief is stored, then clear session and to a /design responsive`And actually when I did:
It in fact looked for brief there -- so I'll move it.
Command Code Version
0.39.1
Operating System
macOS
Terminal/IDE
ghostty
Shell
zsh
Additional context
No response