144건 · 관련도순
Planning a coordinated set of items toward a goal, an event, a trip, or a project, where the request only comes together as several purchases with a structure between them, and later changes to a plan you have presented. Not needed when the customer wants a single item, however carefully chosen.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operate a selective workspace for complex reasoning, long tasks, repository engineering, coordinated agents, and authorized security analysis. Use when work requires durable state, evidence, cross-file consistency, or recovery; keep direct answers lightweight.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, `window.grida`, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs, and CDP / Playwright verification. Use for `desktop/`, `editor/app/desktop/**`, `editor/scaffolds/desktop/**`, `editor/lib/desktop/**`, `/desktop/*` CSP, GRIDA-SEC-004, and deciding whether linked-package or hosted-renderer changes require a native Desktop version bump or coordinated release. For implementing daemon/agent-tenant core behavior, use `agent-system` as well.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security (Art. 21(2)(d); coordinated risk assessments Art. 22), gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis. Also covers Commission Implementing Regulation (EU) 2024/2690, the technical/methodological sub-requirements for Art. 21(2) and the significant-incident thresholds binding on DNS/cloud/data-centre/MSP/MSSP/trust-service and other digital entities. Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences between essential and important entities, and cross-border coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security (Art. 21(2)(d); coordinated risk assessments Art. 22), gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis. Also covers Commission Implementing Regulation (EU) 2024/2690, the technical/methodological sub-requirements for Art. 21(2) and the significant-incident thresholds binding on DNS/cloud/data-centre/MSP/MSSP/trust-service and other digital entities. Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences between essential and important entities, and cross-border coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full lifecycle team skill — plan, develop, test, review in one coordinated session. Role-based architecture with coordinator-driven beat model. Triggers on "team lifecycle v4".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates comprehensive dashboard and analytics interfaces that combine data visualization, KPI cards, real-time updates, and interactive layouts. Use this skill when building business intelligence dashboards, monitoring systems, executive reports, or any interface that requires multiple coordinated data displays with filters, metrics, and visualizations working together.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the BZD mathematical-modeling Skills across problem reading, idea generation, model selection, paper drafting, section checks, final format/AIGC audits and judge-style scoring. Use when a user wants one entry point, an end-to-end competition workflow, the next appropriate Skill, or coordinated processing of a problem and paper.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Social media monitoring, narrative tracking, and OSINT. Use when tracking viral spread, coordinated campaigns, or account vetting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinated wallet cluster detection, wash trading identification, and fake activity analysis for Solana tokens
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate multiple AI agents for construction workflows: estimator, scheduler, document, QA and safety agents coordinated by a supervisor agent, with human checkpoints. Use when automating end-to-end project processes with agentic AI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vendor breach notification cascade management per GDPR Article 33(2). Covers processor-to-controller notification without undue delay, escalation paths, coordinated multi-party breach response, liability allocation, and regulatory notification coordination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages coordinated breach notification across multiple legal jurisdictions including EU member states (72-hour GDPR deadline), US state breach notification laws (varying timelines from 30 to 90 days), and other international regimes. Covers conflict resolution when notification timelines differ, lead supervisory authority determination, and parallel notification execution. Keywords: multi-jurisdiction, cross-border breach, notification coordination, GDPR, US state laws, international breach notification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.