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
This commit is contained in:
@@ -1,29 +1,28 @@
|
||||
# OpenCode Global Instructions
|
||||
# OpenCode Global Instructions – Optimized for Minimal Scope
|
||||
|
||||
## 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.
|
||||
## 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.
|
||||
|
||||
- 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.
|
||||
## 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.
|
||||
|
||||
- Avoid creative alternatives.
|
||||
- Do not propose multiple solutions unless asked.
|
||||
- Produce a single, minimal, correct implementation.
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user