「iso」の検索結果

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.

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

You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.

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

Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.

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

Improve an existing skill or repository through isolated proposals, reproducible evaluation and evidence-based acceptance. Use for self-evolve or skill improvement.

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

"Apply spiral of silence theory (Noelle-Neumann) to analyze how perceived opinion climate suppresses minority expression. Use this skill when the user needs to understand why certain viewpoints disappear from public discourse, evaluate the role of fear of isolation in opinion expression, or assess opinion climate dynamics — even if they say 'why are people afraid to speak up', 'silent majority', or 'social pressure on opinions'.".

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

"Apply Social Identity Theory to analyze how group categorization, identification, and intergroup comparison drive behavior, bias, and conflict. Use this skill when the user needs to explain in-group favoritism or out-group hostility, diagnose organizational silo dynamics, design inclusive team structures, or when they ask 'why do groups polarize', 'how does team identity affect collaboration', or 'what drives us-vs-them thinking'.".

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

"Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)".

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

"Apply Institutional Theory (DiMaggio and Powell, 1983) to analyze how coercive, mimetic, and normative isomorphic pressures shape organizational structures and practices. Use this skill when the user needs to explain why organizations in the same field look alike, evaluate whether a practice was adopted for legitimacy vs efficiency, analyze regulatory or social pressures on strategy, or when they ask 'why do all firms in this industry do the same thing', 'is this best practice or just conformity', or 'how do regulations shape our structure'.".

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

"Apply Grounded Theory (Glaser and Strauss) to build theory inductively from qualitative data through open, axial, and selective coding. Use this skill when the user needs to develop new theory from data rather than test existing hypotheses, conduct theoretical sampling and constant comparison, determine when theoretical saturation is reached, or when they ask 'what theory explains this phenomenon', 'how do I code qualitative data systematically', or 'when do I stop collecting data'.".

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

"Apply basic game theory concepts including Nash equilibrium, dominant strategies, and the Prisoner's Dilemma to analyze strategic interactions. Use this skill when the user needs to model competitive decisions, predict rival behavior, design incentive mechanisms, or evaluate cooperation vs competition scenarios — even if they say 'what will our competitor do', 'should we cooperate or compete', or 'how do we set up the right incentives'.".

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

"Calculate and analyze promotional ROI including incremental sales lift, margin impact, and promo type comparison. Use this skill when the user needs to evaluate whether a promotion was profitable, compare promotion types, simulate promo scenarios, or optimize promotional spending — even if they say 'was this sale worth it', 'which promo type works best', 'are we giving away too many discounts', or 'plan our next promotion'.".

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

Generate financial statements (income statement, balance sheet, cash flow) with period-over-period comparison and variance analysis. Use when preparing a monthly or quarterly P&L, closing the books and need to flag material variances, comparing actuals to budget, building a financial summary for leadership review, or looking up GAAP presentation requirements and period-end adjustments.

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

Research competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.

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

Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".

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

Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

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

Create publication-quality visualizations with Python. Use when turning query results or a DataFrame into a chart, selecting the right chart type for a trend or comparison, generating a plot for a report or presentation, or needing an interactive chart with hover and zoom.

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

Provides context about the regelrecht Figma design system and helps with Figma-related tasks like component lookups and design comparisons. Use this skill proactively when: implementing UI components, looking up Figma node IDs, comparing code with Figma designs, downloading Figma assets, or working with design tokens. Activate automatically when user mentions Figma, design system, component styling, or asks about RR-Components.

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

Search, screen, deeply read, synthesize, and publish recent research papers for a user-specified topic, window, count, quality/attention balance, and language. Use for evidence-anchored literature digests, cross-paper comparisons, original-language excerpts, Chinese explanations, guided Feishu setup, or Feishu research reports.

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

Performs a white-box security review of Atlassian Forge apps using structured, Forge-specific security rules and evidence-driven reporting. Use when the user asks for a Forge security review, security audit, vuln assessment, pentest-style code review, authz review, tenant isolation analysis, web trigger hardening, or static analysis execution for a Forge app.

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

Choose, reuse, restore, park, or clean up Git workspaces while preserving work and host ownership. Create isolation only when it resolves a real conflict; inspection does not authorize creation or deletion.

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

Build structured vendor/tool evaluation matrices with weighted scoring, TCO analysis, and recommendation memos. Covers criteria definition, deal-breaker identification, and negotiation points. Use when selecting SaaS tools, evaluating technology vendors, or making build-vs-buy decisions.

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

Write structured Requests for Proposal (RFP) or Requests for Quotation (RFQ) aligned with ISO 20400 sustainable procurement principles. Cover scope, technical requirements, evaluation methodology, and commercial terms. Use when sourcing vendors, services, or equipment.

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

Author structured policy documents and Standard Operating Procedures (SOPs) following ISO document control standards. Covers purpose, scope, roles, policy statements, procedures, compliance monitoring, and review schedules. Use when creating corporate policies, operational procedures, or governance documents.

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

Stand up or reset project governance for new, complex, or troubled initiatives using PMBOK 8 value delivery, OKR alignment, and Scrum or SAFe cadence choices where relevant. Use when a project needs a charter, decision rights, stakeholder map, RAID logic, escalation path, or reporting rhythm. Do not use for simple task lists, isolated sprint notes, or code implementation planning.

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