536건 · 관련도순
Use when a project follows a structured operating model with: two work lanes (Domain, System), unresolved work tracked as Epic, bounded execution tracked as Ticket, role-based behavior (architect, runner), helper-backed SQLite workflow tables, inbox and outbox files as task and result bodies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search the web through Tavily with bounded depth, domains, dates, and result counts. Use when the user needs current information or source discovery and does not already have a specific URL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run Tavily's multi-source research workflow for comparisons, market analysis, literature-oriented exploration, or detailed cited reports. Use only when bounded search and extraction are insufficient.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover and filter URLs on a known website through Tavily without extracting every page. Use to locate a specific subpage, inspect site structure, or prepare a bounded map-then-extract workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow, 연구부터 논문까지, 연구 주제 설정부터 논문 완성까지, 논문 전체 워크플로.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Crawl and extract a bounded set of pages from one website through Tavily. Use for documentation downloads, site-section collection, or semantic multi-page extraction when map plus individual extract calls are insufficient.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up a bounded iterate-until-done run with the loop plugin's /loop command. Use when the user wants the same task retried or refined across several replies until a check passes, such as "keep going until the tests pass" or "do this up to 5 times".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a large, parallelizable goal into bounded work units, coordinate existing agent/worktree machinery, integrate, and verify. Explicit-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when independent bounded tasks benefit from delegation during implementation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says "create an endpoint", "expose this query as an API", "turn this insight into an endpoint", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design what an employer will have a candidate do during an Otameshi Tenshoku trial: turn a business problem into a bounded paid assignment or an unpaid learning visit, with scope, completion criteria, candidate hours, company staff hours, duration, compensation and change conditions, and check the planned cost against the budget. Use when a hiring manager, recruiter or small-business owner wants to decide what work to offer, how much time it takes, what it costs, or how to adjust a plan when materials are late or the scope grows; do not use to write the public listing (trial-listing-draft), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post, contact or contract on the user's behalf.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate DDD domain modeling sessions via EventStorming conversation and DML (Domain Modeling Language). Use whenever the user wants to model a business domain by discovering domain events, commands, aggregates, policies, read models, and bounded contexts through dialogue. Produces incrementally-built DML as the primary artifact, plus a Markdown session report. Also invoke for refining existing DML, mapping out a new feature's domain model, or when the user says "ドメインモデリングしたい", "イベントストーミング", "DDDで整理したい", "DMLを育てたい".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs differential expression on bulk RNA-seq count data with edgeR's negative-binomial GLM and quasi-likelihood F-test framework. Covers DGEList construction, filterByExpr, TMM/TMMwsp normalization, robust dispersion estimation, glmQLFit/glmQLFTest, TREAT for magnitude-bounded hypotheses, contrasts via no-intercept designs, voom and voomWithQualityWeights for heterogeneous samples, and the edgeR v4 bias-corrected APL changes. Use when running bulk DE with edgeR, choosing edgeR over DESeq2 (small n, transcript DE via catchSalmon, large samples), needing TREAT for a fold-change-threshold hypothesis, troubleshooting v3-to-v4 reproducibility, building paired or interaction designs, or handling library-quality heterogeneity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design authorized, bounded, reproducible security checks without turning scanner findings into penetration-test permission.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Delegate a bounded repository task to an allowlisted external coding CLI through the guarded Flow runner. Use for automatic provider selection or explicit Codex, OpenCode, Kimi, Gemini, or Kiro delegation that requires timeout handling and independent local review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.