6,155 件 ・ 関連度順
概要と使いどころ
Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.
日本語の概要は準備中です。原文の説明を表示しています。
Run, diagnose, or manually test the private Stacktape Console locally, especially when local API/UI behavior must use the shared dev RDS data, Cognito users, AWS services, OAuth callbacks, or provider webhooks. Use for Console dev-mode setup, deciding between UI-only and full mode, shared-dev migrations, and GitHub/GitLab/Bitbucket end-to-end testing.
日本語の概要は準備中です。原文の説明を表示しています。
Python backend development standards for FastAPI, SQLModel, pytest, Ruff, and Pyright. Use when writing or modifying backend code in src/merchant, src/payment, src/apps_sdk, agents, tests, API routes, services, models, or protocol logic.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js frontend development standards for Retail-Agentic-Commerce. Use when creating or modifying UI pages, components, hooks, styling, tests, or Apps SDK widget browser behavior in src/ui or related frontend surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Author or modify a build-logic convention plugin. Use when changing plugin internals, the diagnostics catalog, or Rust-native wiring. Not for adding a dependency/module (gradle-build-system) or version bumps (dependency-update).
日本語の概要は準備中です。原文の説明を表示しています。
Add a Gradle dependency or module, or triage a build failure. Use when editing gradle.properties or a build.gradle.kts. Not for plugin internals (convention-plugin-development) or version bumps (dependency-update).
日本語の概要は準備中です。原文の説明を表示しています。
Bump a Gradle or Rust dependency version. Use when editing libs.versions.toml, native/rust/Cargo.toml, or reviewing a Renovate PR. Not for adding a module or plugin (gradle-build-system, convention-plugin-development).
日本語の概要は準備中です。原文の説明を表示しています。
Spending analysis and custom budget builder. Analyzes spending patterns using 50/30/20 rule, zero-based budgeting, or envelope method. Categorizes expenses, identifies waste, suggests cuts, and produces a 12-month budget. Use when the user says "/finance budget", "build me a budget", "analyze my spending", "where is my money going", or asks about expense optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Self-Evolving Development Loop - Dynamic skill generation with learning and evolution
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing AI agent engine components in internal/agent/. Covers the ReAct loop, swarm delegation, planning, verification, memory reflection, and cron automation.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing REST API endpoints in internal/server/. Covers routing, request validation, WebSocket streaming, and API conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing the ActonOS React 19 + Tailwind v4 frontend adhering to the official DESIGN.md specification. Covers design tokens, component decomposition, zero-hardcoded-text i18n, and go:embed delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for creating ActonOS releases. Covers version bumping, changelog management, git tagging, Docker image publishing, and ISO creation.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing messaging channel adapters via WASM Plugins and managing routing, session state, pairing codes, and accounts in internal/channels/.
日本語の概要は準備中です。原文の説明を表示しています。
A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
日本語の概要は準備中です。原文の説明を表示しています。
Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).
日本語の概要は準備中です。原文の説明を表示しています。
A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
日本語の概要は準備中です。原文の説明を表示しています。
Řídící pult pro workflow kontrakty — zjisti reálný stav, naplánuj (DAG, kolize, resume), nech uživatele vybrat a spusť jeden super.engineering worktree na každý vybraný kontrakt. Vyvolání téhle skill JE uživatelova výslovná žádost o vytvoření worktree pro vybrané kontrakty.
日本語の概要は準備中です。原文の説明を表示しています。
Fork a warp route from the local HTTP registry for development and testing. Forks each chain with the right local node per protocol — anvil for EVM chains, surfpool (Solana mainnet fork) for Sealevel chains. Use when the goal is to simulate transactions on a set of local forks before submitting them on-chain.
日本語の概要は準備中です。原文の説明を表示しています。
Foundation skill for warp-route updates. Reads the current on-chain config of a warp route via `hyperlane warp read`, enumerates every artifact (router, ProxyAdmin, ISM, hook, fee contracts) per chain, classifies each artifact's owner (auto-detects Safe / ICA / EOA; asks the user for everything else — Turnkey, Privy, MPC, custom multisig, timelock, etc.), and persists a per-artifact owner table that downstream update skills consume to know which signing path each batch needs. Read-only — no signing, no on-chain mutations.
日本語の概要は準備中です。原文の説明を表示しています。
Start the local HTTP registry server for development. Use when testing infra scripts or commands that need a Abacus work private overrides such as RPC URLS.
日本語の概要は準備中です。原文の説明を表示しています。
Insurance program review, coverage adequacy testing, contractor insurance verification, builder's risk/OCIP/CCIP evaluation, and property tax escrow management for AM, PM, and Development.
日本語の概要は準備中です。原文の説明を表示しています。
Check the current status of the Strait of Hormuz — shipping transit data, oil price impact, stranded vessels, insurance risk levels, diplomatic developments, and global trade impact. Use this skill whenever the user asks about the Strait of Hormuz, Hormuz chokepoint, Persian Gulf shipping risk, oil transit disruption, war risk premium in the Gulf, Middle East shipping routes, tanker traffic through Hormuz, oil supply chain risk, or geopolitical risk affecting energy markets. Triggers include: "Hormuz status", "Strait of Hormuz", "is Hormuz open", "shipping through the Gulf", "oil chokepoint", "Persian Gulf tanker traffic", "war risk premium", "Hormuz crisis", "energy supply chain risk", "oil transit disruption", "Middle East shipping", any mention of Hormuz or Persian Gulf in context of oil, shipping, or geopolitical risk.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes and describes vulnerabilities for specific assets and threats within an insurance company risk register context. The output must be highly professional, eloquent, and grammatically impressive, utilizing labelled headings and subheadings.
日本語の概要は準備中です。原文の説明を表示しています。