2.1 KiB
2.1 KiB
Project Development Guide
This file serves as the entry point for project development, directing to appropriate constraint files based on development context.
Project Structure
social-app/
├── apps/ # Flutter mobile app
├── backend/ # FastAPI backend service
├── infra/ # Infrastructure (Docker, deployment scripts)
└── docs/ # Documentation and design/planning artifacts
Rules Hierarchy
Follow this hierarchy when developing:
~/.config/opencode/AGENTS.md # Global core rules (skills, agents, process)
├── This file (root AGENTS.md) # Project-level entry
│ ├── backend/AGENTS.md # Backend-specific rules
│ └── apps/AGENTS.md # Frontend-specific rules
Development Guidance
| Development Context | Follow Rules |
|---|---|
| Backend Python dev | backend/AGENTS.md |
| Flutter mobile dev | apps/AGENTS.md |
| Infrastructure/ops | This file + infra/ directory conventions |
| API doc changes | Sync to docs/runtime/runtime-route.md |
Git Workflow
- Default branch:
dev - Feature development: use worktree
git worktree add -b feature/xxx ../feature-xxx dev - Never develop directly on
main - Never push to remote unless explicitly requested by user
Skills (Domain Knowledge)
Project-specific skills are available in .opencode/skills/:
| Skill | Purpose | When to Use |
|---|---|---|
| ag-ui | AG-UI protocol for agent-user interaction | Agent chat, streaming events, tool calls, state sync |
| crewai | CrewAI framework for multi-agent orchestration | Multi-agent systems, agent collaboration, task automation |
Usage: Reference skills by name (e.g., "use the ag-ui skill") in development rules. Skills provide complete documentation, examples, and best practices.
Supabase Services
Project uses locally hosted Supabase for development.
- Docker config:
infra/docker/docker-compose.yml - Start services:
cd infra/docker && docker compose up -d - Stop services:
cd infra/docker && docker compose down