Shai Roemi
Community@raishoemi
Shai Roemi publishes 24 engineering discipline skills covering the full software delivery lifecycle from specification and testing through deployment, observability, and deprecation.
Agent Skills by Shai Roemi
Showing 24 vetted skills indexed across 1 GitHub repositories.
idea-refine
Refines raw ideas into actionable one-pagers through structured divergent and convergent thinking.
debugging-and-error-recovery
Diagnose test failures, build errors, and runtime bugs through structured root-cause triage.
using-agent-skills
Discovers and routes tasks to phase-specific engineering workflow skills.
test-driven-development
Guides test-first development workflows using the red-green-refactor cycle for code changes.
planning-and-task-breakdown
Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.
incremental-implementation
Implements multi-file code changes in tested, committed vertical slices.
api-and-interface-design
Designs stable REST APIs, TypeScript interfaces, and module contracts with consistent error semantics.
ci-cd-and-automation
Configures GitHub Actions CI/CD pipelines with quality gates, deployment strategies, and rollback workflows.
context-engineering
Configures rules files and curates context layers for AI coding agents.
frontend-ui-engineering
Builds accessible, responsive React components following design system conventions.
shipping-and-launch
Guides production deployments with pre-launch checklists, staged rollouts, monitoring, and rollback plans.
spec-driven-development
Creates structured specifications before coding through a gated four-phase workflow.
code-review-and-quality
Reviews code changes across correctness, readability, architecture, security, and performance before merge.
security-and-hardening
Hardens web application code against OWASP vulnerabilities through threat modeling and defensive patterns.
deprecation-and-migration
Plans and executes deprecation of legacy systems with incremental migration patterns.
observability-and-instrumentation
Instruments production code with structured logs, metrics, traces, and symptom-based alerts.
interview-me
Extracts underlying user intent through one-question-at-a-time interviews before planning or coding.
code-simplification
Refactors code to reduce complexity while preserving exact behavior and project conventions.
doubt-driven-development
Subjects non-trivial decisions to adversarial fresh-context review before they stand.
source-driven-development
Implements framework code verified against official documentation with cited sources.
performance-optimization
Diagnose and fix frontend and backend performance bottlenecks using measurement-driven profiling workflows.
browser-testing-with-devtools
Tests and debugs web pages in real browsers using Chrome DevTools MCP.
git-workflow-and-versioning
Structures git commits, branching, and worktree workflows for disciplined version control.
documentation-and-adrs
Writes architecture decision records, API documentation, READMEs, and changelogs for software projects.
Frequently Asked Questions About Shai Roemi
FAQPage SchemaWhat tasks can I accomplish with Shai Roemi's skill collection?▼
The 24 skills cover the full delivery lifecycle: refining ideas, interviewing for intent, writing specs, test-driven development, systematic debugging, code review, API design, CI/CD setup, frontend UI building, performance optimization, security hardening, observability instrumentation, git versioning, documentation with ADRs, and deprecation planning.
Who are these skills designed for?▼
Software engineers and coding agents working across the development lifecycle. They serve developers writing features, reviewers assessing code before merge, and engineers handling production concerns like monitoring, staged rollouts, migrations, and vulnerability hardening on untrusted input or session management.
How do the skills get discovered and invoked at runtime?▼
The using-agent-skills meta-skill governs discovery and invocation of all other skills at session start or when a task matches. The context-engineering skill configures rules files and project context, while individual skills trigger on natural phrases like 'ideate', 'stress-test my plan', or 'interview me'.
What prerequisites or dependencies do these skills require?▼
Most skills are methodology-driven with no external dependencies. The browser-testing-with-devtools skill explicitly requires the chrome-devtools MCP server to be configured for DOM inspection, console error capture, network analysis, and performance profiling in real browsers.
How do the skills ensure code correctness before shipping?▼
Test-driven-development proves behavior with tests, doubt-driven-development applies adversarial fresh-context review to high-stakes decisions, source-driven-development grounds implementation in official documentation, and code-review-and-quality assesses changes across multiple axes before merging.