just-vibeThe command library
There’s a workflow
for that.
218 workflows, 3 aliases, and room for all your context. Find the right starting point.
How to use a command/orient
Identify stack, structure, conventions, and the actual commands, marked verified or discovered
/explain
Explain code or behavior at the requested depth
/reprompt
Improve a prompt while preserving intent and incorporating relevant available skills
/teach
Teach a programming topic or the concepts needed to understand and implement a just-vibe workflow.
/teach-test
Quiz the user on a topic or workflow through native multiple-choice question dialogs, with feedback and adaptive practice.
/trace
Follow a request, event, or data value through the system
/map
Map module and package imports inside a repository, including cycles and dynamic edges
/research
Investigate a technical question with sources and a recommendation
/compare
Compare specific implementation approaches and their tradeoffs
/brainstorm
Generate distinct approaches and explain their tradeoffs
/spec
Produce requirements, acceptance criteria, and edge cases
/plan
Inspect the project and produce a concrete implementation plan
/scope
Separate the essential release from optional work
/challenge
Identify weak assumptions, complexity, and failure cases
/tasks
Convert a brief or plan into ordered, verifiable tasks
/build
Implement a feature through appropriate verification
/fix
Reproduce a bug, identify its cause, and verify the fix
/debug
Investigate and explain a failure before changing code
/refactor
Improve structure while preserving behavior
/integrate
Connect an API, library, or external service
/migrate
Plan and apply a version, schema, or implementation migration
/automate
Turn a repetitive process into a script or workflow
/cleanup
Remove verified dead code and unnecessary complexity
/design
Develop a visual direction and implement the requested interface
/polish
Refine hierarchy, spacing, typography, and interaction details
/responsive
Fix layouts across screen sizes and input methods
/a11y
Inspect semantics, keyboard access, focus, contrast, and announcements
/match
Compare an implementation against a visual reference and close gaps
/copy
Improve interface wording and product messaging
/review
Review a change, selected files, or an entire repository for actionable defects
/test
Add meaningful coverage for specified behavior
/verify
Run relevant checks and report supporting evidence
/security
Examine concrete security risks in a defined scope
/perf
Measure a performance problem and improve its cause
/repro
Create a minimal, reliable reproduction of a problem
/coverage
Identify important untested behaviors and prioritize them
/pr
Prepare a focused diff summary, PR description, and validation notes
/release
Prepare release notes and readiness checks
/ci
Diagnose or improve continuous integration
/docs
Create or update documentation from verified behavior
/deps
Assess dependency updates and compatibility
/deploy
Prepare or perform deployment within the requested authorization
/checkpoint
Save progress, evidence, and unresolved work
/undo
Reverse a recorded local task while preserving unrelated changes
/handoff
Write a self-contained brief for another session or collaborator
/resume
Read a handoff, verify current state, and continue
/remember
Save project instructions, inspect their loading, and make explicit rules checkable
/learn
Extract a reusable lesson from completed work for review
/skill
Create or improve a workflow skill
/doctor
Diagnose installation and configuration problems
/help
Find the right command and show examples
/tools
List and search commands and integrations, showing availability and prerequisites
/auto
Select and apply the relevant engineering workflows from an ordinary request
/do
Use the goal and project context to select, execute, and verify appropriate workflows
/arch-map
Map deployed services, data stores, external providers and their runtime relationships
/arch-boundaries
Find misplaced responsibilities, dependency cycles, and leaking abstractions
/arch-feature
Design where a feature belongs within the existing architecture
/arch-contracts
Define interfaces and contracts between components or services
/arch-event-flow
Design event delivery, retries, ordering, and failure handling
/arch-tenancy
Evaluate tenant isolation across authentication, storage, queries, and jobs
/arch-scale
Identify bottlenecks for a specified workload and growth scenario
/arch-modernize
Plan an incremental transition to a target architecture
/decide
Recommend an option against explicit requirements
/decision-matrix
Compare options using weighted criteria and explain the weights
/decision-adr
Write a decision record with alternatives and consequences
/decision-premortem
Assume a proposal failed and identify plausible causes
/decision-reversible
Separate reversible choices from expensive commitments
/decision-buy-build
Compare building, buying, and integrating a solution
/decision-spike
Design or run a bounded experiment to resolve uncertainty
/decision-revisit
Reassess a decision using new constraints or evidence
/git-status
Explain branches, staged changes, unstaged changes, and repository state
/git-diff
Summarize changes by behavior and identify unrelated edits
/git-commit
Prepare coherent commits with accurate messages and deliberate staging
/git-split
Divide a mixed change into understandable commits
/git-conflicts
Resolve conflicts while preserving the intent of both changes
/git-bisect
Locate a regression with a reproducible pass/fail check
/git-worktree
Create or manage isolated working directories
/git-recover
Investigate reflog and history to recover lost work
/github-triage
Classify issues, identify duplicates, and suggest priorities
/github-issue
Turn a report or request into an actionable issue draft
/github-pr
Prepare or create a PR with scope, evidence, and issue links
/github-review
Review a PR using its discussion, changes, and checks
/github-address-review
Implement actionable review changes and explain resolutions
/github-fix-ci
Diagnose failing Actions jobs and verify repairs
/github-actions
Improve workflows, caching, permissions, and job structure
/github-release
Prepare a release from merged changes, tags, and issues
/vercel-audit
Inspect project configuration, build settings, and deployment assumptions
/vercel-build-fix
Reproduce and repair failed deployment builds
/vercel-env
Compare required variable names and scopes without exposing values
/vercel-preview
Prepare and validate a branch or PR preview deployment
/vercel-runtime
Investigate function errors, timeouts, and runtime differences
/vercel-routing
Diagnose redirects, rewrites, headers, domains, and route behavior
/vercel-performance
Investigate slow routes using available measurements and logs
/vercel-release-check
Verify a deployment and prepare promotion or rollback steps
/vite-setup
Configure Vite for the framework and project requirements
/vite-config
Audit aliases, plugins, build options, and environment handling
/vite-hmr
Diagnose broken, slow, or inconsistent hot-module updates
/vite-env
Check environment loading and exposure of server-only values
/vite-bundle
Analyze bundle composition and measured size reductions
/vite-chunks
Investigate loading boundaries, duplicated modules, and chunks
/vite-assets
Fix asset paths, public files, base paths, and deployment paths
/vite-upgrade
Upgrade Vite and plugins with compatibility and build checks
/react-audit
Review components, hooks, state ownership, and behavioral risks
/react-rerenders
Measure unnecessary rendering and identify its causes
/react-effects
Investigate effect loops, stale closures, and missing cleanup
/react-state
Simplify state ownership, derived state, and synchronization
/react-component
Build a component with its states, API, and accessibility
/react-forms
Implement validation, submission, errors, and pending states
/react-async
Fix loading races, cancellation, stale responses, and async behavior
/react-hydration
Diagnose server/client rendering mismatches where applicable
/ui-audit
Inspect hierarchy, consistency, usability, and visual clarity
/ui-system
Establish typography, spacing, colors, tokens, and component conventions
/ui-states
Add loading, empty, error, partial-data, disabled, and success states
/ui-responsive
Fix layouts across screen sizes and input methods
/ui-accessibility
Inspect semantics, keyboard access, focus, contrast, and announcements
/ui-motion
Add purposeful transitions with reduced-motion behavior
/ui-visual-diff
Compare screenshots against an accepted reference
/ui-flow
Improve a complete user journey, including error recovery
/backend-service
Implement a service with clear boundaries and validation
/backend-auth
Build or audit authentication and session behavior
/backend-permissions
Define and test authorization for roles, resources, and ownership
/backend-jobs
Implement background processing, scheduling, and recovery
/backend-idempotency
Prevent duplicate effects from retries and repeated requests
/backend-concurrency
Investigate races, locking, and competing updates
/backend-cache
Design cache keys, invalidation, expiration, and fallback
/backend-resilience
Add appropriate timeouts, bounded retries, and failure handling
/api-design
Define endpoints, resources, validation, and response contracts
/api-openapi
Create or reconcile OpenAPI documentation with implementation
/api-breaking
Identify backward-incompatible API changes
/api-contract-test
Verify provider and consumer expectations
/api-errors
Standardize useful error responses and propagation
/api-pagination
Design stable pagination, filtering, and sorting
/api-webhooks
Implement signatures, retries, replay handling, and delivery tracking
/api-client
Build a typed client with authentication and error handling
/db-schema
Design or review tables, relationships, constraints, and types
/db-migrate
Create migrations with compatibility and rollback considerations
/db-query
Write or repair queries against the actual schema
/db-explain
Interpret query plans and identify expensive operations
/db-index
Recommend indexes based on queries, write costs, and measurements
/db-integrity
Find orphaned records, invalid relationships, and missing constraints
/db-locks
Investigate blocking, deadlocks, long transactions, and contention
/db-access
Audit roles, tenant filtering, and row-level policies where supported
/data-profile
Summarize distributions, missingness, duplicates, and suspicious values
/data-contract
Define schema, semantics, freshness, and quality constraints
/data-pipeline
Build ingestion or transformation with observable failures
/data-incremental
Implement checkpoints, deduplication, and incremental processing
/data-backfill
Plan or run resumable historical-data backfills
/data-reconcile
Compare source and destination records and explain discrepancies
/data-lineage
Trace field origins and transformations
/data-quality
Check freshness, completeness, validity, and consistency
/ml-frame
Define target, prediction moment, unit of analysis, and objective
/ml-dataset
Audit whether data can support the modeling task
/ml-labels
Inspect label definitions, noise, disagreement, and missing outcomes
/ml-split
Design splits respecting time, groups, entities, and dependencies
/ml-leakage
Find target leakage, temporal leakage, and split contamination
/ml-features
Design features available at prediction time and test usefulness
/ml-imbalance
Evaluate sampling, weighting, metrics, and thresholds for rare outcomes
/ml-dataset-version
Record dataset identity, transformations, and provenance
/ml-baseline
Establish simple, reproducible baselines
/ml-train
Implement training with checkpoints and recorded configuration
/ml-debug-training
Investigate exploding loss, unstable gradients, NaNs, or failure to learn
/ml-tune
Design a bounded hyperparameter search with a fixed evaluation protocol
/ml-ablation
Measure contributions of features or model components
/ml-experiments
Compare runs and check that data and evaluation conditions match
/ml-reproduce
Reproduce a result from code, data, and configuration
/ml-training-cost
Profile training time, memory, and resource bottlenecks
/ml-evaluate
Evaluate using task-appropriate metrics and baselines
/ml-error-analysis
Group failures into actionable patterns and examples
/ml-slices
Compare meaningful cohorts or operating conditions
/ml-calibrate
Assess predicted probabilities against observed outcomes
/ml-threshold
Choose thresholds against explicit costs or capacity limits
/ml-robustness
Test missing inputs, noise, distribution changes, and boundaries
/ml-explain
Investigate behavior with appropriate explanation methods and limits
/ml-report
Document data, results, limitations, and intended use
/ml-package
Package preprocessing, artifacts, dependencies, and interfaces
/ml-serving
Implement online inference with validation and observable errors
/ml-batch
Build resumable batch inference and output tracking
/ml-parity
Check training preprocessing against production inference
/ml-inference-perf
Measure latency, throughput, memory, and optimization tradeoffs
/ml-drift
Design checks for input or prediction-distribution changes
/ml-monitor
Define operational and model-quality monitoring, including delayed labels
/ml-rollout
Prepare shadow, canary or staged rollout of a model version with rollback criteria
/llm-evals
Build representative evaluation cases and scoring criteria
/llm-prompt
Improve prompts against measured failures and explicit requirements
/llm-structured
Implement structured outputs, validation, and recovery
/llm-rag
Design or audit ingestion, retrieval, grounding, and generation
/llm-retrieval
Evaluate chunking, ranking, filters, and retrieval recall separately
/llm-tools
Design tool schemas, execution contracts, and failure handling
/llm-injection
Test handling of hostile instructions in untrusted content
/llm-cost
Measure token use, latency, caching opportunities, and routing tradeoffs
/test-unit
Test isolated behaviors and boundaries
/test-integration
Verify real component and dependency interactions
/test-e2e
Exercise complete user journeys and recovery
/test-regression
Turn a confirmed bug into a lasting behavioral check
/test-flaky
Repair nondeterminism using repeated evidence
/test-fixtures
Create representative, maintainable test data
/test-load
Execute bounded workloads against authorized environments
/test-property
Check invariants across generated inputs and edge cases
/security-threat-model
Identify assets, trust boundaries, attack paths, and mitigations
/security-authz
Test access decisions and cross-user or cross-tenant exposure
/security-secrets
Locate exposed credentials without printing secret values
/security-inputs
Audit validation and injection risks at input boundaries
/security-uploads
Review file validation, storage, processing, and download access
/security-dependencies
Assess findings against actual application exposure
/security-config
Review application, container, and deployment configuration
/security-fix
Implement and verify remediation for an identified vulnerability
/ops-incident
Organize symptoms, evidence, impact, hypotheses, and immediate actions
/ops-logs
Correlate available logs around a specific failure
/ops-observability
Add useful logs, metrics, and traces to unclear execution paths
/ops-alerts
Design actionable alerts with ownership and response guidance
/ops-runbook
Write operational procedures from verified commands and behavior
/ops-container
Diagnose container builds, runtime failures, and configuration differences
/ops-restore
Prepare or validate backup restoration in an appropriate environment
/ops-postmortem
Produce evidence-based timelines and concrete follow-up work
/setup
Install, update, or remove just-vibe through native host plugin management.
/profiles
Browse engineering role profiles and compare their priorities, boundaries and verification
/profile
Set, inspect, automatically select or clear task-scoped engineering profiles
/goal
Create and pursue a persistent objective with completion criteria, progress, blockers and evidence
/orchestrate
Coordinate a feature, fix, refactor or MVP through scoped phases and reviewed dependent assignments
/plan-review
Review a concrete plan or artifact in a private browser canvas with annotations and version-bound feedback
/agent-qa
Verify requested web-app outcomes through browser assertions, screenshots and bounded retests
No matches this time.
Try a broader term or clear the filters to explore everything.