6,194 件 ・ 関連度順
概要と使いどころ
Start, watch, and restart a local stack of app processes together instead of juggling many terminals and ad hoc shell loops.
日本語の概要は準備中です。原文の説明を表示しています。
Resolves AWS SDK v3 client commands and service endpoint signatures using @aws-sdk/client-* packages. Maps IAM permission requirements to specific API calls with request/response type definitions.
日本語の概要は準備中です。原文の説明を表示しています。
Operate Lark and Feishu work objects from one agent-ready CLI instead of stitching together separate APIs and browser flows.
日本語の概要は準備中です。原文の説明を表示しています。
AppFlowy brings documents, projects, wikis, and AI-assisted collaboration into a self-hosted or desktop-friendly workspace. This skill helps agents work from the real AppFlowy project, docs, and deployment methods when users need an open source Notion-style environment with local control.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments Anthropic API calls to log token usage, latency, and cost per request using the Anthropic TypeScript SDK. Wraps the anthropic.messages.create method to capture usage.input_tokens, usage.output_tokens, and timing from the API response. Writes structured logs to CloudWatch Logs via the AWS SDK v3 CloudWatchLogsClient.
日本語の概要は準備中です。原文の説明を表示しています。
Use Bats-core when an agent needs to turn fragile shell scripts or command-line workflows into something it can verify repeatedly after edits. The agent writes focused Bash tests for success paths, failure paths, and output contracts, then runs them locally or in CI before a refactor, release, or incident fix goes out.
日本語の概要は準備中です。原文の説明を表示しています。
Decide what to borrow, adapt, or write before building something. Use when the user describes an app, tool, CLI, or feature they want to build and needs to know which parts already exist as open-source GitHub repos (BORROW), which are worth reading and adapting (KITBASH), and which to just write (WRITE). Every repository named is checked against the live GitHub API, so invented ones never reach the user.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".
日本語の概要は準備中です。原文の説明を表示しています。
Expert sales strategy and operations guidance for B2B SaaS companies. Use when designing sales processes, implementing qualification frameworks (MEDDIC, BANT, SPICED), territory planning, forecasting, quota setting, compensation design, or optimizing pipeline velocity. Covers sales methodology, org structure, tech stack selection, win rate analysis, and deal acceleration strategies.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 5: Prove. Success validation against Phase R baseline metrics, test log review, and AI justification validation. Use after deployment. Triggers on "prove", "phase 5", "validate", "did it work", "success criteria", "measure results", or after go-live.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 1: Clarify. Problem definition, eliciting, painkiller test, buy vs build, AI justification gate, Go/No-Go. Use at the start of any AI implementation project. Triggers on "clarify", "phase 1", "start discovery", "define the problem", "what problem are we solving", or at the beginning of a new client engagement.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 2: Results. Outcome alignment, stakeholder register, baseline measurement, success metrics, tradeoff negotiation. Use after problem definition is complete. Triggers on "results", "phase 2", "define success", "success metrics", "what does done look like", or after Phase C exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
日本語の概要は準備中です。原文の説明を表示しています。
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.
日本語の概要は準備中です。原文の説明を表示しています。
Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.
日本語の概要は準備中です。原文の説明を表示しています。
Define, review, or update SECURITY.md guidance for a repository or component. Use when the user wants to clarify what Codex Security should review, what is out of scope, which security properties must hold, or whether existing guidance still matches the code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
日本語の概要は準備中です。原文の説明を表示しています。
host chinese call of cthulhu and similar investigative tabletop rpg sessions as kp/keeper. use when the user asks to start, continue, simulate, or play a coc scenario, wants chatgpt to be kp, asks for preset investigator cards, npc teammates, dice checks, horror investigation pacing, solo/co-op tabletop roleplaying, or persistent pre-session prep/project folders for a campaign. ask only the minimum setup questions: whether the user wants a custom investigator persona and how many npc teammates; otherwise handle scenario selection, character card creation, npc teammates, dice, pacing, narration, and campaign notes automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Use weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".
日本語の概要は準備中です。原文の説明を表示しています。
Nature-style engineering manuscript reviewer skill for testing devices, robots, platforms, systems, algorithms embodied in physical systems and engineering methods against requirements, validation, benchmarking, uncertainty, robustness and failure modes.
日本語の概要は準備中です。原文の説明を表示しています。