Files
social-app/AGENTS.md
T
qzl 1f6cb1a48f refactor: 删除未使用的 api_external_url 配置并完善 runtime 文档
- 删除 SupabaseSettings 中未使用的 api_external_url computed field
- 更新测试文件移除相关测试用例
- backend/AGENTS.md 新增软删除设计规则
- runtime-database.md 更新表结构(删除 user_agents,表名更新为 agent_chat_sessions/messages,system_agents)
- runtime-frontend.md 补充路由结构和功能模块说明
- 根 AGENTS.md 清理过时技能路径引用
2026-03-06 18:25:18 +08:00

57 lines
2.0 KiB
Markdown

# 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:
```
├── 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](backend/AGENTS.md) |
| Flutter mobile dev | [apps/AGENTS.md](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)
| 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`