514 个 · 按相关度排序
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review,
中文简介正在准备中。当前显示原文说明。
Stand up or rebuild an AWS Shifter tenant end to end (teardown, bootstrap, secrets, image bakes, deploy via the real deploy.yml dispatch, health check, base-range smoke, and a POLARIS range walkthrough). AWS only. Use when asked to rebuild, redeploy, or stand up an AWS tenant such as proof or aws-dev from a clean state.
中文简介正在准备中。当前显示原文说明。
Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.
中文简介正在准备中。当前显示原文说明。
Dispatch to the right problem-solving technique based on how you're stuck
中文简介正在准备中。当前显示原文说明。
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
中文简介正在准备中。当前显示原文说明。
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
中文简介正在准备中。当前显示原文说明。
Use when executing implementation plans with independent tasks in the current session — trigger phrases "execute the plan", "independent tasks", "parallel tasks", "subagents for the plan","split the plan into subagents". Dispatches a fresh subagent per task with two-stage review after each: spec compliance first, then code quality.
中文简介正在准备中。当前显示原文说明。
Use when running the autonomous multi-agent build pipeline after /bdbrainstorm or /grill-me, when the user types /startcycle-graph or "run a startcycle", or when a task needs durable state, a review repair loop and an automated quality gate. Routes to the startcycle-dispatch Dynamic Workflow, which reads production_artifacts/state.json and invokes Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, and Shipping in turn per .agents/graph.md's edge table — the agents never invoke each other.
中文简介正在准备中。当前显示原文说明。
Linear multi-agent build pipeline with file hand-offs in production_artifacts/, run after /bdbrainstorm or /grill-me. This is the linear variant — no state.json, no repair loop, no dispatcher graph — distinct from startcycle-graph, which adds durable state and automated escalation. Use when an approved plan should be built, when the user types /startcycle or "run a startcycle", or when you pick a startcycle variant from the situation yourself (no user prompt needed).
中文简介正在准备中。当前显示原文说明。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
中文简介正在准备中。当前显示原文说明。
Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).
中文简介正在准备中。当前显示原文说明。
Use when deciding WHERE to do work on Syntropic137 itself - "run this through Syntropic", "dispatch a workflow", "should this go in a workspace or local", "kick off a run on the Mini", "dogfood this", "build Syntropic inside Syntropic", "why did the agent's push fail", "can an agent run our QA", "the execution says completed but nothing shipped". Covers what a workspace agent can and cannot do, why `.github/workflows` pushes must come from the local machine, how to write a task prompt that does not repeat a known failure, and how to verify a run actually delivered. Do NOT use for PR/release mechanics (see `devops`), for using the `syn` CLI as an end user (see the syntropic137 plugin skills), or for authoring workflow YAML.
中文简介正在准备中。当前显示原文说明。
Use when: Router bridges your team and the remote team across Telegram. Classifies inbound messages from the remote agent, dispatches Builder or Tester as subagents, composes replies, and posts outbound state-change notifications.
中文简介正在准备中。当前显示原文说明。
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.
中文简介正在准备中。当前显示原文说明。
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
中文简介正在准备中。当前显示原文说明。
Bootstrap a complete .github/workflows/ set for a new project: CI (build/test/lint), CD (workflow_dispatch with env choice + OIDC + ECR), security-scan (gitleaks + dependency scan + CodeQL), and optional database-migration. Use this skill when the user wants to add GitHub Actions CI/CD to a project that does not already have it, or when they want to add missing workflows alongside existing ones.
中文简介正在准备中。当前显示原文说明。
5W1H Decision Framework Tool. Use for: (1) Systematic decision-making before creating todos, (2) Preventing duplicate implementation, (3) Detecting avoidance behavior, (4) Ensuring agile refactor compliance with executor/dispatcher separation
中文简介正在准备中。当前显示原文说明。
Use when independent tasks benefit from parallel work without shared state or sequential dependencies
中文简介正在准备中。当前显示原文说明。
Run a project's GitHub Issues through Orca Workers from a coordinating session in the project's Hub folder. The Orchestrator reads Issues, claims one, dispatches an Orca Task into a fresh worktree of the target repo, supervises until worker_done, and writes the outcome back to the Issue — it never edits code itself. Use when the user says "take
中文简介正在准备中。当前显示原文说明。
Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty / 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic. TRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange / wrong / off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A/A test showing significance, or reports surprises after mid-run edits. DO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).
中文简介正在准备中。当前显示原文说明。
Orchestrate the full ToolUniverse self-improvement cycle: discover APIs, create tools, test with researcher personas, fix issues, optimize skills, and push via git. References and dispatches to all other devtu skills. Use when asked to: run the self-improvement loop, do a debug/test round, expand tool coverage, improve tool quality, or evolve ToolUniverse.
中文简介正在准备中。当前显示原文说明。
Windows アプリ開発 (Win32 / WPF / WinForms 相互運用) の相互運用・近代化。 Win32 API (CreateWindowExW, WNDPROC, メッセージループ), COM (IUnknown, CoCreateInstance, ComPtr), CsWin32, windows-rs, C++/WinRT (winrt::com_ptr, IAsyncOperation, IDL, ABI 相互運用), C#/WinRT (cswinrt, ComWrappers, AOT/trimming, WindowNative), XAML Islands (DesktopWindowXamlSource, DesktopChildSiteBridge, WindowsXamlManager), HwndHost, HwndSource, WindowsFormsHost, ElementHost, UWP から Windows App SDK / WinUI 3 への移行 (namespace mapping, AppWindow, DispatcherQueue, .NET Upgrade Assistant)、 移行判断 (upgrade / modernize / migrate)、WinForms → WinUI 3 パターン対応、GitHub Copilot upgrade。
中文简介正在准备中。当前显示原文说明。
Android アプリ開発 (Kotlin) の画面遷移・Navigation リファレンス。 Jetpack Compose, androidx。Navigation 3 (stable, NavDisplay, NavKey, ResultEventBus, DeepLinkMatcher)、 Navigation Compose (NavHost, composable, 型安全ルート)、 Fragment ナビゲーション (NavHostFragment, Safe Args)、ディープリンク, App Links, assetlinks.json、 予測型戻る (OnBackPressedDispatcher)。
中文简介正在准备中。当前显示原文说明。
Rory Sutherland's 'psycho-logic' approach to marketing, product, and business problems — solve the human perception, not just the engineering or economic metric. Use when the obvious 'logical' fix is expensive, slow, or already done by every competitor; when the user asks 'how do we make people want X', 'the product/price/funnel is fine but nobody converts', 'how do we stand out', 'is there a cheaper way to fix this', or mentions behavioral economics, nudges, irrational behavior, perception, or 'it doesn't make sense but it works'. This is the ROUTER skill: it diagnoses the problem in human terms, then dispatches to reframing, costly-signaling, counterintuitive-tests, or experience-design. Inspired by Rory Sutherland's book *Alchemy*. 日本語の相談（「商品はいいのに売れない」「値下げしかない？」「競合と差別化できない」）にも使う。中文咨询（“产品很好却卖不动”“只能降价吗？”“无法差异化”）也适用。For a catalogue of individual biases, use marketing-psychology (separate plugin) instead.
中文简介正在准备中。当前显示原文说明。