1,484 件 ・ 関連度順
概要と使いどころ
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
日本語の概要は準備中です。原文の説明を表示しています。
Commission a project to an SDLC option bundle (solo / single-team / programme / assured). Asks structured questions, recommends an option × level, installs the bundle, and records the decision in .sdlc/team-config.json.
日本語の概要は準備中です。原文の説明を表示しています。
Configure SDLC team formation and SDLC method for this project. Asks the four-option SDLC method question (solo / single-team / programme / assured), then recommends and installs team plugins based on project type, language, tech stack, and support needs.
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch a structured cross-phase review of a phase artefact. MANDATORY for design-spec and test-spec; the gate validator checks for the resulting review record before passing. Recommended for requirements-spec.
日本語の概要は準備中です。原文の説明を表示しています。
Spot-check citations in library files for obvious hallucinations. Resolves DOIs against the DOI registry, validates arXiv IDs, checks the format of journal references. Soft-fails on transient lookup failures rather than blocking. Recommended after kb-ingest and as part of periodic library hygiene.
日本語の概要は準備中です。原文の説明を表示しています。
Source pre-2016 cinema with gothic/occult sensibility, literary texture, and historical grandeur — build watchlists, curate Criterion/MUBI picks. Uses Perplexity for film discourse, Exa for web search, Firecrawl for scraping. Triggers on film recommendations, watchlist, gothic cinema, occult film, arthouse, pre-2016 movies.
日本語の概要は準備中です。原文の説明を表示しています。
Audits and optimizes the five global Claude layers (User Preferences, Styles, Global Memory, Skills, MCP Connectors) using the Global Layer Scorecard (six dimensions, anchored 1-5 rubrics). Detects eight cross-layer failure modes and produces evolutionary recommendations (Promotion, Demotion, Codification, Skill Extraction). Use when user says "audit my global setup," "optimize my preferences," "review my Claude configuration," "check my cross-project setup," "are my preferences working," "clean up my global memory," or "what should be in my preferences vs my project." Also use when a user has 3+ Projects and wants to improve their shared foundation. Do NOT use for single-Project audits, Project Memory optimization, or full-stack audits (use rootnode-project-audit, rootnode-memory-optimization, or rootnode-full-stack-audit respectively, if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized research and analysis prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for data analysis, policy research, systematic evidence review, investigative research, and research-specific deliverables. Use when building prompts for quantitative data interpretation, evidence-based policy recommendations, literature reviews, causal analysis, hypothesis-driven investigation, or briefing documents. Trigger on: "prompt for data analysis," "research prompt," "policy brief prompt," "literature review prompt," "prompt for investigating," "systematic review prompt," "build a prompt for evidence synthesis," "causal analysis prompt," "briefing document prompt." Also use when user describes a research or analytical task and needs a structured Claude prompt for it. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or auditing Claude Projects (use rootnode-project-audit if available).
日本語の概要は準備中です。原文の説明を表示しています。
Guides selection of identity, reasoning, and output approaches for Claude prompts based on task characteristics. Trigger on: "help me choose an approach," "which approach fits this task," "recommend a prompt pattern," "compare reasoning methods," "map this task to the right approach," "what combination of approaches," "which identity fits," "which reasoning method." Also trigger on symptom-phrased: "my prompt feels generic," "I don't know which approach to use," "my output lacks domain depth." Covers decision-tree logic across 8 identity approaches, 18 reasoning variants, and 10 output formats. After selection, use the relevant catalog skill if available to retrieve full templates. Activate whenever approach-selection across multiple categories is the primary decision. Do NOT use when the user already names a specific approach to retrieve (use the relevant catalog skill directly if available) or for evaluating existing prompts (use rootnode-prompt-validation if available).
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive audit of a user's entire Claude environment — combines Project audit (six-dimension Project Scorecard, seven anti-patterns) with Global audit (six-dimension Global Layer Scorecard) plus Cross-Layer Alignment Check across all nine layers and Evolutionary Recommendations across four pathways. Produces a unified action plan. Use when user says "full audit of everything," "audit my entire Claude setup," "full stack audit," "comprehensive review of my project and preferences," "check everything," or wants the complete health check of both a specific Project AND their global configuration. Also use when a project audit reveals cross-layer issues that require full-stack visibility. Do NOT use for auditing only a Project (use rootnode-project-audit if available) or only global layers (use rootnode-global-audit if available). Do NOT use for single prompt evaluation (use rootnode-prompt-validation if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a GitHub Copilot (or any bot reviewer) pull-request review to a clean pass without babysitting it: fix each finding in its own commit, reply to the review thread with the fix sha, resolve the thread, re-request the bot, and poll for the async re-review. Covers the thread node-id (PRRT_...) vs comment databaseId distinction, the resolveReviewThread GraphQL mutation, the copilot-pull-request-reviewer[bot] slug, and how to read the bot's verdict (COMMENTED plus a "human review recommended" banner is not a blocking finding). Use when Copilot has left review comments on your PR, when bot review threads must be closed out with an auditable fix-reply-resolve trail before merge, or when you need to verify that a re-review actually landed on the new HEAD rather than the old one.
日本語の概要は準備中です。原文の説明を表示しています。
Review software architecture for coupling, cohesion, SOLID principles, API design, scalability, and technical debt. Covers system-level evaluation, architecture decision record review, and improvement recommendations. Use when evaluating a proposed architecture before implementation, assessing an existing system for scalability or security, reviewing ADRs, performing a technical debt assessment, or evaluating readiness for significant scale-up.
日本語の概要は準備中です。原文の説明を表示しています。
Review web design for layout quality, typography, colour usage, spacing, responsive behaviour, brand consistency, and visual hierarchy. Covers design principles evaluation and improvement recommendations. Use when reviewing a design mockup before development, assessing an implemented site for design quality, providing feedback during a design review session, evaluating brand consistency, or checking responsive behaviour across breakpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Perform capacity planning using historical metrics and growth models. Use predict_linear for forecasting, identify resource constraints, calculate headroom, and recommend scaling actions before saturation. Use before seasonal traffic spikes or product launches, during quarterly capacity reviews, when resource utilization trends upward, or before budget planning cycles.
日本語の概要は準備中です。原文の説明を表示しています。
Implement cloud cost optimization strategies for Kubernetes workloads using tools like Kubecost for visibility, right-sizing recommendations, horizontal and vertical pod autoscaling, spot/preemptible instances, and resource quotas. Covers cost allocation, showback reporting, and continuous optimization practices. Use when cloud costs are growing without proportional business value, when resource requests are misaligned with actual usage, when manual scaling leads to over-provisioning, or when implementing showback and chargeback for internal cost accountability.
日本語の概要は準備中です。原文の説明を表示しています。
Map the intellectual property landscape for a technology domain or product area. Covers patent cluster analysis, white space identification, competitor IP portfolio assessment, freedom-to-operate preliminary screening, and strategic IP positioning recommendations. Use before starting R&D in a new technology area, when evaluating market entry against incumbents with strong patent portfolios, preparing for investment due diligence, informing a patent filing strategy, or assessing freedom-to-operate risk for a new product.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of a GitHub repository's security posture. Gathers ref protection (rulesets AND classic branch protection), Actions token permissions, code and supply-chain features (Dependabot, secret scanning, push protection, CodeQL), and repo hygiene toggles via `gh api`, then classifies findings against essential / recommended / advanced tiers into a PASS/GAP report. Makes NO changes. Use when reviewing a repo before open-sourcing or a release, auditing a public user-owned repo whose CI auto-commits to the default branch, verifying a hardening change actually took effect, or producing a baseline security posture report for a repository.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when analyzing market breadth charts, specifically the S&P 500 Breadth Index (200-Day MA based) and the US Stock Market Uptrend Stock Ratio charts. Use this skill when the user provides breadth chart images for analysis, requests market breadth assessment, positioning strategy recommendations, or wants to understand medium-term strategic and short-term tactical market outlook based on breadth indicators. All analysis and output are conducted in English.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive US stock analysis including fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock comparisons, and investment report generation. Use when user requests analysis of US stock tickers (e.g., "analyze AAPL", "compare TSLA vs NVDA", "give me a report on Microsoft"), evaluation of financial metrics, technical chart analysis, or investment recommendations for American stocks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate architecture guidelines for the project. Analyzes tech stack from DESCRIPTION.md, recommends an architecture pattern, and creates .ai-factory/ARCHITECTURE.md. Use when setting up project architecture, asking "which architecture", or after $aif setup.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
日本語の概要は準備中です。原文の説明を表示しています。