Agent Skills
› chrisbanes/skills
› using-chrisbanes-skills
using-chrisbanes-skills
GitHub用于在 Kotlin 或 Jetpack Compose 开发中，根据代码信号精准路由并加载对应子技能。通过判断状态、性能、UI 设计或并发等具体关注点，指导开发者选择最合适的专项技能进行调试、分析或编码，避免盲目加载。
Trigger Scenarios
需要调试 Kotlin 或 Compose 源码但原因不明时
任务涉及多个 Kotlin 或 Compose 技术细节（如 Flow、导航、UI 组件）
Install
npx skills add chrisbanes/skills --skill using-chrisbanes-skills -g -y
SKILL.md
Frontmatter
{
"name": "using-chrisbanes-skills",
"paths": [
"**\/*.kt",
"**\/*.kts"
],
"description": "Use when debugging, benchmarking, or profiling leads into Kotlin or Jetpack Compose source before the cause is known, or when one task spans multiple Kotlin or Compose concerns, especially plain Kotlin Flow or navigation delivery plus sealed branching."
}
Using chrisbanes skills
Core principle
Route by the decision the code needs, not by the number of APIs mentioned. Load one cluster when its shared procedure owns the concern; add a specialist only when its independent behavior changes the same work.
Routing procedure
- Read the task and the Kotlin source that makes the concern concrete.
- If one focused skill clearly matches, load it directly and stop routing.
- Before loading a Compose skill, point to a concrete Compose API or composable in the inspected source, or to an explicit request to create or design Compose code. A hypothetical UI consumer is not evidence. If neither form of evidence exists, stay in the Kotlin cluster even when the task mentions UI, routes, or navigation.
- Match each observed code signal to the table below.
- Add a second skill only when it owns an independent decision in the same change; do not load adjacent skills speculatively.
- Finish routing when every material concern has one focused owner and those skills are loaded before advice or edits.
Common routes
| Task signal | Start with |
|---|---|
| Evidenced Compose state, effects, screen ownership, or UI event collection | compose-state-and-effects |
Recomposition, stability, frame-rate reads, back-writing, or @ReadOnlyComposable |
compose-performance |
| Component modifiers, caller placement, slots, or public content shape | compose-component-design |
| Visibility, value, transition, content-swap, or other motion API choice | compose-animations |
| Keyboard, TV, D-pad, focus targets, custom traversal, or key events | compose-focus-navigation |
| Compose UI, screenshot, semantics, focus/key, or interaction-state tests | compose-ui-testing-patterns |
| Coroutine ownership, cancellation, Flow state/events, sharing, or replay | kotlin-concurrency-and-flow |
Kotlin classification, when, guards, exhaustiveness, smart casts, or null branches |
kotlin-control-flow |
| Kotlin function ownership, domain types, expect/actual, or platform seams | kotlin-api-design |
| Planned Gradle execution or a Gradle-centered warning/failure workflow | gradle-run |
| One ready GitHub issue or in-chat task needs repository-aware planning | to-plan |
| Polling PRs/MRs, review comments, CI failures, or routine follow-up | shepherd |
Combination boundaries
- Add
kotlin-concurrency-and-flowto Compose state work only when delivery, replay, sharing, or cancellation is a separate concern. Add state ownership or performance only when animation work changes that concern too. - Pair focus navigation with UI testing when the task also needs a test shape.
- Add
kotlin-control-flowwhen a Kotlin concern also changes branching. Plain Kotlin route delivery plus a sealed mapping stays in the Kotlin cluster; do not add Compose without the evidence required in step 3. - Load
gradle-runonly for planned Gradle execution or an existing Gradle workflow, not incidental Kotlin or Compose advice.
Version History
-
2026.8.24
Current 2026-08-27 17:16
精简指令冗余度；重新认证 Kotlin 和 Gradle 技能评估标准。
-
2026.8.16
2026-08-19 19:31
新增 Gradle 运行工作流支持，增加直接聊天内规划功能。
-
2026.8.5
2026-08-16 02:45
重构技能分类，将15个细粒度入口合并为5个自包含集群；更新路由表以匹配新的技能簇；移除旧的技能名称引用，优化了路由决策逻辑。
- 2026.7.21 2026-07-24 12:25
