1.8万 件 ・ 関連度順
概要と使いどころ
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
日本語の概要は準備中です。原文の説明を表示しています。
Converts ETL pipeline metadata (Informatica IICS, PowerCenter XML, and similar) into clean dbt models, SQL, and YAML rather than a mechanical one-to-one translation. Use when migrating legacy ETL mappings to dbt.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a coding agent (Claude Code, Cursor, Codex, Copilot CLI) burns through tokens or usage limits, sessions get slow or hit context limits, or the user asks to cut agent cost. Measures where the tokens go, then applies levers in order: session hygiene, always-loaded context (CLAUDE.md, skills, MCP), tool-output filtering, subagent delegation, output verbosity, and model/effort choice.
日本語の概要は準備中です。原文の説明を表示しています。
Use when unsure which engineering-workflow skill applies to the task at hand. Routes from development phase — idea, spec, plan, implement, test, review, ship — to the right skill, and shows how they chain together across a feature or bugfix.
日本語の概要は準備中です。原文の説明を表示しています。
When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet the requirements with least privilege access and how to apply that role
日本語の概要は準備中です。原文の説明を表示しています。
Updates Azure Verified Module (AVM) references in a Bicep file to their latest versions, applying only non-breaking changes and reporting the result as a table. Use when Bicep templates pin outdated AVM versions or before an infrastructure release.
日本語の概要は準備中です。原文の説明を表示しています。
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
日本語の概要は準備中です。原文の説明を表示しています。
Use on every code change — commit structure, branching, history hygiene, and versioning. Apply when committing work, opening or splitting a branch, writing commit messages, cutting a release, or recovering from a bad history state.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when making an architectural decision, choosing between competing approaches, adding or changing a public API, shipping a user-facing behavior change, or repeatedly explaining the same thing. Captures the why — context, constraints, alternatives — as ADRs and project docs. Not for restating obvious code.
日本語の概要は準備中です。原文の説明を表示しています。
Setup and initialization guide for developing AWS CDK (Cloud Development Kit) applications in Python. This skill enables users to configure environment prerequisites, create new CDK projects, manage dependencies, and deploy to AWS. Use when starting or setting up an AWS CDK project in Python.
日本語の概要は準備中です。原文の説明を表示しています。
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations. Use when an Azure bill needs reducing or a resource group needs a cost review.
日本語の概要は準備中です。原文の説明を表示しています。
Apply GDPR-compliant engineering practices across your codebase. Use this skill whenever you are designing APIs, writing data models, building authentication flows, implementing logging, handling user data, writing retention/deletion jobs, designing cloud infrastructure, or reviewing pull requests for privacy compliance. Trigger this skill for any task involving personal data, user accounts, cookies, analytics, emails, audit logs, encryption, pseudonymization, anonymization, data exports, breach response, CI/CD pipelines that process real data, or any question framed as "is this GDPR-compliant?". Inspired by CNIL developer guidance and GDPR Articles 5, 25, 32, 33, 35.
日本語の概要は準備中です。原文の説明を表示しています。
Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
日本語の概要は準備中です。原文の説明を表示しています。
Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python. Use when working on applications, plugins, or function-calling flows built on Semantic Kernel.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building a Python terminal UI inspired by Claude Code with Rich. Translates a detailed TypeScript/Ink-style visual reference into a staged Python architecture for logo, message stream, streaming Markdown, tools, diffs, prompt, footer, spinners, permissions, transcript mode, themes, accessibility, and tests. Separates Rich rendering from the input and widget responsibilities that require an application-owned event loop or an optional Textual layer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing long-horizon agents that need subagents, isolated context windows, filesystem-backed work, persistence, human approval, MCP tools, or production tracing.
日本語の概要は準備中です。原文の説明を表示しています。
Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor duplicated code by extracting helpers, shared abstractions, or clearer reusable structure. Use when asked to apply DRY, remove duplication, consolidate repeated logic, or run `/refactor:dry`.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and manage a UI redesign experiment with three git worktree branches for modern minimal, bold creative, and classic refined design directions. Use when asked to run a UI redesign experiment, compare design approaches, or prototype multiple visual directions in parallel branches.
日本語の概要は準備中です。原文の説明を表示しています。
Commit the current changes with quality checks, status review, staged diff inspection, appropriate tests, and a clear commit message. Use when the user says "commit", "c", asks to make a commit, or wants changes saved in git.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.
日本語の概要は準備中です。原文の説明を表示しています。
Review+fix protocol with optional pre-core git diff review and safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "/tw-fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal. Stop only after self-review exhausts actionable changes, each full cycle reaches post-self-review rerun plus terminal diff-review closure, and two consecutive zero-edit full cycles are clean.
日本語の概要は準備中です。原文の説明を表示しています。