「culture」の検索結果

Create or redesign creative agency, production studio, architecture, culture, and portfolio websites with billboard typography, hard black-and-white chapters, exposed grids, documentary imagery, irregular collages, restrained parallax, brutalist navigation, and accessible FAQ controls.

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

Analyze a startup from three perspectives — VC investor, job applicant, and CEO/founder — covering market, traction, unit economics, team, defensibility, runway, equity value, culture, and competitive position, with a verdict for each. Use this skill whenever the user wants to evaluate a startup or private tech company: due diligence, whether to invest in it or join it, weighing a startup job offer, company health, outlook, or competitive position, or open-ended asks such as "what do you think of [company]" or "research [company] for me".

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

Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste", "saying no", or "is this good enough to ship". Also trigger when critiquing a UI, feature, or roadmap for focus and simplicity, cutting scope to the essential, or pressure-testing the whole experience from first run to daily use. Covers the simplicity audit, the no list, design-is-how-it-works, end-to-end ownership, demo culture, and a Jobs-style review protocol with binary verdicts. For visual design fundamentals, see refactoring-ui. For usability audits, see ux-heuristics. For detail polish, see microinteractions.

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

Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.

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

Use when evaluating Nick Sleep-style long-term compounders: scale economies shared, customer obsession, low turnover, long runway, owner culture, and value creation through lower prices.

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

Build a candidate's research brief on a company before an application or interview. Use when asked to research a company for a job, prep a company brief before an interview, or understand a prospective employer fast. Produces a one-page brief — what they do & how they make money, recent news & trajectory, product & competitors, likely challenges, culture signals, and smart questions to ask.

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

Help users build a sustainable engineering culture by measuring health through frameworks like Core 4, managing technical debt as leverage, and optimizing workflows with AI tools.

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

Help users build and scale a high-velocity growth experimentation engine that prioritizes impact and fosters a culture of rapid learning.

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

Use when targeting Forest Ecology and Management or deciding whether a forest-science manuscript fits this venue. Encodes the journal's fit, the ecological-evidence-with-management-relevance bar, silviculture and disturbance expectations, Elsevier house style, official-submission re-check, and desk-reject heuristics.

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

Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (amj-rebuttal).

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

Structures biological experiments so inference is valid by construction, covering Fisher's principles (randomization, replication, local control), the experimental-vs-observational unit distinction and pseudoreplication (Hurlbert 1984; Lazic 2018), randomization mechanics (complete, restricted, stratified, rerandomization, run-order), blocking layouts (randomized complete block, Latin square, incomplete block), factorial designs and interactions, and the split-plot/nested error strata hidden inside multi-batch genomics. Use when deciding the experimental unit and what counts as a replicate, planning randomization and run order, choosing a blocked/factorial/split-plot/nested layout, avoiding pseudoreplication in cell-culture or animal studies, or specifying the random-effects structure of the analysis model. For assigning samples to sequencing batches/lanes/plates and batch-effect correction see experimental-design/batch-design; for regulated clinical-trial randomization see clinical-biostatistics.

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

Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech. Use for management reviews, quality objectives and KPIs, quality culture, and Notified Body / FDA inspection prep per ISO 13485 Clause 5.5.2.

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

Surface beliefs, assumptions, stories, and values shaping a system. Use when deeper mental models need examining with care and evidence.

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

Map systemic forces shaping a wellbeing concern without individualising the problem. Uses Bronfenbrenner's ecological model and social determinants to generate structural interventions.

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

Anchor curriculum learning in a specific local place with connections to community, culture, and identity. Use when connecting academic content to students' local environment and heritage.

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

Prepare management meeting materials and question lists for A-share investment due diligence. Adapted from the original dd-meeting-prep skill for Chinese business culture and management meeting conventions. Triggers on "A股尽调会议准备", "管理层会议准备", "management meeting China", "DD meeting prep", "管理層访谈准备", or "prepare for management meeting [company]".

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

Expert knowledge for Azure Health Data Services development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using FHIR/DICOM APIs, bulk import/export, de-identification, events, or Synapse/Data Lake integrations, and other Azure Health Data Services related development tasks. Not for Azure Health Bot (use azure-health-bot), Azure Data Manager for Agriculture (use azure-data-manager-for-agri), Azure Energy Data Services (use azure-energy-data-services).

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

Expert knowledge for Azure Energy Data Services development including troubleshooting, decision making, architecture & design patterns, security, configuration, integrations & coding patterns, and deployment. Use when configuring ADME metrics/partitions, choosing tiers, securing auth/ACLs/legal tags, or integrating ACZ/DDMS with Databricks/Fabric, and other Azure Energy Data Services related development tasks. Not for Azure Data Explorer (use azure-data-explorer), Azure Synapse Analytics (use azure-synapse-analytics), Azure Data Factory (use azure-data-factory), Azure Data Manager for Agriculture (use azure-data-manager-for-agri).

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

Write a brand manifesto — a bold, belief-driven declaration of what the brand stands for, fights against, and exists to change. Use when the user says "brand manifesto", "manifesto", "what we believe", "brand declaration", "brand belief statement", "rally the team around the brand", "inspire the team", "internal brand document", "culture document", "why we exist statement", "brand credo", "brand creed", or wants to write something that goes beyond a mission statement to express the brand's conviction and worldview.

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

Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. Not reformatting — re-contextualizing for each platform's culture. Triggers on: "atomize this content", "repurpose my blog post", "turn this into social posts", "content atomizer", "pillar content", "one to many content", "repurpose content", "multiply my content", "content explosion", "turn article into posts", "break down this article", "micro content from blog", "content pillar strategy", "10x my content", "platform-native content", "atomize", "content multiplication".

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

Use when working on accessibility, a11y, WCAG, ARIA, screen readers, keyboard nav, focus order, contrast, alt text, captions, reduced motion, or target sizes; not language/culture/device (see inclusive-design).

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

VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale

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

Guide incident response from detection to post-mortem using SRE principles, severity classification, on-call management, blameless culture, and communication protocols. Use when setting up incident processes, designing escalation policies, or conducting post-mortems.

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

Assess organization's digital transformation readiness. Evaluate data culture, technology adoption, and process maturity.

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