Kilo Code vs PearAIComparisonUpdated 2026-03-18
SUMMARY
Kilo Code (IDE) uses markdown configuration while PearAI (Editor) uses markdown. They differ on 1 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Kilo Code | PearAI |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✗ | ✗ |
| Global config | ✗ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✗ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | Editor |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | Kilo Code | PearAI |
|---|---|---|
| Project rules | .kilorules | .pearai/rules |
SIDE-BY-SIDE CODE SAMPLES
Kilo Code
.kilorules
markdown
# Project Rules
## Stack
- TypeScript 5.x with strict mode
- React 19 + Next.js 15 (App Router)
- Tailwind CSS v4 for styling
- Drizzle ORM for database access
## Code Standards
- Named exports only (no default exports)
- Prefer `const` assertions and satisfies operator
- Use Result<T, E> pattern for error handling
- Maximum 30 lines per function
## File Organization
- Colocate tests: `foo.ts` → `foo.test.ts`
- One component per file
- Barrel exports (index.ts) for public module APIs
## Git
- Conventional commits: feat|fix|chore|docs|test
- Squash merge feature branches
- Branch naming: type/description
PearAI
.pearai/rules
markdown
# PearAI Project Rules
## Framework
- Next.js 15 App Router with TypeScript
- Drizzle ORM with PostgreSQL
- TailwindCSS v4 for styling
## Patterns
- Use server actions for mutations
- Colocate loading.tsx and error.tsx with page routes
- Prefer RSC; add "use client" only when needed
## Naming
- Components: PascalCase (UserProfile.tsx)
- Utilities: camelCase (formatDate.ts)
- Database tables: snake_case
## Dependencies
- Do NOT add new dependencies without asking
- Use date-fns for date manipulation
- Use zod for all validation
## Commands
- Dev: pnpm dev
- Build: pnpm build
- Lint: pnpm lint
KEY DIFFERENCES
Kilo Code: Supported. PearAI: Editor.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Kilo Code, configure .kilocodemodes. If you use PearAI, configure .pearai/rules. 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-18COMPARE(1)