tomevault-io Liquid Galaxy Code Converter
Overview
This skill converts code snippets, prototypes, and reference implementations from other languages (JavaScript, Python, Kotlin, Swift) into production-quality Dart/Flutter code that follows the Liquid Galaxy Controller-to-Rig architecture.
Announce at start: "I'm using the lg-code-converter skill to convert [Source Language] code to Dart/Flutter."
GUARDRAIL: If the student doesn't understand why the conversion choices were made, trigger the Critical Advisor (.agent/skills/lg-critical-advisor/SKILL.md).
Common Conversion Scenarios
1. JavaScript → Dart (LG Web Apps to Flutter)
Many existing LG apps (BYOP, Laser Slides) are web-based. Convert their patterns:
| JavaScript Pattern | Dart/Flutter Equivalent |
|---|---|
fetch() / XMLHttpRequest |
http.get() / http.post() |
WebSocket |
dartssh2 (SSH) for LG rig communication |
document.getElementById() |
Provider + Consumer widget |
setTimeout / setInterval |
Future.delayed() / Timer.periodic() |
JSON.parse() / JSON.stringify() |
jsonDecode() / jsonEncode() |
class extends EventEmitter |
class with ChangeNotifier |
Promise / async/await |
Future / async/await |
module.exports |
Dart library exports (no special syntax) |
2. Python → Dart (Data Processing Scripts)
Convert Python data pipelines (API fetch → transform → KML) to Dart:
| Python Pattern | Dart Equivalent |
|---|---|
requests.get() |
http.get() |
json.loads() |
jsonDecode() |
f"string {var}" |
'string $var' or 'string ${expr}' |
dict / list |
Map<String, dynamic> / List<T> |
with open() as f |
File(path).readAsString() |
class: |
class ClassName { } |
try/except |
try/catch |
__init__ |
Constructor |
@property |
Dart getter: Type get name => _name; |
3. Kotlin/Swift → Dart (Native Mobile to Flutter)
Convert existing native LG controller apps to cross-platform Flutter:
| Native Pattern | Dart/Flutter Equivalent |
|---|---|
val/let (immutable) |
final |
var (mutable) |
var (no type annotation) or typed |
data class / struct |
Plain Dart class with final fields |
suspend fun / async |
Future<T> functionName() async |
LiveData / @Published |
ChangeNotifier + notifyListeners() |
ViewModel |
Service class registered in MultiProvider |
Coroutine / DispatchQueue |
Future, Isolate, compute() |
Conversion Process
Step 1: Analyze Source Code
- Identify the code's purpose in the LG context (SSH command? KML generation? API fetch?).
- Map source patterns to Dart equivalents.
- Identify LG-specific logic (coordinate handling, KML XML, SSH commands).
Step 2: Convert with Architecture Alignment
- Place converted code in the correct Flutter file:
- Network/SSH logic →
services/ - KML generation →
services/kml_service.dartor a converter inutils/ - Data models →
models/ - UI logic →
screens/orwidgets/
- Network/SSH logic →
- Apply Dart conventions:
///doc comments,finalfields, typed collections. - Use
Providerfor state instead of global variables.
Step 3: Verify
flutter analyze— zero errors.flutter test— write a test for the converted logic.- Compare output of original and converted code with identical inputs.
Example: Convert JS KML Generator to Dart
JavaScript (original):
function generateFlyTo(lat, lon, alt, heading, tilt, range) {
return `<gx:FlyTo>
<gx:duration>3</gx:duration>
<LookAt>
<longitude>${lon}</longitude>
<latitude>${lat}</latitude>
<altitude>${alt}</altitude>
<heading>${heading}</heading>
<tilt>${tilt}</tilt>
<range>${range}</range>
</LookAt>
</gx:FlyTo>`;
}
Dart (converted):
/// Generates a KML FlyTo element for Google Earth camera navigation.
///
/// Note: KML uses longitude,latitude order internally, but this
/// method accepts latitude,longitude (the intuitive order).
String generateFlyTo({
required double latitude,
required double longitude,
double altitude = 0,
double heading = 0,
double tilt = 60,
double range = 15000,
double duration = 3.0,
}) {
return '''<gx:FlyTo>
<gx:duration>$duration</gx:duration>
<LookAt>
<longitude>$longitude</longitude>
<latitude>$latitude</latitude>
<altitude>$altitude</altitude>
<heading>$heading</heading>
<tilt>$tilt</tilt>
<range>$range</range>
</LookAt>
</gx:FlyTo>''';
}
⛔ Student Interaction Checkpoints
After Conversion — Understanding Check
Before applying any converted code, STOP and engage the student:
⛔ STOP and WAIT — Ask:
"Before I apply this conversion, can you explain what the original code does? What will change in the Dart version?"
Wait for the student's answer. Evaluate:
- ✅ Correct: Acknowledge, then proceed with the conversion.
- ⚠️ Partially correct: Guide them — highlight the key pattern change (e.g.,
Promise→Future,EventEmitter→ChangeNotifier). - ❌ Wrong or "I don't know": Walk through the original code line by line. Link to lg-learning-resources (.agent/skills/lg-learning-resources/SKILL.md).
After Applying — Trace Exercise
⛔ STOP and WAIT — Ask:
"Trace the data flow in this converted Dart code. Where does the input come in, how is it transformed, and where does the output go?"
Do NOT proceed to verification until the student can trace the flow.
Pattern Comparison
Present the original and converted code side-by-side, then ask:
"What are the 2-3 biggest differences between the original and the Dart version? Which Dart feature improves on the original?"
⛔ STOP and WAIT for the student's answer before moving on.
Handoff
After conversion → lg-code-reviewer for quality review.
🔗 Skill Chain
After the conversion is applied and the student can explain the Dart version, automatically offer the next stage:
"Conversion complete! You clearly understand the Dart patterns now. Let's run a code review to make sure the converted code meets LG quality standards. Ready for the Code Review? 🔍"
If student says "ready" → activate .agent/skills/lg-code-reviewer/SKILL.md.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.