This rule → Global effect? → Yes → Root AGENTS.md
         → Specific module? → Yes → Subdirectory AGENTS.md or Skill
         → Complex workflow? → Yes → Skill
         → Uncertain? → Consider if it's really necessary

~/.config/opencode/AGENTS.md   # User global (shared by all projects)
    ↓ Inherit/Override
project/AGENTS.md              # Project root (project-level rules)
    ↓ Inherit/Override
project/src/python/AGENTS.md   # Module-level (specific module rules)

# ❌ Wrong: Project AGENTS.md duplicates user global rules
# Language
Always respond in Chinese.          # Already defined in ~/.config/opencode/AGENTS.md, duplicate!

# Git
Short commit messages, no prefix    # Already defined in ~/.config/opencode/AGENTS.md, duplicate!

# ✅ Correct: Project AGENTS.md only contains project-specific rules
# Project Structure
src/ is the source code directory, tests/ is the test directory.

# Team Agreement
PRs must be reviewed by at least one person.

~/.config/opencode/
└── AGENTS.md                # User global rules (shared by all projects)

project/
├── AGENTS.md                # Project global rules (< 50 lines)
├── docs/
│   ├── AGENTS.md            # Project-level documentation rules, architecture descriptions
│   ├── architecture.md      # Architecture documentation
│   └── api-guide.md         # API usage guide
├── src/
│   ├── python/
│   │   └── AGENTS.md        # Python module-specific rules
│   └── frontend/
│       └── AGENTS.md        # Frontend module-specific rules
└── .opencode/
    └── skills/
        └── deploy/SKILL.md  # Deployment workflow (complex task)

Is this rule needed in every session?
├── Yes → Is it needed for all projects?
│   ├── Yes → Place in ~/.config/opencode/AGENTS.md (user global)
│   └── No → Place in project root AGENTS.md
└── No → Is it for a specific module/folder?
    ├── Yes → Place in AGENTS.md under that folder
    └── No → Is it project-level documentation/architecture description?
        ├── Yes → Place in docs/AGENTS.md
        └── No → Is it a complex workflow?
            ├── Yes → Create a Skill
            └── No → Consider if this rule is really necessary

1. Confirm which global rules are needed (language, principles, Git)
2. Determine if module-level rules need to be placed separately
3. Write a concise root AGENTS.md
4. If needed, create subdirectory AGENTS.md, docs/AGENTS.md or Skill

1. Read the existing AGENTS.md
2. List all rule modules
3. Mark the scope of each module (global/module/project documentation/task)

1. Create subdirectory AGENTS.md, docs/AGENTS.md or Skill files
2. Migrate relevant rules (maintain format and hierarchy)
3. Update the root AGENTS.md, removing split content
4. Add necessary reference notes (optional)

1. Check if the root AGENTS.md is concise
2. Confirm that subdirectory files have complete content
3. Verify no rules are lost or duplicated
4. Confirm docs/AGENTS.md contains project-level documentation rules (if applicable)

# Language
Always respond in Chinese.

# Core Principles
- Prioritize simple, maintainable solutions
- Avoid over-engineering

# Git
- Short commit messages, no prefix

# Module Rules
Python projects → Refer to src/python/AGENTS.md
Frontend projects → Refer to src/frontend/AGENTS.md

# Documentation
Project architecture → Refer to docs/AGENTS.md

# Python Project Specifications

## Tools
Use uv for dependency management, ruff for formatting.

## Principles
- Fast-fail: Only use try-except at the outer layer
- Prohibit hard-coded credentials

# Project Documentation Specifications

## Architecture Description
This project uses a three-tier architecture, see architecture.md for details.

## API Documentation
- REST API specifications → api-guide.md
- GraphQL Schema → schema.graphql