2,338 件 ・ 関連度順
概要と使いどころ
Use when the user wants to discover and verify available Entra ID app registrations, wire one to a Power Apps Wrap mobile app, or create one through the Wrap page and update auth.config.json.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding an unspecified data source to an Expo/React Native Power Apps mobile app; routes to Dataverse, SharePoint, or another connector.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user has finished building a mobile app, started Metro with `npm run dev`, and wants the running app monitored for runtime errors AND silent failures (empty lists, blank screens, swallowed network errors) and fixed autonomously. Accepts a free-text symptom (e.g., `/debug-app "todos not appearing on home screen"`) to drive persisted-log diagnostics — injects temporary console.log statements at data-path boundaries, reads the sanitized `.powernative/metro-logs/` log, and cleans up logs after the root cause is fixed. Supports port/platform filtering, configurable clean-cycle and timeout limits, and watch-only `--no-fix` mode. Otherwise polls with a durable byte cursor, fixes inline or routes appropriately, verifies each fix from new output, and exits after the configured clean checks (default 3). Foreground loop — blocks the conversation while running. Run only after the app is loaded.
日本語の概要は準備中です。原文の説明を表示しています。
Creates the Tamagui brand system for an Expo/React Native Power Apps mobile app, including design-system.md, tokens.ts, and an HTML gallery.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update Application Insights configuration, the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow.
日本語の概要は準備中です。原文の説明を表示しています。
Use to deploy, publish, or push an Expo/React Native Power Apps mobile app to a Power Platform tenant.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a Power Apps mobile project needs dependency updates or an npm audit review. Checks the mobile-app plugin first, then updates the native host, other Microsoft packages, and all remaining direct npm packages in order with validation and rollback.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
日本語の概要は準備中です。原文の説明を表示しています。
Use to find or create a Power Platform connection ID or reference for an Expo/React Native Power Apps mobile app.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor scorecard, vendor comparison, contract negotiation, vendor switch, procurement. Also triggers when a renewal is coming up or when a tool isn't meeting expectations.
日本語の概要は準備中です。原文の説明を表示しています。
How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.
日本語の概要は準備中です。原文の説明を表示しています。
A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.
日本語の概要は準備中です。原文の説明を表示しています。
Modern, interactive alternative to `/do` — clarify intent up front, then take a task end-to-end with a serial AI review gauntlet (lens debate (lowy ⇄ hickey) → codex debate → simplify → code-police, each editing the branch in turn) → CI → evidence. ONLY invoke when the user explicitly types `/be` or `$be`; never auto-select from a natural-language request.
日本語の概要は準備中です。原文の説明を表示しています。
秋芝2046（前产品经理，AI Native创作者）的AI科普内容创作思维——爆肝实操导向、痛点前置产品思维、全平台内容矩阵、B站深度+抖音短平快+飞书系统化。 触发词：「秋芝2046视角」「像秋芝2046那样写」「AI科普教程」「DeepSeek教程」「One-Click解决一切」。 擅长：AI工具测评与推荐、AI教程设计（幼儿园→专业级）、技术热点快速响应、AIGC内容实验、多平台内容矩阵运营、飞书知识库架构、AI春晚级别的项目管理。
日本語の概要は準備中です。原文の説明を表示しています。
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs. Use after corrections or discarded proposals. Not for ordinary deletion, deprecation, migration, or exclusions materially required for safety, accuracy, compatibility, audit, quotation, or requested comparison.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — product idea diagnostic before writing code. Two modes: Startup (6 forcing questions with rigorous pushback) and Builder (generative brainstorming). Outputs design doc. Includes landscape research, premise challenge, alternatives generation, visual wireframe sketching, and optional cross-model second opinion.
日本語の概要は準備中です。原文の説明を表示しています。
Builds .NET 8 applications with minimal APIs, clean architecture, cloud-native microservices, Entity Framework Core, CQRS with MediatR, and AOT compilation.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy to AWS Elastic Beanstalk, in either Beanstalk Standard mode (EC2) or Beanstalk Cluster mode (managed EKS). Triggers on: elastic beanstalk, EB, beanstalk standard, beanstalk cluster, managed EC2 platform, web app with managed patching, worker on EC2, Heroku alternative, don't want to manage servers or container orchestration, migrate from Heroku, managed operational lifecycle, containerised app without operating Kubernetes, several services sharing a managed cluster, managed EKS without kubectl. Covers web and worker applications on EC2, and containerised single- and multi-service applications on managed EKS.
日本語の概要は準備中です。原文の説明を表示しています。
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).
日本語の概要は準備中です。原文の説明を表示しています。
Apple Human Interface Guidelines expert across iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use when designing or reviewing an Apple-platform app, auditing for HIG compliance, picking native components, or validating accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-framework for how a company runs -- the connective tissue between C-suite roles (EOS, Scaling Up, OKR-native). Use when setting up company operations, selecting a management framework, designing meeting rhythms, or implementing OKRs.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a PM Brain — a markdown-native second brain for a product operator (PM, product lead, founder, or anyone accountable for one product or initiative) doing judgment-heavy work with scattered inputs. Detects greenfield vs. migration mode, runs a focused interview, copies the deterministic scaffold into the working directory, populates placeholders from interview answers, runs a self-test, and commits. Use when invoked via `/pm-brain` or when the user asks to set up a PM Brain.
日本語の概要は準備中です。原文の説明を表示しています。
Build competitor comparison pages: X-vs-Y, alternatives and roundups, with schema. "create a vs page"
日本語の概要は準備中です。原文の説明を表示しています。