frb-debugging
Troubleshoots Flutter Rust Bridge codegen and runtime integration issues.
Install
mkdir -p .claude/skills/frb-debugging && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12453" && unzip -o skill.zip -d .claude/skills/frb-debugging && rm skill.zipInstalls to .claude/skills/frb-debugging
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when generated code looks wrong, code generation fails, or you need to understand FRB internalsKey capabilities
- →Dump intermediate representations (IR)
- →Access generated spec and code
- →View effective configuration
- →Generate debug logs
- →Troubleshoot runtime errors in generated code
How it works
The skill accesses intermediate representations and debug logs to provide insights into the code generation process and runtime behavior. It uses a configuration setting to enable dumping of internal data.
Inputs & outputs
When to use frb-debugging
- →Debug generated code
- →Fix code generation failures
- →Understand FRB internals
About this skill
FRB Debugging
Note: Check your user-level
remote-testingrules before running commands. Codegen and debugging may require remote execution.
When to Use
- Generated code looks wrong
- Code generation fails
- Need to understand FRB internals
- Runtime errors in generated code
Quick Diagnostics
Dump Intermediate Representations
The in-tree examples by default enable dump_all: true in flutter_rust_bridge.yaml for debugability.
Therefore, you can check rust/target/frb_dump/ for:
- Effective configuration
- IR (intermediate representation)
- Generated spec and code
- ...
Debug Logs
RUST_LOG=debug flutter_rust_bridge_codegen ...
Full Troubleshooting
If above doesn't help, see:
website/docs/docs/guides/contributing/tip.mdwebsite/docs/manual/troubleshooting.md
Before going deep into FRB internals, first check whether you are actually seeing failure propagation from unstable generated outputs or integrate templates.
In particular:
- If CI failures may be explained by failure propagation, repeated package-level drift, or unstable generated outputs, you MUST use
frb-fix-cifirst - You MUST only stay in
frb-debuggingafterfrb-fix-cihas ruled out those simpler explanations
Related Skills
frb-code-generation- Which generation commands to runfrb-fix-ci- Diagnose CI failure propagation before deep debuggingfrb-develop-feature- Development workflow
When not to use it
- →When CI failures are due to failure propagation
- →When CI failures are due to repeated package-level drift
- →When CI failures are due to unstable generated outputs
Limitations
- →Requires 'dump_all: true' in 'flutter_rust_bridge.yaml' for full intermediate representation dumps
- →Requires `RUST_LOG=debug` environment variable for detailed debug logs
How it compares
This skill provides direct access to internal FRB data structures and debug logs, unlike manual inspection of generated code.
Compared to similar skills
frb-debugging side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| frb-debugging (this skill) | 0 | 4mo | Review | Intermediate |
| rust-router | 3 | 2mo | No flags | Advanced |
| debug-fuzzer-failure | 1 | 3mo | Review | Advanced |
| implementing-cards | 7 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
rust-router
actionbook
CRITICAL: Use for ALL Rust questions including errors, design, and coding. HIGHEST PRIORITY for: 比较, 对比, compare, vs, versus, 区别, difference, 最佳实践, best practice, tokio vs, async-std vs, 比较 tokio, 比较 async, Triggers on: Rust, cargo, rustc, crate, Cargo.toml, 意图分析, 问题分析, 语义分析, analyze intent, question analysis, compile error, borrow error, lifetime error, ownership error, type error, trait error, value moved, cannot borrow, does not live long enough, mismatched types, not satisfied, E0382, E0597, E0277, E0308, E0499, E0502, E0596, async, await, Send, Sync, tokio, concurrency, error handling, 编译错误, compile error, 所有权, ownership, 借用, borrow, 生命周期, lifetime, 类型错误, type error, 异步, async, 并发, concurrency, 错误处理, error handling, 问题, problem, question, 怎么用, how to use, 如何, how to, 为什么, why, 什么是, what is, 帮我写, help me write, 实现, implement, 解释, explain
debug-fuzzer-failure
noir-lang
End-to-end workflow for debugging SSA fuzzer failures from CI. Extracts a reproduction case from GitHub Actions logs, then bisects SSA passes to identify the bug. Use when a `pass_vs_prev` or similar fuzzer test fails in CI.
implementing-cards
bcollazo
Fill out the implementation of effects of different attacks, abilities, and trainer cards in this Pokemon TCG Pocket engine codebase.
flutter-architecture-expert
flutter-it
Architecture guidance for Flutter apps using the flutter_it construction set (get_it, watch_it, command_it, listen_it). Covers Pragmatic Flutter Architecture (PFA) with Services/Managers/Views, feature-based project structure, manager pattern, proxy pattern with optimistic updates and override fields, DataRepository with reference counting, scoped services, widget granularity, testing, and best practices. Use when designing app architecture, structuring Flutter projects, implementing managers or proxies, or planning feature organization.
write-rust-tests
RediSearch
Write Rust tests to verify correctness of Rust code.
rust-errors
EpicenterHQ
Rust to TypeScript error handling patterns for Tauri apps. Use when defining Rust errors that will be passed to TypeScript, handling Tauri command errors, or creating discriminated union error types.