Augment Code vs FusionComparisonUpdated 2026-03-16
SUMMARY
Augment Code (IDE) uses markdown configuration while Fusion (IDE) uses mdc. They differ on 5 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Augment Code | Fusion |
|---|---|---|
| Config format | markdown | mdc |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | ✓ |
| Schema / structure | Free-form (Markdown) | Hybrid (MDC frontmatter + Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
SIDE-BY-SIDE CODE SAMPLES
Augment Code
AGENTS.md
markdown
# Project Rules
## Architecture
- Clean architecture with domain, application, and infrastructure layers
- Domain models must not import from infrastructure
- Use dependency injection for all services
## Code Style
- TypeScript strict mode, no implicit any
- Use Result<T, E> for error handling in domain layer
- Prefer composition over inheritance
- Maximum 3 parameters per function; use options objects for more
## Testing
- Unit tests for domain logic (no mocking frameworks)
- Integration tests for API endpoints
- E2E tests for critical user journeys with Playwright
## Dependencies
- Do not add new dependencies without discussing first
- Prefer standard library over third-party for simple tasks
Fusion
.builder/rules/*.mdc
mdc
---
description: React component conventions
globs: src/components/**/*.tsx
alwaysApply: false
---
# React Component Rules
## Structure
- Use functional components with TypeScript
- Define props interface above the component
- Export components as named exports
## Styling
- Use the project design system tokens for spacing and colors
- Prefer utility classes over custom CSS
- Keep component-specific styles colocated
## Patterns
- Wrap async data in Suspense boundaries
- Use forwardRef for reusable interactive components
- Keep components under 150 lines; extract hooks for logic
## Accessibility
- All interactive elements need aria-labels
- Use semantic HTML elements (nav, main, section)
- Ensure keyboard navigation works for custom widgets
KEY DIFFERENCES
Augment Code: markdown. Fusion: mdc.
Augment Code: Supported. Fusion: Not supported.
Augment Code: Supported. Fusion: Not supported.
Augment Code: Supported. Fusion: Not supported.
Augment Code: Free-form (Markdown). Fusion: Hybrid (MDC frontmatter + Markdown).
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Augment Code, configure AGENTS.md. If you use Fusion, configure .builder/rules/*.mdc. 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
Tool pages:
File references:
agentconfig.ing2026-03-16COMPARE(1)