Applies first-principles, multi-order consequence analysis, inversion, systems thinking, probability, antifragility, and high-energy thrive ascent (2036 lens) before material coding decisions (architecture, dependencies, public API, security, data contracts, hard-to-revert refactors). Use when choosing between approaches, planning cross-cutting changes, or when the user asks for decision analysis, tradeoffs, pre-mortem, second-order effects, or thrive vision.
Load and maintain the shellyxz shell kernel ontology graph — PATH contract, kernel/plugin boundary, load order, and verification bridge (ab/av/at). Use when editing ~/.config/shell core/, plugins/verification/, bin shims, moving files across the kernel boundary, or answering where a concept lives.
Authors evidence-driven architecture backlog docs (coming-next style): scorecards, mermaid diagrams, blueprint cards SN-*, thrive vision, gantt order. Use when creating or updating roadmaps, arch-design/coming-next.md, backlog after PRs, or when the user wants blueprint cards, Musk 5-step, or optimistic 10-year plans. Pairs with ai-optimization, fusion-sage, and higher-order-decision-architect.
Generates project-specific tmux verification cockpits for repos that use an av-style agent verify workflow. Reads target project AGENTS.md, setup docs, and scripts; writes .agents/verification/ with SOC-style panes and tiered auto-launch. Use when setting up av layouts, mission-control verify panes, or regenerating .agents/verification after stack changes.
Peramanathan Sathyamoorthy's senior ML/AI systems engineering principles — first principles thinking inspired by Feynman and Musk, Machine First architecture, strong mathematical and physics foundations, rapid practical learning through clean iteration, deep systems capability, clear language, extensibility, and uncompromising quality.
Overarching patterns for self-guarded, pause-aware, agent-driven desktop/web platforms. Combines finder-reactor, Tauri shell, X resources, and CV guard into a cohesive autonomous system with intervention only on guards. Use for high-level autonomy design, meta-improvement loops, MCP composability. Fusion for the reactor as living system; fission for specific guards.
Manifest V3 Chrome extension development — service worker lifecycle, message passing (popup ↔ service worker ↔ content script), content script injection, and host_permissions fetch patterns. Use when editing manifest.json, background/service worker, popup, content scripts, chrome.runtime.sendMessage, or extension permissions.
Strict self-guarded mechanism for reading an external CV source (e.g. cvdata.json in a portfolio repo) for grounding and safely promoting insights back with sidecars, diffs, previews, backups, and explicit user confirmation. Never mutates external profile without multiple gates. Use for CV-related logic in finder-reactor or prep flows. Sidecar-first, auditable, intervention points. Fission for safe edit code; fusion for protecting the public profile while improving future matches.