本文へ移動
cccskills
無料GitHub で公開

"grad-affordance"

"Apply Affordance Theory (Gibson, 1979; Norman, 1988) to analyze the action possibilities that an artifact provides to an actor. Use this skill when the user needs to evaluate technology design from an affordance perspective, identify why users struggle with an interface, analyze IT-enabled organizational change through affordance actualization, or when they ask 'what does this technology afford', 'why can't users figure out this feature', or 'how does technology enable new practices'.".

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.3 KB
  • examples/sample_scenario.md7.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Affordance Theory (Gibson / Norman)

Overview

Affordance Theory explains how actors perceive and realize action possibilities offered by objects or environments. Gibson's ecological view holds that affordances are relational properties existing between actor and environment, independent of perception. Norman adapted the concept for design — perceived affordances guide user interaction, and signifiers communicate where action is possible. In IS research, affordance theory explains how technology enables (or constrains) organizational action.

When to Use

  • Analyzing why users can or cannot effectively use a technology
  • Designing interfaces that communicate functionality clearly
  • Explaining how the same technology produces different outcomes in different organizations
  • Bridging the gap between technology features and organizational practices

When NOT to Use

  • Predicting adoption likelihood (use TAM/UTAUT)
  • Measuring usability metrics quantitatively (use SUS or heuristic evaluation)
  • When the focus is purely on aesthetic design without functional implications

Assumptions

IRON LAW: An affordance exists in the RELATION between actor and artifact —
it is neither a property of the object alone nor of the user alone.

Key assumptions:

  1. Affordances are relational — they depend on both artifact properties and actor capabilities
  2. Affordance existence differs from affordance perception differs from affordance actualization
  3. The same technology affords different actions to different actors (role, skill, goal-dependent)
  4. Constraints are the complement of affordances — what the artifact prevents or discourages

Methodology

Step 1 — Identify actors and artifacts

Specify the technology artifact and the actor groups. Characterize actor capabilities, goals, and context. The same artifact affords different things to a novice versus an expert.

Step 2 — Enumerate affordances

For each actor-artifact pair, identify:

Affordance TypeDescription
ExistenceWhat action possibilities objectively exist in the relation
PerceptionWhich affordances actors actually perceive (Norman's focus)
ActualizationWhich perceived affordances actors act upon

Include constraints (actions the artifact prevents) alongside affordances.

Step 3 — Analyze gaps

Identify three critical gaps:

  • Perception gap: affordances that exist but are not perceived (design/signifier problem)
  • Actualization gap: affordances perceived but not actualized (motivation/skill/resource problem)
  • False affordance: actions perceived as possible but that do not actually exist

Step 4 — Recommend design or organizational interventions

For perception gaps: improve signifiers, onboarding, or documentation. For actualization gaps: provide training, resources, or remove organizational barriers. For false affordances: fix misleading cues in the interface.

Output Format

## Affordance Analysis: [Artifact] x [Actor Group]

### Actor Profile
- Role: ...
- Capabilities: ...
- Goals: ...

### Affordance Map
| Affordance | Exists? | Perceived? | Actualized? | Gap Type |
|-----------|---------|------------|-------------|----------|
| | | | | |

### Constraints
- [constraint]: [effect on actor behavior]

### Gap Analysis
- Perception gaps: ...
- Actualization gaps: ...
- False affordances: ...

### Recommendations
1. [Gap type]: [intervention]
2. ...

Gotchas

  • Do not conflate Gibson's affordances (relational, objective) with Norman's perceived affordances (subjective, design-focused) — state which lens you are using
  • "Feature" is not "affordance" — features are artifact properties; affordances emerge from the actor-artifact relation
  • Affordance theory is explanatory, not predictive — it helps interpret why things happen, not forecast adoption rates
  • In IS research, affordance actualization depends on organizational context (norms, routines, power structures), not just individual perception
  • Beware affordance creep — listing every conceivable action possibility without prioritizing those relevant to the research question
  • Norman later preferred "signifier" over "perceived affordance" to reduce confusion — use current terminology

References

  • Gibson, J. J. (1979). The Ecological Approach to Visual Perception. Houghton Mifflin.
  • Norman, D. A. (1988). The Design of Everyday Things. Basic Books.
  • Markus, M. L., & Silver, M. S. (2008). A foundation for the study of IT effects: A new look at DeSanctis and Poole's concepts of structural features and spirit. Journal of the AIS, 9(10/11), 609-632.
  • Volkoff, O., & Strong, D. M. (2013). Critical realism and affordances: Theorizing IT-associated organizational change processes. MIS Quarterly, 37(3), 819-834.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

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

charlieviettq/awesome-agent-skill262026年7月20日 更新

charlieviettq のスキルをすべて見る

このスキルの問題を報告する