Historical publisher document: fixed Git revision, recorded commit date 2026-02-12T17:12:18Z. This is a Git-recorded date, not an independent web-archive capture date. The complete original document body follows, rendered from unchanged Markdown with relative links anchored to that revision. It was reconstructed from the publisher commit API and verified against its Git blob and tree. Checked on 2026-10-17 UTC.
The publisher renamed this skill in a commit dated 2026-08-06. This listing retains its original catalog name and install identifier; compatibility of that old install identifier is untested. Companion files, research claims and third-party functionality were not independently verified; commands were not executed.
Ambient Computing & Calm Technology — Designing the Invisible Interface
Why Calm Technology Is the Next Design Frontier
The dominant paradigm of digital design for the past four decades has been the screen. Rectangles of light demanding focal attention, pulling users out of their physical context, and competing for the scarcest resource in modern life: human attention. The average person checks their phone 144 times per day. Each check is a context switch. Each context switch carries a cognitive tax. The aggregate cost is a civilization perpetually distracted by the tools that were supposed to serve it.
Calm technology inverts this paradigm. Instead of demanding that humans attend to technology, calm technology attends to humans. It moves information processing from the center of attention to the periphery, from the foreground to the background, from explicit interaction to implicit awareness. The thermostat that adjusts itself. The hallway light that brightens as you approach and dims as you leave. The watch face that shifts color to indicate air quality without requiring a glance at a number. These are not lesser interfaces. They are more mature ones.
Mark Weiser and John Seely Brown articulated this vision at Xerox PARC in 1996: "The most profound technologies are those that disappear. They weave themselves into the fabric of everyday life until they are indistinguishable from it." Three decades later, the hardware exists — ubiquitous sensors, edge computing, low-power wireless, ambient displays, spatial audio. The missing piece is design methodology. How do you design an interface that users never consciously look at? How do you make invisible technology discoverable? How do you provide intelligence without surveillance?
This skill provides the principles, patterns, and evaluation frameworks for designing technology that respects attention rather than hijacking it.
Amber Case and the Principles of Calm Technology
Amber Case's framework, building on Weiser and Brown's foundational work, codifies eight principles that define whether a technology qualifies as calm. These are not aesthetic preferences. They are functional criteria that determine whether a system amplifies human capability or diminishes it.
The principles operate across a spectrum of attention engagement. A calm technology should require the minimum attention necessary to deliver its value. It should communicate through ambient channels — peripheral vision, background sound, haptic rhythm — before escalating to focal attention. It should amplify the user's existing abilities rather than creating new dependencies. And it should function even when it fails, degrading gracefully rather than catastrophically.
Case's key insight is that calm technology is not about simplicity for its own sake. A jet cockpit is profoundly complex, but its information hierarchy is designed for peripheral scanning with focal attention reserved for anomalies. That is calm design applied to a high-stakes context. Complexity is acceptable. Unnecessary demand on focal attention is not.
For the full enumeration of all eight principles with modern application examples, evaluation criteria, and anti-patterns, see references/calm-technology-principles.md.
The Attention Spectrum: Center, Periphery, Background
Human attention operates on a continuous spectrum, not a binary switch. Interface design has historically treated attention as either "on" (the user is looking at the screen) or "off" (the user is not). Calm technology recognizes at least three distinct zones, each with its own design vocabulary.
Center of attention is focal, conscious engagement. Reading a text message, typing a search query, examining a chart. Traditional screen-based UI lives here. The user is actively processing information, and the interface has their full cognitive bandwidth. This zone is expensive — it monopolizes working memory, blocks parallel task execution, and fatigues quickly. Reserve it for tasks that genuinely require conscious decision-making.
Peripheral attention is awareness without focal engagement. A clock on the wall. A weather widget at the edge of a desktop. An LED on a router that glows green when the connection is healthy and red when it is not. The user registers information from the periphery without shifting cognitive focus from their primary task. This zone is efficient but limited — it can communicate status, trends, and binary states, but not nuanced data requiring interpretation.
Background processing is fully automated, requiring zero human attention under normal conditions. The spam filter that silently discards junk email. The smart thermostat that adjusts temperature based on occupancy patterns. The phone that switches between Wi-Fi and cellular without notification. Background systems should surface to peripheral attention only when an anomaly occurs, and escalate to focal attention only when user intervention is required.
The design challenge is building systems that place information at the correct point on this spectrum and transition smoothly between zones as context changes. A home security system operates in the background during normal conditions, shifts to peripheral (a subtle chime when a door opens during the day), and escalates to focal (an alarm and phone notification for unexpected entry at night). The transitions are as important as the states.
See cognitive-psychology-ux for the underlying attention science — selective attention, divided attention, sustained attention, and inattentional blindness — that explains why this spectrum matters.
Zero-UI Patterns
Zero-UI is the design of interactions that require no explicit screen-based interface. The user does not tap, swipe, click, or type. Instead, the system senses context and acts, or communicates through non-screen channels.
Proactive notifications deliver information before the user asks. "Leave now to arrive on time given current traffic." "Your package will arrive in 20 minutes." "The air quality outside has dropped — close the windows." Proactive notifications succeed when they are timely, actionable, and infrequent enough to maintain trust. They fail when they devolve into a stream of irrelevant alerts that train users to ignore them.
Ambient displays communicate data through environmental change rather than screen content. A lamp that shifts from blue to amber as the workday progresses. An e-ink panel on the kitchen wall showing the family calendar. A desktop device that raises or lowers physical bars to represent stock portfolio performance. Ambient displays work because they exploit peripheral vision — the information is always available but never demands focus.
Voice-first interfaces remove the screen entirely and communicate through natural language. The critical design constraint is working memory: a screen can present 20 options simultaneously, but a voice interface can present three before the user forgets the first. Voice-first design requires aggressive content hierarchy, confirmation patterns, and graceful fallback to screen when complexity exceeds what speech can carry. See ai-spatial-voice-ux for comprehensive voice interaction patterns.
Gesture-based interfaces use body movement as input without touching a device. Waving to dismiss, pointing to select, approaching to activate. Gesture systems must solve discoverability (how does the user know which gestures are available?) and false-positive filtering (distinguishing intentional gestures from incidental movement). See interaction-motion-design for gesture design patterns.
Haptic communication uses vibration, pressure, and texture to convey information through touch. A phone that delivers distinct vibration patterns for different notification types. A steering wheel that vibrates directionally for navigation. A wearable that squeezes the wrist gently to prompt a breathing exercise. Haptic design is constrained by a limited vocabulary — humans can reliably distinguish only a handful of vibration patterns — but its intimacy and privacy make it uniquely valuable for personal alerts in public contexts.
Ambient Computing Contexts
Ambient computing is not a single product category. It is an architectural approach that manifests differently across environments.
Smart home environments orchestrate lighting, climate, security, entertainment, and appliances around occupant behavior. The design priority is household harmony — multiple users with different preferences sharing a single environment. Conflict resolution patterns (whose temperature preference wins?), guest modes (how does the home behave for visitors without accounts?), and graceful degradation (what happens when the internet goes down?) are the defining design challenges.
Smart office environments optimize productivity, comfort, and resource efficiency. Meeting rooms that auto-configure AV equipment based on the calendar invite. Desk lighting that adapts to individual preference as the user sits down. Occupancy-aware HVAC that heats only floors with people on them. The design challenge is balancing personalization with shared-space constraints and maintaining privacy in an employer-monitored environment.
Automotive interfaces operate under the most extreme attention constraint: the driver's eyes and hands are occupied with a life-critical task. Every interface element must be evaluated against the question, "Can this be communicated without the driver looking away from the road?" Head-up displays, spatial audio navigation cues, haptic seat alerts, and voice interaction are the appropriate modalities. Touchscreens for driving functions are a calm technology anti-pattern — they demand focal attention in a context where focal attention must remain on the road.
Wearable interfaces live on the body and compete for the smallest screen real estate in computing. Glanceability is the supreme design value: if the user cannot extract the information in under two seconds, the interface has failed. Complications (small data widgets on a watch face), haptic alerts, and voice interaction are the primary patterns. Extended reading, complex navigation, and multi-step forms are hostile to the wearable context.
Public space interfaces serve transient, anonymous users in retail, transit, healthcare, and urban environments. Wayfinding signage, queue status displays, environmental indicators, and interactive kiosks must communicate to people who have no training, no account, and no patience. Accessibility is not a feature — it is the fundamental requirement, because the user population is maximally diverse. See accessibility-inclusive-design for universal design principles that apply directly to public ambient interfaces.
The Discoverability Paradox
The central design tension of calm technology is the discoverability paradox: the better an interface disappears, the harder it becomes for users to discover its capabilities, understand its behavior, and maintain a sense of control.
An invisible interface that users do not know exists cannot be trusted, configured, or debugged. A thermostat that silently adjusts temperature is delightful until the user feels cold and has no idea why the system chose that temperature, how to override it, or whether it is even functioning.
Resolving this paradox requires layered disclosure. The system operates invisibly by default, but provides clear pathways to visibility when the user seeks them. A subtle indicator (a gentle glow, a status light, a soft chime) communicates that the system is active. A simple interaction (tapping the device, saying "why did you do that?", opening a companion app) reveals the system's reasoning and controls. An advanced interface (settings, automation rules, activity logs) provides full transparency and configuration.
The principle is: invisible by default, transparent on demand, configurable when desired.
See agentic-ai-generative-ux for related patterns around AI agent transparency and user control — the challenge of making autonomous system behavior understandable applies equally to AI agents and ambient computing systems.
Privacy in Ambient Computing
Ambient computing requires sensing. Sensing requires data collection. Data collection in the spaces where people live, work, sleep, and have private conversations creates surveillance risk that is categorically different from voluntarily opening an app.
The design obligations are severe. Always-listening devices must provide unambiguous physical indicators of their listening state — a hardware LED that cannot be overridden by software. Always-watching cameras must have physical shutters. Location-tracking systems must offer genuine opt-out that does not degrade core functionality into uselessness. Data minimization must be architectural, not policy-based: process data locally, extract only the minimum signal needed, and discard raw sensor data immediately.
Transparency indicators — visual, auditory, or haptic signals that communicate when the system is sensing, processing, or transmitting data — are not optional features. They are ethical requirements. A smart speaker that transmits audio to a cloud server without a visible indicator is not a calm technology. It is a surveillance device with a consumer-friendly shell.
The "creepy line" — the boundary between helpful and invasive — is subjective, cultural, and shifts over time. Design for the most privacy-sensitive user in the household, not the least. Make the default behavior conservative and the expanded capability opt-in. Never assume consent from convenience.
See ux-ethics-content-strategy for the broader ethical framework around data collection, consent, and dark patterns in ambient contexts.
Evaluation Frameworks for Calm Technology
Evaluating calm technology requires different metrics than evaluating screen-based interfaces. Task completion time and click-through rates are meaningless for a system designed to operate without user interaction.
The Calm Technology Scorecard evaluates a system across Case's eight principles, rating each on a scale from "violates" through "neutral" to "exemplifies." A system that scores well delivers its value with minimal attention demand, communicates through appropriate channels on the attention spectrum, and degrades gracefully.
The Attention Budget Audit quantifies how much focal, peripheral, and background attention a system demands across a typical usage day. Map every notification, status indicator, alert, and interaction to an attention zone and duration. Sum the totals. If a "background" system is demanding more than a few seconds of focal attention per day, it has failed at being calm.
Ambient UX Heuristics adapt Nielsen's classic heuristics for non-screen contexts. Visibility of system status becomes "ambient awareness of system state." User control and freedom becomes "override and opt-out without breaking functionality." Consistency and standards becomes "predictable behavior across contexts and times."
For the complete evaluation frameworks with scoring templates and worked examples, see references/calm-technology-principles.md.
Cross-References to Other Skills
Ambient computing and calm technology intersect with nearly every other discipline in this plugin:
- ai-spatial-voice-ux: Voice interaction is a primary modality for zero-UI systems. Spatial audio is a key ambient communication channel. The AI agent patterns for autonomous action and user oversight directly parallel ambient computing's challenge of invisible automation.
- interaction-motion-design: Motion and animation serve as peripheral communication channels. Micro-interactions provide feedback in ambient displays. Gesture design is fundamental to screenless interaction.
- accessibility-inclusive-design: Ambient interfaces must serve users with visual, auditory, motor, and cognitive differences. Multi-sensory communication (visual + auditory + haptic) is both an ambient design principle and an accessibility requirement. Universal design and calm design share the same goal: technology that works for everyone without demanding special effort.
- agentic-ai-generative-ux: AI agents that act autonomously face the same discoverability and trust challenges as ambient systems. Transparency patterns, approval gates, and progressive autonomy models apply to both domains.
- cognitive-psychology-ux: The attention spectrum, working memory limitations, peripheral perception, and the science of interruption all provide the cognitive foundation for calm technology design.
How to Use This Skill
When Claude Code activates this skill in response to an ambient computing or calm technology trigger, it will draw from:
- This overview for conceptual framing, the attention spectrum model, zero-UI pattern vocabulary, and cross-skill connections
- calm-technology-principles.md for Amber Case's eight principles with modern examples, ambient display patterns, proactive intelligence UX, smart environment design, privacy frameworks, peripheral attention design, evaluation scorecards, and anti-pattern identification
Use these resources to evaluate whether a proposed system qualifies as calm technology, design ambient interfaces that communicate without demanding attention, audit existing products for attention cost, navigate the privacy challenges inherent in always-on sensing, and build evaluation criteria for ambient computing projects.
Publisher license and attribution
The following LICENSE and NOTICE were obtained from the current publisher repository on 2026-10-17 UTC; their presence in the initial revision is not asserted. Apache-2.0 does not grant trademark rights or imply publisher endorsement.
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 Phazur Labs LLC
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
NOTICE
Sumi
Copyright 2026 Phazur Labs LLC
This product includes software developed at Phazur Labs LLC (https://phazurlabs.com).
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--------------------------------------------------------------------------------
The Apache License, Version 2.0 does not grant permission to use the trade
names, trademarks, service marks, or product names of Phazur Labs LLC. See
TRADEMARKS.md for the trademark policy governing this project.