一键导入
money-tracker
money-tracker 收录了来自 garethbaumgart 的 7 个 skills,并提供仓库级职业覆盖和站内 skill 详情页。
这个仓库中的 skills
Prepare and shepherd pull requests from local changes with clear summary, behavior changes, risk analysis, test evidence, and disciplined review handling. Use when a user asks to prepare/open a PR, write a PR description, address review comments (including AI reviewers like Copilot, CodeRabbit, Sourcery), run multi-round review loops, or confirm merge readiness.
Turn raw product ideas into a clear, implementation-ready issue package by capturing intent, scope, acceptance criteria, dependencies, and execution mode. Use when a user has an idea and asks for issue planning.
Execute multiple GitHub issues concurrently using isolated git worktrees, one branch per issue, lane-aware startup rules, issue-specific implementation skills, tests, and one PR per issue. Use when the user asks to execute multiple issues in parallel (for example "Execute issues 5,6,7") or wants batch issue delivery with safe isolation.
Refine rough, incomplete, or ambiguous GitHub issues into decision-complete engineering specs with clear scope, acceptance criteria, implementation approach, test plan, and risks. Use when a user asks to improve an issue, clarify requirements, split scope, or produce implementation-ready backlog items.
Generate UX exploration artifacts as raw HTML option packs for product decision-making before Flutter implementation. Use when an issue has significant UX impact (onboarding, paywall, dashboard/navigation changes, new multi-step flows, high-risk interaction changes) and stakeholders need comparable options before coding.
Implement backend features with vertical slices and pragmatic Domain-Driven Design in .NET. Use when adding or refactoring API endpoints, commands/queries, domain rules, repositories, integrations, or tests for business-critical modules such as budgets, transactions, households, subscriptions, and provider sync flows.
Apply consistent Flutter UX and theming standards using Material 3, ThemeData, ColorScheme, ThemeExtension tokens, and component themes. Use when building or refactoring Flutter screens, introducing design tokens, changing theme behavior, adding dark/light modes, or reviewing UI code for theming consistency and reuse.