Files
PMOCrazycoder/.opencode/instructions.md
Eric Coissac f984f5f062 Update devcontainer and Docker setup with new LLM API configuration
Update devcontainer.json to set terminal shell and add empty features object
Update docker-compose.yml to change port mapping and add environment variable for LOCAL_LLM_API
Add new OpenCode configuration files for LLM settings and instructions
Update Dockerfile to install additional tools and dependencies including Go, Rust, Node.js, and Python packages
Modify docker-entrypoint.sh to handle MCP server initialization and shell configuration
Update LM client readme to reflect new API endpoint configuration
2026-02-21 16:34:27 +01:00

29 lines
1.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# OpenCode Global Instructions Optimized for Minimal Scope
## Path handling
- Always use relative paths. Never generate absolute paths (e.g., /Users/..., /home/..., C:\...).
- All paths must be relative to the project root unless explicitly specified.
- Do not guess the current working directory. Ask for clarification if ambiguous.
- Only operate on files explicitly mentioned in the task. Never traverse directories not specified.
## Workspace assumptions
- Assume the workspace root is the repository root.
- Do not infer environment-specific values (machine, OS, home directory).
- Only read or reference files explicitly provided or mentioned. Ignore all others.
## File generation
- Generate only the requested file. Do not modify unrelated files.
- Do not add extra files or configurations unless explicitly requested.
- Output valid JSON without comments when JSON is requested.
- When accessing a file, assume no knowledge of other files unless explicitly provided.
## Determinism
- Avoid creative alternatives. Produce a single, minimal, correct implementation.
- Do not propose multiple solutions unless explicitly asked.
- Do not speculate about missing files, directories, or dependencies.
## Explicit scope limitation
- Operate strictly on files and paths explicitly mentioned in the prompt.
- Do not recursively explore the directory tree.
- Ask for clarification if necessary information is missing instead of assuming.