analyze-code
|
assign-task
|
auto-validate
|
check-service-status
|
check-team-codex
Validate code against Team Codex standards. Use when (1) before creating commits, (2) during verification phase, (3) quality gate enforcement.
circuit-breaker
|
close-sprint
|
create-command
Create SEMO slash commands following Claude Code conventions. Use when (1) need to add new /SEMO:command, (2) creating interactive workflows triggered by slash commands, (3) packaging command-based operations.
create-decision-log
|
create-event-schema
|
create-feedback-issue
|
create-impl-plan
|
create-meeting-minutes
|
create-sprint
|
debug-service
|
deploy-service
|
design-handoff
Generate design-to-development handoff documents. Use when (1) preparing designs for developers, (2) documenting component specifications, (3) creating style guides, (4) bridging design and code. Creates comprehensive handoff documents.
design-tests
|
design-user-flow
|
e2e-test
|
estimate-epic-timeline
|
explore-approach
Prototype and explore technical approaches. Use when (1) multiple valid technical approaches exist, (2) performance characteristics unknown, (3) implementation path unclear, (4) need evidence-based technical recommendation.
fast-track
경미한 수정사항 빠른 처리 및 사후 이슈 생성. Use when (1) 오타/문구 수정, (2) 스타일 미세조정, (3) 버그 핫픽스, (4) 코드 정리 (3파일 이하, 30분 이내).
fetch-supabase-example
Fetch reference implementations from core-supabase repository. Use when (1) implementing Repository layer with Supabase, (2) need RPC function usage patterns, (3) checking correct parameter structures and type assertions, (4) verifying Supabase integration patterns.
fetch-team-context
Fetch Semicolon team standards from docs wiki. Use when (1) providing workflow or process advice, (2) recommending DevOps strategies, (3) referencing team conventions for decision-making, (4) checking team standards compliance.
frontend-design
차별화된 프로덕션 수준의 프론트엔드 UI 설계 및 구현. Use when (1) UI/UX 디자인 필요, (2) 컴포넌트 디자인, (3) 화면 설계 및 구현, (4) Design Thinking 기반 프론트엔드 개발.
generate-mockup
Generate UI mockups using Magic MCP (21st.dev). Use when (1) creating new UI components, (2) prototyping interfaces, (3) building design system components.
generate-spec
|
git-workflow
|
manage-principles
Manage and update project Constitution. Use when (1) Constitution violation detected during implementation, (2) proposing new architectural principle, (3) templates need sync after Constitution update, (4) reviewing project architecture rules.
migrate-db
|
notify-slack
|
persist-context
|
production-gate
|
project-board
GitHub Project 보드 이슈 연동 및 상태 관리. Use when (1) 이슈 생성 후 프로젝트 보드 연동, (2) 태스크 완료 후 상태 변경.
project-kickoff
Interactive project creation from cm-template. Use when (1) user requests new service creation, (2) creating new cm-* project, (3) need guided wizard for project configuration, (4) generating ready-to-copy project in implement-dist/.
project-status
|
qa-test
|
quality-gate
|
release-manager
|
request-test
|
review-task
|
rollback-service
서비스를 이전 버전으로 롤백. Use when (1) 롤백 요청, (2) 이전 버전 복원, (3) /SEMO:rollback 커맨드.
routing-map
|
run-code-review
|
run-tests
|
scaffold-domain
Bootstrap DDD 4-layer domain structure. Use when (1) starting new domain implementation, (2) during v0.1.x PROJECT phase, (3) need to create repositories/api-clients/hooks/components with __tests__ and index.ts exports.
semo-architecture-checker
|
semo-help
|
setup-environment
|
Page 1560 of 1641 · 82007 results