rakovi4
28 verified skills56 total stars
task
Create a new task (bug or refactoring) with spec and progress tracking. Use when user wants to create a task or mentions /task command.
development2
align-design
Align frontend component styling to match HTML mockup pixel-for-pixel. Reads mockup CSS, compares with component, fixes all differences. Use when user wants to match a component to its mockup or mentions /align-design command.
development2
architecture
Facilitate architectural decisions during implementation. Use when the developer encounters a design choice with multiple viable approaches (data model, race condition handling, processing strategy, schema design) and needs structured discussion, trade-off analysis, and documentation. Triggers on /architecture or when a conversation reveals competing design options that need evaluation before coding continues.
development2
continue
Continue working on a story or task by reading progress.md, executing the next work unit, and updating progress. Use when user wants to resume story/task work or mentions /continue command.
tools2
design-preview
Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
testing2
design-review
Review frontend component for hardcoded mockup placeholder data after align-design. Flags emails, dates, prices, and other user-specific values that should be dynamic. Use when user mentions /design-review command.
development2
interview
Interactive interview to create interview.md for a story. Asks structured questions about scope, APIs, decisions, and constraints, then generates the handwritten-style context file. Use when user wants to create story specifics or mentions /interview command.
development2
mockups
Generate HTML interface mockups for user stories. Use when user wants to create UI mockups, prototypes, or mentions /mockups command.
development2
prompt-refactor
Scan a prompt file for layer violations and structural problems, then fix them. Use when user wants to clean up documentation files or mentions /prompt-refactor command.
development2
refactor
Refactor code using Martin Fowler's patterns. Improves readability, moves behavior closer to data, removes unnecessary abstractions.
development2
run-frontend
Start the frontend dev server. Use when user wants to start the frontend or mentions /run-frontend command.
development2
test-review
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.
testing2
test-usecase
Run use-case module tests quickly. Use when user wants to run use-case tests or mentions /test-usecase command.
testing2
cleanup-chrome
Kill orphaned chromedriver and headless Chrome processes left over from failed Selenium test runs. Use when Selenium tests mass-fail with Connection reset or TimeoutException, when the system feels sluggish during test runs, or when the user mentions /cleanup-chrome. Also use proactively before running frontend acceptance tests if previous runs were interrupted or stopped.
development2
api-spec
Generate OpenAPI specifications for story endpoints. Use when user wants to create API specs for a story or mentions /api-spec command.
development2
demo
Run a Selenium test in visible (non-headless) mode with slowdown so the user can watch it. Use when user wants to demo or visually watch a Selenium test or mentions /demo command.
testing2
doc
Document findings, research, or knowledge into ProductSpecification/ with proper cross-references. Use when the user wants to write up research results, create a reference doc, consolidate scattered knowledge, or mentions /doc command. Also triggers on "document this", "write this up", "let's capture what we learned", "create a reference for".
testing2
run-backend
Run the backend application. Use when user wants to start the backend server or mentions /run-backend command.
development2
prompt-update
Classify new content (rule, pattern, workflow step) and write it to the correct documentation layer. Use when user wants to add prompt documentation or mentions /prompt-update command.
documentation2
story
Generate story specifications from MVP stories list. Use when user wants to create detailed story documentation or mentions /story command.
testing2
stop-backend
Stop the running backend application. Use when user wants to stop the backend server or mentions /stop-backend command.
development2
test-coverage
Run tests with coverage and report uncovered lines/branches per class. Use when user wants to check test coverage, find untested code, identify coverage gaps, or mentions /test-coverage command. Also use after green phases to verify new code is well-covered.
development2
test-all
Run all tests - unit tests in parallel, then acceptance tests with backend. Use when user wants to run the full test suite or mentions /test-all command.
development2
test-adapter
Run adapter module tests. First argument is adapter name (matches directory under backend/adapters/). Use when user wants to run adapter tests or mentions /test-adapter command.
development2
test-acceptance
Run acceptance tests (backend API or frontend UI). Use when user wants to run E2E acceptance tests or mentions /test-acceptance command.
development2
test-spec
Generate BDD test specifications for story in 6 categories (API, UI, Load, Infrastructure, Security, Integration). Use when user wants to create test cases or mentions /test-spec command.
development2
test-frontend
Run frontend tests. Use when user wants to run frontend unit tests or mentions /test-frontend command.
development2
screenshot
Take screenshots of HTML mockups from any version. Use when user wants to capture mockups as PNG images, regenerate screenshots, or mentions /screenshot command.
development2