# .ainative Directory

**Purpose**: Project context and configuration for AI coding assistants
**Compatible With**: Gemini CLI, Claude Code, Cursor, Windsurf, and other AI tools

---

## Quick Start

### For Gemini CLI Users

```bash
# Navigate to project
cd /path/to/your/project

# Start Gemini CLI (automatically loads .ainative/settings.json)
gemini

# Verify context loaded
@memory What is this project?
```

### For Claude Code Users

```bash
# Open project (automatically reads .claude/ and .ainative/)
claude /path/to/your/project
```

### For Other AI Tools

1. Read `AINATIVE.md` for complete project context
2. Review `settings.json` for configuration details
3. Follow rules in `rules/` directory

---

## Directory Structure

```
.ainative/
├── README.md                        # This file (quick reference)
├── AINATIVE.md                      # Complete project context
├── settings.json                    # Gemini CLI-compatible settings
└── rules/
    └── gemini-cli-alignment.md      # Alignment with Gemini CLI conventions
```

---

## File Descriptions

### AINATIVE.md
**Primary project context file** containing:
- Project overview and tech stack
- Repository paths
- Architecture and patterns
- Development workflow
- Git rules (ZERO TOLERANCE for AI attribution)
- Environment variables
- Key file references

**When to read**: Always load first for project understanding

### settings.json
**Gemini CLI configuration** following their schema:
- Project metadata
- Path configurations
- Context file references
- Model settings
- Tool permissions
- Security policies
- MCP server integrations
- Development settings

**When to read**: For tool configuration and security settings

### rules/gemini-cli-alignment.md
**Compatibility guide** for Gemini CLI and other AI tools:
- Dual configuration approach (.ainative + .claude)
- Configuration hierarchy
- Tool integration patterns
- Path references
- AI coding rules (universal)
- Usage guidelines for different tools
- MCP server integration
- Best practices

**When to read**: When using Gemini CLI or ensuring cross-tool compatibility

---

## Important Rules

### ZERO TOLERANCE: AI Attribution
**NEVER include in commits, PRs, or issues:**
- No "Claude", "Anthropic", "Gemini", "Google"
- No "Generated with [AI Tool]"
- No "Co-Authored-By: [AI Tool]"
- No AI tool attribution

### Pre-Commit Checklist
1. Lint - must pass
2. Type-check - must pass
3. Build - must succeed
4. Tests - must pass

---

## Context Loading Order

1. **Primary**: `.ainative/AINATIVE.md` (project fundamentals)
2. **Supplementary**: `.claude/CLAUDE.md` (Claude-specific instructions)
3. **Backlogs and Summaries**: as needed

---

## Common Tasks

### Start Development
```bash
npm run dev          # Start dev server
```

### Verify Code Quality
```bash
npm run lint         # ESLint
npm run type-check   # TypeScript
npm run build        # Production build
npm test             # Run tests
```

### Check Open Issues
```bash
gh issue list --label "critical"
gh issue list --label "high-priority"
```

---

## MCP Servers Available

Configure MCP servers in `settings.json` or `.claude/mcp.json`.
See `settings.json` for MCP configuration.

---

## Quick Reference

| What | Where |
|------|-------|
| Project context | `.ainative/AINATIVE.md` |
| Gemini CLI settings | `.ainative/settings.json` |
| Alignment rules | `.ainative/rules/gemini-cli-alignment.md` |
| Claude Code context | `.claude/CLAUDE.md` |

---

## Support

### Documentation
- Gemini CLI: https://google-gemini.github.io/gemini-cli/
- Claude Code: https://docs.claude.com/en/docs/claude-code/
