Tabnine vs VoidComparisonUpdated 2026-03-16
SUMMARY
Tabnine (IDE) uses markdown configuration while Void (IDE) uses markdown. They differ on 0 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Tabnine | Void |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✗ | ✗ |
| Global config | ✗ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✗ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
SIDE-BY-SIDE CODE SAMPLES
Tabnine
.tabnine/guidelines/*.md
markdown
# Application Guidelines
## Architecture
- This is a monorepo managed with Turborepo
- Apps: web (Next.js), api (Express), mobile (React Native)
- Shared packages: ui, config, types
## Code Standards
- TypeScript strict mode in all packages
- Use barrel exports (index.ts) for public APIs
- No default exports; use named exports everywhere
- Prefer async/await over raw Promises
## API Design
- RESTful endpoints follow /api/v1/{resource} pattern
- All responses use { data, error, meta } envelope
- Validate request bodies with Zod schemas
- Return 4xx for client errors, 5xx for server errors
## Database
- Use Prisma ORM for all database operations
- Migrations checked into source control
- Soft-delete pattern: use deletedAt timestamp, never hard delete
- All timestamps stored as UTC
## Testing
- Jest for unit tests, Playwright for E2E
- Test files colocated: foo.ts -> foo.test.ts
- Mock external services, never call real APIs in tests
Void
.void/rules/*.md
markdown
---
description: Python backend conventions
globs: "app/**/*.py"
auto_apply: true
---
# Backend Rules
## Stack
- Python 3.12 with FastAPI
- SQLAlchemy 2.0 with async sessions
- Alembic for migrations
- pytest for testing
## Conventions
- Use type hints on all function signatures
- Async endpoints by default
- Pydantic v2 models for request/response schemas
- Repository pattern for database access
## File Structure
- app/api/routes/ — API endpoints
- app/models/ — SQLAlchemy models
- app/schemas/ — Pydantic schemas
- app/services/ — Business logic
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Tabnine, configure .tabnine/guidelines/*.md. If you use Void, configure .void/rules/*.md. Many projects include config files for multiple tools so each team member can use their preferred editor.
PORTABILITY TIP
sync-instructions.sh
bash
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md
SEE ALSO
agentconfig.ing2026-03-16COMPARE(1)