「ticket」の検索結果

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

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

Activate for any ticket that builds new UI, reshapes an existing interface, or requires visual direction. Guidance for distinctive, intentional visual design, aesthetic direction, typography, and layout choices. Do not apply when the project has an established design system and the ticket is within its constraints.

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

Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.

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

Use when: Tester runs a full QA session, processes a Builder handoff, executes test steps, writes a GitHub test report, or aligns ticket state after verification.

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

Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.

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

This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.

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

ユーザーとの対話と既存コード分析から機能仕様ドキュメント（要件定義・クリティカル設計の決定・必要なら機能全体の設計）を作成する。GitHub Issue 作成は /create-ticket の責務。Triggers on: '/define-feature', '機能定義', '要件定義', '機能設計'

Perform DCSync attacks to replicate Active Directory credentials and establish domain persistence by extracting KRBTGT, Domain Admin, and service account hashes for Golden Ticket creation.

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

Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket automatically from the issue's linear-linkback comment.

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

Generate an event ticket image with QR code, event name, date, venue, and seat information.

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

Claude API (platform.claude.com) のプロンプトエンジニアリング・評価リファレンス。 prompt engineering, XML タグ, few-shot, system prompts, モデル別プロンプティング（Fable 5 / Opus 5 / Sonnet 5）。 evals, grading（LLM-graded 等）, jailbreak・prompt leak 対策, hallucination 低減, classification, ticket routing 等ユースケース実装。

Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.

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

Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.

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

Creating an Azure DevOps work item or posting a comment with the obvious `az boards` command silently stores HTML that cannot be fixed afterward. Use this instead. Also covers reading a work item and transitioning its state. Trigger on "create ticket", "new work item", "comment on

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

Perform DCSync attacks to replicate Active Directory credentials and establish domain persistence by extracting KRBTGT, Domain Admin, and service account hashes for Golden Ticket creation.

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

Active Directory attack methodology for internal network red team engagements. Covers reconnaissance (BloodHound, PowerView, ADExplorer), credential abuse (Kerberoasting, ASREProasting, NTLM relay, LLMNR/NBT-NS poisoning), privilege escalation (ACL abuse, GPO abuse, unconstrained/constrained delegation), lateral movement (Pass-the-Hash, Pass-the-Ticket, Overpass-the-Hash, WMI/WinRM/PsExec), persistence (Golden/Silver/Diamond Tickets, DCSync, DCShadow, AdminSDHolder, Skeleton Key), forest trust attacks, ADCS abuse (ESC1-ESC15), and modern MDI/Defender for Identity evasion. Use when assessing on-prem AD, hybrid AD/Entra ID environments, or ADCS deployments.

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

You are helping a penetration tester forge Kerberos tickets for domain

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

This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.

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

macOSのThings 3で、今日の予定や受信箱を確認し、タスクの追加・検索・更新を行うスキル。メモ、期限、タグ、チェックリストも扱えます。

• 今日の予定と受信箱を確認したいとき
• 期限やチェックリスト付きのタスク登録
• 既存タスクを検索・更新したいとき

一度の対話では収まらない大きな企画や変更を、決めるべき問いと依存関係に整理します。課題管理ツールに判断の記録を残し、実行に移るまでの道筋を明らかにするスキル。

• 複数の対話にまたがる大きな計画
• 未決事項と依存関係の整理
• 共同作業で判断の経緯を共有

技術が苦手で不満を抱きやすい利用者になりきってアプリを試し、操作の分かりにくさや離脱の原因を発見。実際の改善課題と個人的な不満を分け、修正案をまとめます。

• 公開やデモ前に使いやすさを確認したいとき
• 新規ユーザーの体験を点検したいとき
• 登録・課金でのつまずきを探したいとき

Turn messy user research notes, interviews, support tickets, surveys, and product context into an evidence-backed decision room: a single HTML artifact with an evidence ledger, theme map, confidence heatmap, opportunity matrix, decision memo, and experiment queue. Use when teams need to move from qualitative signals to product or design decisions without fabricating certainty.

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

Primary entry point for direct flight, hotel, restaurant, or event-ticket transactions and for bounded live availability checks delegated by Travel Planning. Always use before provider-specific skills or browser work when the user asks to find live availability or prices, compare bookable options, book, or continue an active booking. Do not use for trip planning itself, broad inspiration, opening hours, schedules, flight status, or other factual questions without transaction intent.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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