「gt」の検索結果

This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.

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

Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.

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

Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.

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

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy.

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

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

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

Design first-run experiences that get users to value quickly without overwhelming them.

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

Structure a pattern library entry with problem context, solution pattern, usage examples, and related patterns.

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

Compare multiple job offers side-by-side with total compensation analysis

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

Research market rates, build negotiation strategy, and create counter-offer scripts

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

Design search experiences that help users find what they need, recover from failure, and refine results.

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

Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.

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

Select and design navigation patterns that match product structure, user tasks, and platform conventions.

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

Structure compelling design presentations for stakeholders, reviews, and showcases.

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

Ensure ATS-friendly formatting and create clean scannable layouts

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

Design adaptive layouts and interactions that work across all screen sizes and input methods.

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

When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

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

Establish design review gates with criteria, checklists, and approval workflows.

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

Craft-first interface design for dashboards, admin panels, SaaS apps, tools, settings pages, data interfaces, and interactive products. Use when designing, building, reviewing, auditing, or refining product UI where visual craft, layout hierarchy, tokens, states, visual direction, or design-system consistency matter. Not for marketing pages, landing pages, campaigns, or brand-only work.

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

Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.

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

Cluster a list of keywords into topical groups with search intent labels, validated search volume, KD, and CPC data. Use this skill whenever a user provides a list of keywords (pasted, uploaded as CSV/Excel, or via Google Sheet URL) and asks to cluster, group, map, organize, or categorize them. Also trigger when a user says "keyword cluster", "cluster my keywords", "group these keywords", "keyword map", "keyword strategy from this list", "organize keywords by topic", or pastes or uploads a list of keywords and wants structure from it. Always use this skill — do not attempt keyword clustering manually without following this workflow.

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

Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

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

Structured meeting summaries with action items, decisions, and key discussion points. Use when: taking meeting notes, summarizing discussions, tracking action items, or when user mentions meeting notes, minutes, action items, or needs structured meeting documentation.

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

Audits any landing or service page across 48 checks in 10 categories for LLM/AI discoverability, GEO readiness, content clarity, schema markup, internal linking, freshness signals, and technical crawlability. Produces an overall score out of 100, a per-category score out of 100, pass/warn/fail/ manual counts, and a prioritised fix list — all rendered as a standalone HTML report saved to disk. Use when a user provides a URL and asks to audit it, score it, check its GEO readiness, test its AI discoverability, run a landing page audit, or evaluate it for LLM citation potential. Also trigger on phrases like "audit this page", "score this URL", "check GEO for", "is this page AI-ready", "run a GEO audit", "LLM page check", "how would AI read this page", or "landing page score".

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

Design forms that minimize friction, prevent errors, and guide users to successful completion.

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