datamaker-kr
Organization시냅스 제품군 개발을 위한 공용 Claude Marketplace 입니다. 용도 및 목적 별 plugins 를 통해 claude plugins, agents, skills, commands 를 제공합니다.
Categories
Indexed Skills (37)
changelog-manager
Manages changelog entries following Keep a Changelog format with CalVer versioning. Analyzes changes and generates appropriate changelog descriptions.
commit-with-message
커밋 메시지 작성 가이드 (한글/영어). 커밋 생성 시 자동으로 활성화되어 규칙을 준수하도록 안내합니다.
docs-analyzer
Analyzes code changes and identifies documentation gaps. Scans git history, catalogs existing docs, and generates comprehensive analysis reports.
docs-bootstrapper
Bootstraps documentation structure for projects. Creates initial README, architecture docs, and API documentation with project-aware templates.
mermaid-expert
Specialized skill for generating Mermaid diagrams with light/dark mode compatible colors. Use when creating architectural diagrams, flowcharts, ER diagrams, or sequence diagrams.
tdd-workflow
Guides development following Kent Beck's Test-Driven Development and Tidy First principles. Use when implementing features or fixing bugs.
init-specs
Initialize spec documents (requirements, specs, plans) for a new task. Creates scaffolded markdown files in specs/ directory. Use when user wants to start a new task specification.
plan-with-requirements
Lite 파이프라인 — requirements.md에서 곧장 plans.md를 생성합니다. low 난이도 / 단순 작업에 사용. specs.md 단계를 건너뜁니다.
plan-with-specs
Read finalized specs and generate a detailed implementation plan. Updates the plans markdown with actionable steps. Use when user has reviewed specs and wants to generate an implementation plan.
specify-with-requirements
Read requirements markdown and generate detailed technical specifications. Analyzes requirements, clarifies ambiguities, and updates the specs document. Use when user has written requirements and wants to generate specs. Also handles lite→full pipeline escalation.
sync-to-jira
완성된 specs/plans 문서를 Jira 이슈로 push-back 합니다 (Markdown → ADF 자동 변환). Jira MCP가 가용한 환경에서만 동작합니다.
update-requirements
Update requirements and cascade changes to specs and plans. Accepts natural language change descriptions to modify the full spec chain. Use when user wants to add, remove, or modify requirements.
checklist-generation
Expertise in generating domain-specific quality checklists for specifications. Activates when user discusses quality validation or requirement testing. Trigger keywords: checklist, quality gate, requirement testing, validation, completeness check, review checklist
consistency-analysis
Expertise in detecting inconsistencies, gaps, and conflicts across specification documents. Activates when user asks about document quality or consistency. Trigger keywords: consistency, analysis, gap analysis, conflict detection, spec review, cross-reference, traceability
spec-authoring
Expertise in writing clear, testable specifications. Activates when user discusses requirements, features, user stories, or acceptance criteria. Trigger keywords: specification, requirements, user story, acceptance criteria, feature spec, functional requirement, non-functional requirement, spec.md
task-decomposition
Expertise in breaking down specifications into executable, dependency-ordered tasks. Activates when user discusses task planning, work breakdown, or implementation ordering. Trigger keywords: task decomposition, work breakdown, task list, dependency order, implementation tasks, tasks.md, T001, parallelizable
docs-manager
Orchestrates comprehensive documentation management by coordinating docs-analyzer, docs-bootstrapper, and mermaid-expert skills. Proactively monitors code changes and ensures documentation stays synchronized with the codebase.
planner
Expert planning specialist focused on creating comprehensive, actionable implementation plans. Analyzes requirements, decomposes complex features, identifies dependencies, and creates step-by-step execution strategies.
update-pr
Complete PR update workflow - updates both title and description with project-aware content. Orchestrates update-pr-title and update-pr-desc commands.
spec-manager
Orchestrates specification management workflow by coordinating init-specs, specify-with-requirements, plan-with-specs, plan-with-requirements, update-requirements, and sync-to-jira skills. Manages the full lifecycle of task specifications from requirements through implementation planning and Jira push-back.
jira-sync
CHANGELOG 기반 Jira 티켓 상태를 Git 브랜치 상태에 맞게 동기화하는 로직을 가이드합니다.
synapse-applications
Build a new Synapse App as an OCI image and publish it to the Datamaker registry so the workspace can install it via the App Store. Use when the user asks to create/scaffold a Synapse App, sub-app, plugin, iframe app, or embedded dashboard, or mentions synapse-app.yaml, /plugins registry, apiVersion synapse.datamaker.io/v1, or the iframe bridge. Supports React, Vue, Next.js, Nuxt 3, Gradio, Streamlit, Static HTML, Django, FastAPI (priority in that order).
synapse-export-workflow
Use when user mentions "export", "download annotations", "ground truth", "export project", "COCO format", "YOLO format", "Pascal VOC", "export assignments", "export tasks", "download labels".
synapse-action-development
Explains how to create Synapse plugin actions. Use when the user asks to "create an action", "write an action", uses "@action decorator", "BaseAction class", "function-based action", "class-based action", "Pydantic params", "ActionPipeline", "DataType", "input_type", "output_type", "semantic types", "YOLODataset", "ModelWeights", "pipeline chaining", or needs help with synapse plugin action development.
synapse-config-yaml-guide
Explains how to write Synapse plugin config.yaml files. Use when the user asks about "config.yaml", "plugin configuration", "action definition", "execution method", "runtime environment", or needs help with synapse plugin settings.
synapse-plugin-execution
Explains how to execute Synapse plugins programmatically. Use when the user mentions "run_plugin", "ExecutionMode", "LocalExecutor", "RayActorExecutor", "RayJobExecutor", "PluginDiscovery", "from_path", "from_module", or needs help with running plugins programmatically.
synapse-result-schemas
Explains result schema classes for Synapse plugin actions. Use when the user mentions "TrainResult", "InferenceResult", "ExportResult", "UploadResult", "WeightsResult", "MetricsResult", "result_model", "result schema", or needs help with action return type validation.
synapse-runtime-context-api
Explains how to use Synapse RuntimeContext API. Use when the user asks about "RuntimeContext", "ctx.", "logging", "progress tracking", "set_progress", "set_metrics", "log_message", "BaseStepContext", "TrainContext", "ExportContext", "UploadContext", "InferenceContext", "AddTaskDataContext", or needs help with synapse plugin context and logging.
synapse-specialized-actions
Explains specialized Synapse action classes for specific workflows. Use when the user mentions "BaseTrainAction", "BaseExportAction", "BaseUploadAction", "BaseInferenceAction", "BaseDeploymentAction", "AddTaskDataAction", "train action", "export action", "upload action", "inference action", "deployment action", "pre-annotation", "add_task_data", "autolog", "get_dataset", "create_model", or needs workflow-specific action development help.
synapse-step-workflow
Explains step-based workflow system for Synapse plugin actions. Use when the user mentions "BaseStep", "StepRegistry", "Orchestrator", "StepResult", "BaseStepContext", "step-based workflow", "workflow steps", "rollback", "progress_weight", or needs help with multi-step action development.
synapse-file-conversion
Use when source files need format conversion before upload. Triggers on: "convert", "tiff to png", "file format", "unsupported extension".
synapse-upload-workflow
Use when user mentions "upload", "data collection", "file specifications", "data units", "organize files", "map files to specs", "bulk upload", "s3 upload", "cloud storage", "multi-path", "excel metadata".
add-changelog-command
Run the `platform-dev-team-common:add-changelog` workflow from the original Claude slash command. Use when the user asks to add a changelog entry to CHANGELOG.md in the Unreleased section following Keep a Changelog format with CalVer versioning.
sync-jira-tickets-command
Run the `platform-dev-team-common:sync-jira-tickets` workflow from the original Claude slash command. Use when the user asks to 현재 프로젝트의 CHANGELOG.md에 있는 Jira 티켓들을 Git 브랜치 상태에 맞게 동기화합니다.
update-docs-command
Run the `platform-dev-team-common:update-docs` workflow from the original Claude slash command. Use when the user asks to manually triggers documentation analysis and updates. Scans repository for outdated documentation and generates Mermaid charts for architectural changes.
update-pr-desc-command
Run the `platform-dev-team-common:update-pr-desc` workflow from the original Claude slash command. Use when the user asks to updates PR description with comprehensive template compliance, mandatory Mermaid charts, and support for Korean/English. Auto-detects project type and adapts content accordingly.
update-pr-title-command
Run the `platform-dev-team-common:update-pr-title` workflow from the original Claude slash command. Use when the user asks to updates PR title with auto-generated description based on commits and changes. Supports Korean and English, preserves ticket IDs.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.