413 件 ・ 関連度順
概要と使いどころ
Debug iOS apps and profile performance using LLDB, the interactive Memory Graph Debugger, and Instruments. Use for crashes, retain-cycle inspection, hangs, build failures, and generic CPU, memory, energy, or network profiling. Use ios-memgraph-analysis for .memgraph capture, leaks CLI ownership paths, or persistent heap growth; use ios-ettrace-performance for ETTrace capture and JSON.
日本語の概要は準備中です。原文の説明を表示しています。
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
日本語の概要は準備中です。原文の説明を表示しています。
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and verification strategy before coding.
日本語の概要は準備中です。原文の説明を表示しています。
Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Map stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
日本語の概要は準備中です。原文の説明を表示しています。
Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
日本語の概要は準備中です。原文の説明を表示しています。
How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.
日本語の概要は準備中です。原文の説明を表示しています。
Writes idiomatic Rust code with memory safety, zero-cost abstractions, ownership patterns, lifetime management, trait hierarchies, and async applications with tokio.
日本語の概要は準備中です。原文の説明を表示しています。
Agile product ownership for backlog management and sprint execution. Use for writing user stories and acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing a backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate and compare technology stacks with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.
日本語の概要は準備中です。原文の説明を表示しています。
Audits AI-assisted legal, compliance, governance, and institutional decisions before reliance to determine whether the responsible human or institution has enough access to the evidence, reasoning basis, uncertainty, authority, and review path to genuinely own the decision rather than merely approve, sign, or transmit it.
日本語の概要は準備中です。原文の説明を表示しています。
Analyses contracts for risk across five critical clauses (Limitation of Liability, Indemnities, IP Ownership, Data Protection, Termination). Built for founders with no legal background. Flags red flags, explains risks in plain language, and provides negotiation guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Generate scaffolds that gradually increase student choice, voice, and ownership within a learning task. Use when students depend heavily on teacher direction and need to develop autonomy.
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI's actual mental model — view identity, lifetime, and dependencies (the Demystify canon), state ownership decision rules, Observation's per-property tracking, body-performance discipline, and the main-actor concurrency contract. Use when state resets mysteriously, views re-render too often, animations glitch between branches, choosing @State vs @Bindable vs plain property, or debugging "why did body run."
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI framework skills — data flow (identity, Observation, state ownership), layout & containers (Layout protocol, lazy-stack performance), AlarmKit, 3D charts, rich text editing, customizable toolbars, and WebKit embedding. Use for SwiftUI state/rendering bugs, custom layouts, scroll performance, or these feature areas.
日本語の概要は準備中です。原文の説明を表示しています。
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
日本語の概要は準備中です。原文の説明を表示しています。
Build and validate .arch/index.json — a committed map from each architectural component of this repository to the real directories and files that implement it, pinned to a git commit, with every path verified to exist. Also detects structural drift between that index and the current code. Use when asked to map a codebase, produce a component or code-ownership index, find which files implement a component, check whether architecture docs are stale, or detect architecture drift after a refactor. Triggers include 'map the codebase', 'component index', 'which files implement X', 'is the architecture still accurate', 'architecture drift', 'refresh the architecture index'.
日本語の概要は準備中です。原文の説明を表示しています。
Establishes configuration ownership, validation, secret boundaries and environment isolation; not credential identity policy or live deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review.
日本語の概要は準備中です。原文の説明を表示しています。
Design NestJS module boundaries and provider ownership. Use only when structuring feature/core/shared modules, controller-service boundaries, or provider lifetime; defer JWT/security, caching, and unrelated request-pipeline recipes.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
日本語の概要は準備中です。原文の説明を表示しています。
Structure Go code with package-first boundaries, `cmd/` and `internal/`, and explicit dependency wiring. Use when shaping project layout, package ownership, or service boundaries in Go; defer Redis/cache-specific implementation recipes to database skills.
日本語の概要は準備中です。原文の説明を表示しています。
Apply and enforce cloud resource tagging strategies across AWS, Azure, GCP, and Kubernetes for cost allocation, ownership tracking, compliance, and automation. Use when implementing cloud governance, optimizing costs, or automating infrastructure management.
日本語の概要は準備中です。原文の説明を表示しています。