- Skills
- 11
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
Gustavo Dutra Domingues Saboia 的 Skills 11
{name=null}
Describe what {name} does and when the agent should use it
tdd
Develops with TDD driven by BDD scenarios (Given/When/Then), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.
security-audit
Audits code for exploitable security problems (injection, broken access control, leaked secrets, unsafe input handling, vulnerable dependencies) and reports only verified findings with severity and fix. Use when asked for a security review or audit, before a release, or when a change touches authentication, permissions, secrets, user input, file paths, commands or network calls.
requirements
Turns a request or idea into clear, testable requirements, with scope, user stories and Given/When/Then acceptance criteria. Use when starting a new feature or project, when a request is vague, or when asked for requirements, user stories, acceptance criteria or a feature spec.
refactoring
Restructures existing code without changing its behavior, in small steps with the tests green after each one. Use when asked to refactor, clean up, simplify, rename, extract, move or reorganize code, or to work on items recorded as "Refactor later".
implementation-plan
Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.
git-workflow
Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.
frontend
Builds web interfaces that are clear, accessible and consistent, with a deliberate visual direction and simple component code (Vue 3 and TypeScript by default). Use when creating or changing pages, components, layouts, forms or styles, or when asked about UI, UX, visual design or accessibility.
docs
Writes and updates project documentation (README, project spec, ADRs, CHANGELOG, code comments) so it stays short, true and in sync with the code. Use when creating or changing docs, recording an architecture decision, preparing a release, describing what a project is, or when a change alters behavior that docs describe.
design-principles
Applies KISS, SOLID, DRY and YAGNI, in that priority, to design and refactoring decisions, with a rule for when they conflict. Use when designing a module or API, choosing between implementations, adding an abstraction, deciding whether to remove duplication, or judging code structure.
code-review
Reviews a diff, branch or pull request for real problems (bugs, missing tests, security, needless complexity) and reports only verified findings, ranked by severity. Use when asked to review code, a diff, a branch, a commit or a pull request, or before saying a change is ready to merge.