ApertureOscillation

Surface design tensions across narrow, wide, and synthesis passes.

1|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/starlink-awaken/pai-universal --skill apertureoscillation-starlink-awaken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ApertureOscillation
Source: https://github.com/starlink-awaken/pai-universal/tree/main/templates/packs/ApertureOscillation/src
Command: npx skills add https://github.com/starlink-awaken/pai-universal --skill apertureoscillation-starlink-awaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ApertureOscillation surfaces design tensions by holding a question constant and varying the scope across three structured passes to surface tensions invisible at any single zoom level.

Core Features & Use Cases

  • Three passes: narrow (tactical), wide (strategic), and synthesis to surface divergences.
  • Two inputs: tactical target and strategic context, enabling alignment between local logic and system-wide goals.
  • Outputs: design tensions, coherence assessment, and ISC implications for architecture decisions.
  • Use cases: architecture decisions, feature design, and system coherence checks within larger platforms.

Quick Start

Provide a tactical target and a strategic context, then run the three-pass aperture oscillation workflow to surface design tensions.

Frequently Asked Questions about ApertureOscillation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify design tensions between local component logic and system-wide architecture?

Aperture oscillation surfaces design tensions by holding a question constant and varying the scope across three structured passes. It aligns local component logic with system coherence by evaluating a tactical target against its strategic context.

What is the best way to check system coherence before making architecture decisions?

Checking system coherence requires running a three-pass workflow across narrow, wide, and synthesis scopes. This process documents divergences between tactical targets and strategic contexts to output integrated tensions and ISC implications.

How do I structure an ai-design workflow to surface hidden architecture divergences?

Structure the ai-design workflow by providing a tactical target and a strategic context as inputs. The workflow then executes narrow, wide, and synthesis passes to document divergences and surface design tensions invisible at any single zoom level.

Can I use aperture oscillation for feature design within larger platforms?

Yes, aperture oscillation works for feature design and system coherence checks within larger platforms. It evaluates the tactical target against the strategic context to output coherence assessments and ISC implications for architecture decisions.

When do I need a structured three-pass workflow for evaluating design tensions?

A structured three-pass workflow is needed when aligning local component logic with system-wide goals to surface design tensions. It enforces documentation of divergences across narrow, wide, and synthesis scopes to produce integrated recommendations.

Why does evaluating a single scope fail to surface certain design tensions?

Evaluating a single scope fails because design tensions often remain invisible at any single zoom level. Aperture oscillation solves this by holding the question constant and varying the scope to surface divergences between tactical and strategic contexts.