testonohm
- 15 skills
- 0 followers
- 12 hours ago last updated
- ▌ Debugging And Error Recovery · testonohmGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
- ▌ Browser Testing With Devtools · testonohmTests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
- ▌ Idea Refine · testonohm bundleRefines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
- ▌ Jira Task Workflow · testonohmGuides end-to-end delivery starting from an assigned Jira issue: load issue context via Atlassian MCP, clarify ambiguous requirements, establish root cause for bugs before coding, resolve repo from Labels, implement locally without committing until the user finishes manual testing, then—only on explicit user request—assist with git actions if asked. The user typically commits, pushes, and opens the PR themselves; once a PR URL exists, the agent must update Jira automatically (status transitions and activity via comments). If labels do not identify exactly one repo, the agent must ask the user every time. Use for Jira-linked work, keys (e.g. PROJ-123), URLs, or phrases like "จาก Jira", "งาน SD-", "เริ่มจาก task บน Jira".
- ▌ Code Simplification · testonohmSimplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
- ▌ Context Engineering · testonohmOptimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
- ▌ Security And Hardening · testonohmHardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.
- ▌ Frontend UI Engineering · testonohmBuilds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
- ▌ Spec Driven Development · testonohmCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
- ▌ Test Driven Development · testonohmDrives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
- ▌ API And Interface Design · testonohmGuides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
- ▌ Performance Optimization · testonohmOptimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
- ▌ Source Driven Development · testonohmGrounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
- ▌ Incremental Implementation · testonohmDelivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
- ▌ Planning And Task Breakdown · testonohmBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.