alexanderop/aop-mode

aop-mode

Explicitly invoke the complete original pstack workflow, adapted for Claude Code, Codex, or Copilot. Use only when the user requests aop-mode.

principle-build-resilient-pwas

Apply only when building, improving, or reviewing a Progressive Web App (PWA): preserve the core journey through offline use, installation, and updates. Ordinary responsive websites and native apps are outside this principle.

principle-design-calm-interfaces

Apply when designing, implementing, or reviewing UI appearance and interactions. Build calm interfaces with deliberate hierarchy, restrained color, and consistent spacing and states.

principle-design-mobile-first

Apply when designing, implementing, or reviewing responsive web experiences. Start with the essential task under mobile constraints, then enhance for space and capabilities.

principle-test-at-the-right-layer

Apply when setting up frontend testing, implementing a feature, fixing a bug, or reviewing coverage. Choose tests by the behavior and failure they must expose.

asd

Restate the last answer using ASD-STE100 Simplified Technical English principles.

improve-codebase-architecture

Find architectural friction in an existing codebase and present ranked improvements in a visual report. Use when explicitly asked to survey the architecture or find refactoring opportunities.

visual

Turn the previous answer or a requested topic into a dark HTML blog-style explainer with diagrams and Shiki-highlighted code, then open it in the browser.

principle-isolate-features

Apply when organizing business capabilities or changing feature dependencies. Keep sibling features independent, compose workflows in the application, and enforce import boundaries.

principle-functional-core

Apply when business decisions are mixed with I/O, expected failures are hidden in exceptions, or state flags permit impossible combinations. Model decisions as data and compose pure TypeScript functions.

principle-compose-ui-variants

Apply when UI variants duplicate shared behavior or accumulate props that select different component trees. Let consumers compose the parts they need.

principle-make-dependencies-explicit

Apply when designing code with time, randomness, persistence, network, or service dependencies, or when tests need to replace them. Make dependencies explicit without unnecessary abstraction.