7,585 件 ・ 関連度順
概要と使いどころ
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
"Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
Visual design audit for iOS apps on real hardware. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
Scrape the Hacker News front page (titles, points, comment counts).
日本語の概要は準備中です。原文の説明を表示しています。
Generate missing documentation from scratch for a feature, module, or entire project. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"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 the Resource-Based View (Barney, 1991) and VRIO framework to evaluate whether a firm's resources and capabilities confer sustained competitive advantage. Use this skill when the user needs to assess internal resources for strategic value, determine if a competitive edge is sustainable, audit resource portfolios for VRIO criteria, or when they ask 'what makes our advantage sustainable', 'which resources matter most', or 'can competitors replicate this'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Design finalization: generates production-quality Pretext-native HTML/CSS. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply rigorous survey design principles including construct operationalization, Likert scale development, reliability and validity assessment, and common method variance control. Use this skill when the user designs questionnaires, develops measurement items, needs to evaluate Cronbach's alpha or AVE, or when they ask 'how do I operationalize this construct', 'is my scale reliable', or 'how do I control for CMV'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Uppsala Internationalization Model to analyze gradual foreign market entry based on psychic distance and experiential learning. Use this skill when the user needs to plan a staged internationalization sequence, understand why firms enter culturally similar markets first, or evaluate whether a firm's international expansion follows the establishment chain from export to subsidiary.".
日本語の概要は準備中です。原文の説明を表示しています。
Cross-model benchmark for gstack skills. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
Save working context. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".
日本語の概要は準備中です。原文の説明を表示しています。
"Turn an English description (or mermaid source) into a diagram triplet: the source, an editable .excalidraw file you can open (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Giddens' structuration theory to analyze the duality of structure — how social structures are both the medium and outcome of the practices they organize. Use this skill when the user needs to bridge agency and structure in organizational or social analysis, explain how routines reproduce or transform institutional patterns, analyze the recursive relationship between action and structure, or when they ask 'do people shape institutions or do institutions shape people', 'how are these routines maintained', or 'where does change come from if structures constrain action'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Full safety mode: destructive command warnings + directory-scoped edits. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
Chief Security Officer mode. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Technology Acceptance Model (Davis, 1989) and Unified Theory of Acceptance and Use of Technology (Venkatesh et al., 2003) to predict technology adoption. Use this skill when the user needs to evaluate user acceptance of a new system, diagnose adoption barriers, design interventions to improve technology uptake, or when they ask 'why aren't users adopting this', 'what drives technology acceptance', or 'how do we increase adoption rates'.".
日本語の概要は準備中です。原文の説明を表示しています。