jampissarandev
Community@jampissarandev
jampissarandev provides 24 engineering discipline skills covering specification, test-driven development, debugging, code review, security hardening, CI/CD, observability, and production launch readiness.
Agent Skills by jampissarandev
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 using the red-green-refactor cycle for code changes and bug fixes.
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
Guides design of stable REST APIs, TypeScript contracts, and module boundaries.
ci-cd-and-automation
Configures CI/CD pipelines with quality gates, deployment strategies, and rollback workflows.
context-engineering
Structures rules files, specs, and source context for AI coding agents.
frontend-ui-engineering
Builds accessible, responsive React components following design system standards.
shipping-and-launch
Guides production deployments with pre-launch checklists, staged rollouts, monitoring, and rollback plans.
spec-driven-development
Writes structured specifications before coding through a gated specify-plan-tasks-implement 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, injection, XSS, SSRF, and LLM threats.
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 user intent through one-question-at-a-time interviews before planning or coding begins.
code-simplification
Refactors working code to reduce complexity while preserving exact behavior.
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 jampissarandev
FAQPage SchemaWhat tasks can I accomplish with jampissarandev's skills?▼
The 24 skills cover the full software delivery lifecycle: refining ideas, interviewing for requirements, writing specs, test-driven development, systematic debugging, code review, security hardening, performance optimization, CI/CD setup, observability instrumentation, deprecation management, and production launch preparation.
Who should use jampissarandev's skill collection?▼
Software engineers and coding practitioners who want disciplined development practices. The skills target people implementing features, fixing bugs, reviewing code, designing REST or GraphQL interfaces, hardening authentication and data handling, and shipping production releases with monitoring and rollback plans.
How do the skills get discovered and invoked during a session?▼
The using-agent-skills meta-skill governs discovery and invocation of all other skills at session start or when a task matches a skill's trigger conditions. Each skill declares explicit trigger phrases, such as 'ideate', 'interview me', or 'stress-test my plan', that activate it.
What prerequisites or dependencies do these skills require?▼
Most skills are self-contained methodology guides with no external dependencies. The exception is browser-testing-with-devtools, which requires the chrome-devtools MCP server to be configured so it can inspect the DOM, capture console errors, and analyze network requests in a real browser.
Do the skills cover production readiness and post-launch concerns?▼
Yes. shipping-and-launch provides pre-launch checklists, staged rollouts, and rollback strategies; observability-and-instrumentation adds logging, metrics, tracing, and alerting; performance-optimization addresses Core Web Vitals and bottlenecks; deprecation-and-migration handles sunsetting old systems safely.