4,892 件 ・ 関連度順
概要と使いどころ
Use when designing or building any terminal user interface — choosing a layout paradigm, keybindings/interaction model, color system, data visualization, or motion. Framework-agnostic universal patterns that work with Ratatui, Ink, Textual, Bubbletea, or any TUI toolkit. For the repo's own pythinker-code TUI, use write-tui instead.
日本語の概要は準備中です。原文の説明を表示しています。
Update Pythinker Code CLI user documentation after meaningful code changes that affect product behavior or user experience.
日本語の概要は準備中です。原文の説明を表示しています。
Use when cutting, debugging, or verifying a pythinker-code (TSC monorepo) release — changesets flow, the ci release-packages version PR, release.yml anatomy, npm Trusted Publishing OIDC, native assets, brew tap, CDN redeploy, and their failure modes. Invoked by /release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating changesets in the pythinker-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Use after a release succeeds, when maintainers need to sync apps/pythinker-code/CHANGELOG.md into docs/release-notes/changelog.md, then open a PR on a dedicated branch.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI presentation generation systems. TRIGGERS - Use when user needs help with ai-presentation-maker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build experiment tracking systems for AI. TRIGGERS - Use when user needs help with ai-experiment-tracker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI compliance checking systems. TRIGGERS - Use when user needs help with ai-compliance-checker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Track changes and versions in AI systems. TRIGGERS - Use when user needs help with ai-changelog-tracker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI accessibility checking. TRIGGERS - Use when user needs help with ai-accessibility-checker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Design AP tracking with payment scheduling. TRIGGERS - Use when user needs help with accounts-payable-tracker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Design AR tracking with aging and collection processes. TRIGGERS - Use when user needs help with accounts-receivable-tracker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Pitfalls, examples, and edge cases for workers executing a Surogates subagent task. Loaded automatically when the dispatcher spawns a session bound to a Task (Session.task_id is set).
日本語の概要は準備中です。原文の説明を表示しています。
The Arbor executor workflow: clone the repo from the git bundle your brief hands you, implement and evaluate exactly ONE hypothesis with the file tools, then report structured results via worker_complete. Preloaded automatically on arbor-executor task workers. Never touch the held-out test split.
日本語の概要は準備中です。原文の説明を表示しています。
Use when installing or running the Inngest CLI and Dev Server for local development, local testing, serve endpoint debugging, Docker or Docker Compose setup, MCP configuration, self-hosted `inngest start`, or deployment workflow checks. Covers `inngest dev`, `inngest start`, auto-discovery, config files, environment variables, `@inngest/test`, local event sending, platform gotchas, and production/self-hosted server flags.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
MVP 开发专家团运维工程师（卜宕机）。负责自动化部署（CloudBase/Docker）、环境验证、健康检查、回滚策略、交付包组装。确保每次部署可验证、每次交付可追溯。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 4 部署任务时激活。不直接面向用户。
日本語の概要は準備中です。原文の説明を表示しています。
资金行为分析师（金向北）。擅长北向资金行为、机构持仓变动、基金重仓与拥挤度、资金共识方向判断。 在 A 股研究团队中由主理人调度，参与 Workflow 1 / Workflow 2 / Workflow 3 / Workflow 4 / Workflow 5 / Workflow 6。 擅长：北向资金净流入趋势、重点加仓/减仓方向、外资风格偏好、机构持仓变动（社保/险资/QFII 新进退出、十大股东变化）、基金重仓行业配置比例、拥挤度指标、三路资金共识图谱（北向×机构×公募×盘面主线交叉验证）、区分趋势性信号和短期交易噪音。
日本語の概要は準備中です。原文の説明を表示しています。
Shows you how to use Cowork's parallel workers to run multiple tasks at the same time instead of one after another — dramatically cutting the time on batch work. For processing large batches of files or research tasks, when running multiple independent analyses simultaneously, or during a performance optimization session. Use when the user says "speed up", "parallel workers", "batch task", "process multiple files", "why is cowork so slow", "faster", "do several things at once", or "can cowork multitask".
日本語の概要は準備中です。原文の説明を表示しています。
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap new 33GOD ecosystem agents with standardized configuration. Use when creating new agents, spawning workers, deploying Yi nodes, or when the user says "spin up an agent", "create a new agent", "deploy a new worker", or needs a new agent for a specific pipeline role. Handles workspace creation, config injection, skill installation, provider mirroring, channel binding, and 33GOD ecosystem onboarding (GOD Docs, Plane, Bloodbank, memory).
日本語の概要は準備中です。原文の説明を表示しています。
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `committer` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
日本語の概要は準備中です。原文の説明を表示しています。
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Defines the Code Change Loop, Test Writing Loop, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Includes bundled scripts for specialist-review (code review) and test-review-request (test audit) that delegate to Claude CLI. Use this skill when starting any implementation task.
日本語の概要は準備中です。原文の説明を表示しています。