Setup dev container and MCP infrastructure

Add dev container configuration with docker-compose, Dockerfile, and entrypoint script

- Create .devcontainer/devcontainer.json for VS Code dev container
- Create .devcontainer/docker-compose.yml for container setup
- Add Dockerfile with Python, Go, Rust, R, and jj tools
- Add docker-entrypoint.sh to initialize .ai_index and start mcp-server
- Add Makefile for container management and MCP operations
- Add .gitignore entries for AI index
- Add OpenCode global instructions
- Add basic MCP server and tool for listing Go imports
- Add Zed integration configuration
- Update README with project vision and structure
This commit is contained in:
2026-02-21 13:17:51 +01:00
parent c3923a3f59
commit c4947e0df9
13 changed files with 247 additions and 0 deletions

29
.opencode/instructions.md Normal file
View File

@@ -0,0 +1,29 @@
# 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.