busic-ui-development
SkillDev toolsBuSic UI development guidelines. Use when developing Screens and Widgets to confirm base class selection, responsive shell, theme tokens, i18n, and desktop platform differences
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the busic-ui-development skill
What this skill tells your AI
The instructions your AI receives, as published by glowled/busic in .agents/skills/busic-ui-development/SKILL.md and read by ahel’s review.
何时使用
- 新增 Screen、Widget 或路由接入
- 调整主题、响应式布局、国际化或桌面端壳层
- 需要判断某段 UI 逻辑应写在 Widget、Notifier 还是共享组件里
先看这些真源
docs/30-reference/ui.mddocs/10-project/ui-and-platform-quirks.mdlib/shared/widgets/responsive_scaffold.dartlib/core/router/app_router.dart
Widget 结构
- 纯展示且读 Provider：优先
ConsumerWidget - 需要生命周期：用
ConsumerStatefulWidget - 纯静态展示：
StatelessWidget - 复杂页面里的私有 UI 片段优先抽成同文件私有 Widget
- feature 专属可复用组件放到
presentation/widgets/
主题与响应式
- 统一通过
AppTheme与 theme extensions 取值 - 业务页面优先使用
context.appPalette、context.appSpacing、context.appRadii、context.appDepth - 不要在页面里堆魔法数字颜色、圆角和阴影
- 主壳层布局优先复用
ResponsiveScaffold
i18n 与交互
- 所有用户可见文本必须进 ARB
- 改了
lib/l10n/*.arb后记得flutter gen-l10n - 常见弹窗优先复用
CommonDialogs - 路由接入以
app_router.dart为准
平台差异提醒
- 桌面端关闭窗口默认是托盘隐藏，不一定等于退出
minimal模式是独立生命周期策略，不是普通页面皮肤- 改标题栏、托盘、极简模式时要同时检查桌面壳层逻辑
相关 Skill
Signals
- GitHub stars
- 27
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
busic-ui-development- Source
- github.com/glowled/busic