susomejias
- 9 skills
- 0 followers
- 6 hours ago last updated
- ▌ Testing · susomejias bundlePragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.
- ▌ Write Prd · susomejiasCreate a PRD through user interview, codebase exploration, and module design, then save it as a local file. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
- ▌ Git Commit · susomejias bundleUse this skill when creating git commits with emoji conventional commit messages, staged-file awareness, and commit-splitting guidance for mixed changes.
- ▌ Zero Tech Debt · susomejiasRework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".
- ▌ Systems Thinker · susomejias bundleCall this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.
- ▌ Find Buggy Commit · susomejiasFind the exact commit that introduced a bug, regression, or behavioral change using binary search. Supports autonomous mode (running tests automatically) and interactive mode (guided step-by-step). Use when the user wants to find when something broke, track down a regression, locate a bad commit, or figure out which commit caused a problem.
- ▌ Root Cause Tracing · susomejias bundleUse when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
- ▌ Systematic Debugging · susomejias bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
- ▌ NPM Security Best Practices · susomejias bundleApply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.