Enforce 5-layer Dart/Flutter architecture rules for backend development tasks.
npx skills add https://github.com/MHD-Nour-KJ/Intertwined --skill backend-logic
Please help me install this Agent Skill. Skill: backend-logic Source: https://github.com/MHD-Nour-KJ/Intertwined/tree/main/.agent/skills/backend-logic Command: npx skills add https://github.com/MHD-Nour-KJ/Intertwined --skill backend-logic
This Skill eliminates the risk of implementing new backend features, refactors, or services for the Beautifully Done app that violate core architectural rules, repeat past mistakes, or introduce untestable, unmaintainable code by providing the full rationale behind every backend design decision.
Use the backend-logic skill to review the architectural rationale before implementing any new feature, refactor, or service for the Beautifully Done backend to avoid critical design mistakes.
High-intent search queries and answers about installing and using this skill.
To structure dependency injection in a Flutter offline-first app, use get_it to enforce strict 5-layer isolation. This prevents private constructors from breaking DI and ensures backend architecture remains testable and free of god classes.
Correct SQLite database migrations in Dart require following specific database migration conventions and proper DB clear order. This prevents data corruption and ensures architectural consistency across application updates.
Cascading changes leak into DAO or Provider layers because logic is misplaced. You must place cascade logic in the stateless Orchestrator layer to maintain testability, enforce strict layer isolation, and avoid creating god classes.
Handle errors in Dart backend architecture by implementing Result<T> error handling patterns within the stateless orchestrator layer. This maintains testable strict layer isolation and prevents untestable code from spreading across your architecture.
Common gotchas when refactoring a 5-layer Flutter backend include using private constructors that break DI, incorrect DB clear order during SQLite migrations, and un-cancelled timer stream subscriptions that cause production bugs.
Yes, you can use get_it for dependency injection across all 5 layers of a Dart backend. It enforces strict layer isolation, ensures correct DI setup, and prevents architectural mistakes like private constructors breaking dependency injection.
wildbitcaRun Flutter analyzer and apply fixes to eliminate code issues.
zzafergokReplace exceptions with explicit Result types in TypeScript business logic.
wildbitcaImplement Result<T> types for standardized async error handling in Flutter apps.
NNPopovStructure Flutter apps into layered UI, logic, and data boundaries.
