「firm」の検索結果

Create marketing plans for accounting firms. TRIGGERS - Use when user needs help with accounting-firm-marketing related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply the Dynamic Capabilities framework (Teece et al., 1997) — sensing, seizing, and transforming — to analyze how firms adapt, integrate, and reconfigure competences in rapidly changing environments. Use this skill when the user needs to explain why some firms sustain advantage while others decline, evaluate organizational agility, distinguish operational from strategic capabilities, or when they ask 'how do we stay competitive as the market shifts', 'why did this firm fail to adapt', or 'what capabilities do we need to build'.".

日本語の概要は準備中です。原文の説明を表示しています。

Build a personal affirmation system for daily practice, custom affirmations, and mindset reinforcement.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts U.S. civil litigation Answers with paragraph-by-paragraph admissions/denials, affirmative defenses, and counterclaim triage. Trigger when user needs a responsive pleading to a complaint, mentions affirmative defenses, admit/deny responses, Rule 8, or insufficient knowledge responses.

日本語の概要は準備中です。原文の説明を表示しています。

Guides selection of the optimal confirmatory test (CCT, SIT, FUT, OSLT) for primary aldosteronism based on patient safety and feasibility. Triggers include when a clinician asks “Which confirmatory test should I use?” or evaluates patient comorbidities before testing.

日本語の概要は準備中です。原文の説明を表示しています。

Identifies patients with a positive aldosterone-to-renin ratio screening who may proceed directly to subtype testing without confirmatory testing based on specific clinical criteria. Triggers include spontaneous hypokalemia, baseline plasma aldosterone concentration >100 pg/mL (CLEIA), renin suppression, or a clinician questioning the need for a confirmatory test after a positive screen.

日本語の概要は準備中です。原文の説明を表示しています。

Core firmware context for the Megahub ESP32 project. Use when working on PlatformIO configuration, build scripts, library structure, main.cpp, or general ESP32 firmware development. Covers build system, project structure, common pitfalls, and debugging.

日本語の概要は準備中です。原文の説明を表示しています。

Plan advisory firms. TRIGGERS - Use when user needs help with advisory-firm-plan related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Create accounting firm business plans. TRIGGERS - Use when user needs help with accounting-firm-plan related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Grow accounting firms. TRIGGERS - Use when user needs help with accounting-firm-growth related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Create marketing plans for accounting firms. TRIGGERS - Use when user needs help with accounting-firm-marketing related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

日本語の概要は準備中です。原文の説明を表示しています。

Cloud Workerで使うツールを事前に組み込んだイメージを作成・選択し、起動時間と稼働を検証。失敗時の切り戻しや、承認後の旧イメージ削除も扱います。

• ツールを組み込んだイメージの作成
• 変更前後の起動時間を比較したいとき
• 新イメージでのセッション稼働確認

作業完了や不具合修正を報告する前に、テストやビルドを実行して結果を確認します。コミットやPR作成の前にも、実際の出力を根拠に状況を伝えるスキルです。

• 完了報告の前に結果を確認したいとき
• 不具合の修正を確かめたいとき
• コミットやPR前の検証

Mailtrapで登録確認やパスワード再設定のメール送信を実装します。開発用のテスト環境と本番の送信先を分け、認証やドメイン確認、配信失敗への対処も整理します。

• 登録確認メールを追加したいとき
• パスワード再設定メールの実装
• 実際に配信せずテストしたいとき

macOSのMessages.appを通じて、iMessageやSMSの会話履歴と新着を確認します。送信先と本文を確認したうえで、文章や添付ファイルを送るスキルです。

• 最近のメッセージ一覧を確認したいとき
• 会話履歴を読み返したいとき
• 確認後に文章や添付ファイルを送るとき

Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffold a custom AI agent harness via `metaharness new {name} --template {id} --host {id}`. Defaults to DRY-RUN (no writes) unless --confirm is passed. Refuses to write to the calling repo root or anywhere inside it. Honors ADR-150 architectural constraint + ruflo's "destructive-action confirmation" pattern.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate firmware rollouts with canary deployment and anomaly-gated advancement

日本語の概要は準備中です。原文の説明を表示しています。

Routine client correspondence from templates — appointment confirmations, document requests, brief "we filed it" updates. Plain language, required elements, supervision routing. NOT substantive advice. Use when a student needs to send routine correspondence, an appointment confirmation, a document request letter, or a brief status note to a client.

日本語の概要は準備中です。原文の説明を表示しています。

Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.

日本語の概要は準備中です。原文の説明を表示しています。

IoT and embedded device security testing methodology. Covers hardware reconnaissance (UART, JTAG, SWD, SPI flash, I2C EEPROM, eMMC chip-off), firmware acquisition (vendor portals, OTA capture, flash dump, binwalk extraction), firmware analysis (filesystem mounting, binary triage, hardcoded secrets, default credential discovery), bootloader attacks (U-Boot console, secure-boot bypass, fault injection), runtime attacks on embedded Linux/RTOS (busybox CVEs, MTD writes, /dev/mem), wireless protocol attacks (Zigbee, BLE, Z-Wave, LoRaWAN, Thread/Matter, sub-GHz), MQTT/CoAP/Modbus/BACnet/OPC-UA exploitation, mobile companion app analysis, cloud-IoT API abuse, and side-channel/glitching basics. Use for IoT pentest, smart-home assessment, ICS/OT testing, or embedded vulnerability research.

日本語の概要は準備中です。原文の説明を表示しています。

Methodology for detecting client SOC patches, attacker activity, and security-state changes that occur DURING a red-team engagement — and converting those observations into deliverable findings. Built from authorized red-team work where the client patched a confirmed SQLi within 30 minutes of detection AND an external attacker locked multiple new accounts during a single test session. Use when (a) running ANY active engagement against a monitored target, (b) a previously-confirmed finding stops reproducing, (c) baseline timing shifts unexpectedly, or (d) you notice response patterns changing during testing.

日本語の概要は準備中です。原文の説明を表示しています。

Hunt Clickjacking — missing X-Frame-Options / CSP frame-ancestors lets an attacker embed the target page in an invisible iframe and trick victims into clicking buttons they cannot see (UI redressing). Targets: login flows, money transfers, account settings, OAuth confirmation pages. Confirm by fetching the page, then PROVE it frames in a real browser and a sensitive state-changing action survives the cross-site context (SameSite cookies / framebusting JS can defeat it) — header-absence alone is not a finding.

日本語の概要は準備中です。原文の説明を表示しています。