1.1万 件 ・ 関連度順
概要と使いどころ
Agent fallback for CChicken_Event_Killed-decompiles (auto-generated, category: vfunc). Locate CChicken::Event_Killed in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CChicken_Event_Killed-decompiles, CChicken::Event_Killed
日本語の概要は準備中です。原文の説明を表示しています。
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
日本語の概要は準備中です。原文の説明を表示しています。
Design patterns and architectural guidance for .NET applications. Navigation skill covering vertical slices, domain modeling, messaging patterns, resilience, caching, and system design. For building scalable, maintainable applications. Keywords: architecture, patterns, vertical slices, domain modeling, messaging, resilience, caching, design patterns
日本語の概要は準備中です。原文の説明を表示しています。
Defines caching strategies with cache keys, TTL values, invalidation triggers, consistency patterns, and correctness checklist. Provides code examples for Redis, CDN, and application-level caching. Use when implementing "caching", "performance optimization", "cache strategy", or "Redis caching".
日本語の概要は準備中です。原文の説明を表示しています。
CI/CD caching optimizer for dependency caching, Docker layer caching, and build speed improvements. Activate on: CI cache, build speed, dependency caching, Docker layer cache, turbo remote cache, GitHub Actions cache, pnpm store cache. NOT for: CI/CD pipeline creation (use github-actions-pipeline-builder), deployment strategy (use blue-green-deployment-orchestrator), Docker image building (use docker-multi-stage-optimizer).
日本語の概要は準備中です。原文の説明を表示しています。
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
日本語の概要は準備中です。原文の説明を表示しています。
Architecture and systems design for agents that retain bounded state across sessions. Covers durable event history, owned state, derived memory, retrieval indexes, framework evaluation, recovery, deletion, and rebuild behavior. Uses constructed implementation examples and workload calibration rather than universal vendor, latency, similarity, retention, or cost claims. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).
日本語の概要は準備中です。原文の説明を表示しています。
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
日本語の概要は準備中です。原文の説明を表示しています。
GitHubのローカル保存データからIssueやPR、重複候補を調べ、同期状況や情報の不足を確認しながら、判断前に最新の状態を照合するスキル。
Granolaのローカルアーカイブから会議メモや文字起こしを検索・取得するスキル。同期状態を確認し、必要な更新やSQLによる正確な件数集計も扱います。
概念や業務の流れ、ソフトウェア構成を図にまとめます。ブラウザで開けるSVG入りHTMLか、編集できるExcalidraw形式で保存するスキルです。
Redisを使ったキャッシュ、アクセス回数制限、複数処理の同時実行制御、メッセージ配信を設計し、キーの有効期限や接続管理も見直すスキル。
機械学習のない既存アプリに、推薦・分類・予測などを追加するための手順を整理します。課題とデータの確認から、最初のモデルの学習・評価・組み込みまでを支援します。
LaravelのWebアプリやAPIを、役割の分かれた構成で実装・レビューします。データ取得、入力検証、API応答、キューやキャッシュを整理し、保守しやすい設計を支援します。
PDF解析や画像分析などの処理結果を、ファイル内容に基づいて保存・再利用するスキル。移動や名前変更に影響されず、内容が変われば再処理する仕組みを設計します。
AndroidやKMPのモジュール構成と依存関係を整理し、業務処理・画面・データ取得を分けて設計するスキル。実装例をもとに各層の役割を明確にします。
システムの構成やデータの流れを、クリックして詳しく読める立体的なHTMLマップに整理します。同じデータから説明文も生成し、設計上の判断や未解決の質問を管理します。
Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.
日本語の概要は準備中です。原文の説明を表示しています。
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
日本語の概要は準備中です。原文の説明を表示しています。
Design AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
日本語の概要は準備中です。原文の説明を表示しています。
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
日本語の概要は準備中です。原文の説明を表示しています。
Universal archivist for personal file archives (Dropbox/B2/Gmail-takeout/local-mount/hard-drive-dump). Filters for high-value content (the user's own writing, ideas, relationships) and surfaces it interactively. REFUSES TO RUN without an explicit gbrain.yml `archive-crawler.scan_paths:` allow-list.
日本語の概要は準備中です。原文の説明を表示しています。
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data architecture, valuing data for fundraising or M&A, sequencing data hires, or when user mentions CDO, chief data officer, data strategy, data mesh, lakehouse, training data, data product, data monetization, or customer data asset. NOT a tactical data engineering skill — strategic decisions only.
日本語の概要は準備中です。原文の説明を表示しています。