- Skills
- 22
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 1
- Stars
- ★ 0
Shounak Mulay 的 Skills 22
verify-change
Use when verifying DevPulse changes, choosing scoped Gradle checks, reviewing database or feed changes, or reporting platform verification gaps.
test-change
Use when adding or reviewing behavioral tests for DevPulse features, state/effects, use cases, network boundaries, paging, persistence or coroutine lifetimes.
plan-change
Use when planning a DevPulse feature, bug fix or refactor, clarifying ownership and edge cases, or deciding the implementation and acceptance checks.
navigation-3
Use when changing DevPulse Navigation3 routes, tab stacks, adaptive list/detail metadata or back behavior.
ktlint-fix
Use when explicitly asked to run the legacy ktlint workflow; first check whether formatting tasks actually exist.
implement-change
Use when implementing or refactoring existing DevPulse behavior across screens, state, use cases, repositories or shared utilities after establishing acceptance checks.
change-platform
Use when changing DevPulse Koin wiring or startup, expect/actual implementations, notifications, permissions, native services, background workers or app entry points.
change-network
Use when changing DevPulse HTTP clients, transport responses, serialization, remote feed parsing or discovery catalog download and reconciliation.
change-database
Use when changing DevPulse Room entities, indexes, FTS, triggers, migrations, SQL queries, transactions, paging or persisted article/user state.
add-screen
Use when adding a screen to an existing DevPulse feature module, including state, events, effects, ViewModel and navigation wiring.
add-feature
Use when adding a new DevPulse KMP feature module, tab or top-level feature and wiring its build, DI and navigation.
verify-change
Use when verifying DevPulse changes, choosing scoped Gradle checks, reviewing database or feed changes, or reporting platform verification gaps.
test-change
Use when adding or reviewing behavioral tests for DevPulse features, state/effects, use cases, network boundaries, paging, persistence or coroutine lifetimes.
plan-change
Use when planning a DevPulse feature, bug fix or refactor, clarifying ownership and edge cases, or deciding the implementation and acceptance checks.
navigation-3
Use when changing DevPulse Navigation3 routes, tab stacks, adaptive list/detail metadata or back behavior.
ktlint-fix
Use when explicitly asked to run the legacy ktlint workflow; first check whether formatting tasks actually exist.
implement-change
Use when implementing or refactoring existing DevPulse behavior across screens, state, use cases, repositories or shared utilities after establishing acceptance checks.
change-platform
Use when changing DevPulse Koin wiring or startup, expect/actual implementations, notifications, permissions, native services, background workers or app entry points.