SUMMARY
Gemini Code Assist (IDE) uses markdown configuration while Jinn (CLI) uses yaml. They differ on 7 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Gemini Code Assist | Jinn |
|---|---|---|
| Config format | markdown | yaml |
| Hierarchy support | ✓ | ✗ |
| Global config | ✗ | ✓ |
| Project config | ✓ | ✗ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | CLI |
| Schema / structure | Free-form (Markdown) | unknown |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
KEY DIFFERENCES
Gemini Code Assist: markdown. Jinn: yaml.
Gemini Code Assist: Supported. Jinn: Not supported.
Gemini Code Assist: Not supported. Jinn: Supported.
Gemini Code Assist: Supported. Jinn: Not supported.
Gemini Code Assist: Supported. Jinn: Not supported.
Gemini Code Assist: Supported. Jinn: CLI.
Gemini Code Assist: Free-form (Markdown). Jinn: unknown.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Gemini Code Assist, configure GEMINI.md. If you use Jinn, configure config.yaml. Many projects include config files for multiple tools so each team member can use their preferred editor.
PORTABILITY TIP
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md