30 lines
988 B
Markdown
30 lines
988 B
Markdown
|
# OpenCode Global Instructions
|
||
|
|
|
||
|
|
## Path handling rules
|
||
|
|
|
||
|
|
- Always use relative paths.
|
||
|
|
- Never generate absolute paths (e.g. /Users/..., /home/..., C:\...).
|
||
|
|
- Never assume a specific username, OS, or local filesystem layout.
|
||
|
|
- All paths must be relative to the project root unless explicitly specified.
|
||
|
|
- Do not guess the current working directory.
|
||
|
|
- If the working directory is ambiguous, ask for clarification instead of inventing one.
|
||
|
|
|
||
|
|
## Workspace assumptions
|
||
|
|
|
||
|
|
- Assume the workspace root is the repository root.
|
||
|
|
- Do not hardcode environment-specific values.
|
||
|
|
- Do not infer the machine, OS, or home directory.
|
||
|
|
|
||
|
|
## File generation rules
|
||
|
|
|
||
|
|
- Generate only the requested file.
|
||
|
|
- Do not modify unrelated files.
|
||
|
|
- Do not add additional configuration unless explicitly requested.
|
||
|
|
- Output valid JSON with no comments when JSON is requested.
|
||
|
|
|
||
|
|
## Determinism
|
||
|
|
|
||
|
|
- Avoid creative alternatives.
|
||
|
|
- Do not propose multiple solutions unless asked.
|
||
|
|
- Produce a single, minimal, correct implementation.
|