223건 · 관련도순
Assesses litigation outcome impact with settlement probability, damage range estimation, and stock price sensitivity analysis. Use when evaluating litigation catalysts, modeling legal outcomes, or analyzing litigation-driven opportunities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assesses spin-off equity with forced selling dynamics, orphaned security identification, and standalone valuation analysis. Use when evaluating spin-off investments, identifying forced-sell situations, or analyzing newly public entities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assesses conglomerate break-up activism with segment valuation, separation feasibility, and tax-free qualification analysis. Use when evaluating SOTP activism, analyzing break-up proposals, or modeling separation value.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates tender offer structures with premium analysis, proration risk, and conditional tender strategies. Use when analyzing tender offers, calculating tender economics, or evaluating proration scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates dual-class share structures with discount analysis, unification catalysts, and governance reform probability assessment. Use when analyzing share class spreads, evaluating unification likelihood, or assessing dual-class dynamics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates management buyouts and take-private proposals with fairness assessment, minority squeeze-out mechanics, and appraisal rights analysis. Use when analyzing going-private deals, evaluating MBO fairness, or assessing minority shareholder protections.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates insider purchase patterns with cluster buying identification, historical signal analysis, and conviction scoring. Use when analyzing insider buying, assessing management confidence signals, or tracking insider activity patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates proxy fight mechanics with shareholder base analysis, ISS/Glass Lewis recommendations, and vote probability modeling. Use when analyzing proxy contests, assessing vote outcomes, or evaluating director nomination campaigns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates Dutch auction mechanics with optimal pricing strategy, odd-lot proration, and shareholder base analysis. Use when analyzing Dutch auctions, modeling tender strategies, or evaluating self-tender economics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies governance-related catalysts with board refreshment, compensation reform, and shareholder proposal analysis. Use when analyzing governance catalysts, evaluating shareholder proposals, or assessing governance improvement potential.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates activist investor campaigns with thesis assessment, proposed changes, and likely outcome analysis. Use when analyzing activist situations, evaluating campaign theses, or assessing activist track records.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides architectural pattern knowledge for designing feature implementations including MVC, event-driven, microservices, and CQRS patterns. Use when designing system architecture or choosing implementation patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply collective intelligence coordination patterns — stigmergy, local rules, and quorum sensing — to organize distributed systems, teams, or workflows without centralized control. Covers signal design, agent autonomy boundaries, emergent behavior cultivation, and feedback loop tuning. Use when designing distributed systems without a coordination bottleneck, organizing teams that must self-coordinate, building event-driven architectures with shared state communication, or replacing fragile centralized orchestration with resilient emergent coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work with the @upstash/qstash TypeScript/JavaScript SDK, an HTTP-based message queue, task scheduler, and background job system for serverless and edge runtimes (Next.js, Vercel, Cloudflare Workers, Deno, Node.js). Use when publishing messages to HTTP endpoints or URL groups, running background jobs without a long-running worker process, scheduling with cron expressions, delaying messages, building FIFO queues with parallelism and flow control, configuring retries and callbacks, handling a dead letter queue (DLQ), deduplicating messages, fanning out to multiple endpoints, verifying QStash webhook signatures (Next.js App Router, Pages Router, and Edge Runtime), running a local QStash dev server, or migrating regions. Also use when the user asks for a serverless cron job, async task queue, job scheduler, delayed delivery, webhook delivery with retries, or event-driven messaging between services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement event-driven side effects that react to domain events
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate ScriptableObject-based systems including data containers, event channels, and runtime sets. Use when creating game data (weapons, enemies, items, abilities), cross-system events, or live object tracking. Triggers on requests like "create weapon data", "add an event system", "make a runtime set", "decouple these systems", "create item database", "add a damage event", "track active enemies", "create a config SO", "add game settings data", or any task involving ScriptableObject data containers, event-driven communication, or runtime object tracking. Reads ProjectConfig.yaml -> architecture_pattern to determine SO-first vs DI-first context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spring Modulith 2.0 implementation for bounded contexts in Spring Boot 4. Use when structuring application modules, implementing @ApplicationModuleListener for event-driven communication, testing with Scenario API, enforcing module boundaries, externalizing events to Kafka/AMQP, building a modular monolith, defining module dependencies, managing inter-module events, or organizing DDD modules as packages. Covers package-based module boundaries, named interfaces, event publication, and Scenario API testing. For architecture decisions, see domain-driven-design skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to select the right Salesforce integration pattern — from point-to-point to event-driven to hub-and-spoke — by applying the official Salesforce two-axis decision framework (integration type × timing) to a business integration scenario. Trigger keywords: integration pattern decision, choose integration approach, Salesforce integration architecture, when to use platform events vs API, integration type selection. NOT for implementation of any specific integration pattern (use domain-specific integration skills), MuleSoft architecture (use architect/mulesoft-anypoint-architecture), or middleware vendor selection. More triggers: integration decision record, Bulk API vs REST for a nightly load, external Id upsert, Named Credential vs Remote Site Setting, platform event vs CDC, who calls whom.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze demand forecasting systems — time-series decomposition (ARIMA, Prophet, ETS), seasonal and event-driven demand modeling, booking curve and pickup analysis, cancellation prediction, forecast accuracy metrics (MAPE, bias), and model retraining pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collection of AWS development skills covering CDK infrastructure as code, cost optimization, and serverless/event-driven architectures with integrated MCP servers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.