Azhi-ss

This sub-skill offers custom HTML editing interfaces for 'operate and export' tools like triage boards, feature flag editors, and prompt tuners. Each editor must have a 'Copy Result' button to return the UI state to the agent, loading when the parent skill routes relevant requests.

This sub-skill manages prototypes and clickable flows. It's used when a user needs to determine transition duration/easing (via an animation sandbox) or test the feel of a 4-6 screen interactive flow, loading when the parent skill routes requests for animation, prototype, feel, or clickable flows.

Sub-skill: Keyboard-controlled slides. Ideal for meetings where the user needs "ready-to-present" slides in a single HTML file, without Keynote/PPT/Google Slides, navigable by arrow keys. Activated by requests like "slides" or "slide deck".

This Periodic Reports sub-skill is used to generate weekly status reports (KPIs, shipped, velocity, carryover) or incident postmortems (timeline, root cause, impact, action items). It loads when the parent skill detects requests such as 'weekly report', 'status report', 'postmortem', or 'incident'.

This sub-skill is used for illustrations and diagrams, including SVG illustration sets for blogs/documents, flowcharts, state machines, and deploy pipelines. All figures are generated with inline SVG, without external libraries, and it loads when the parent skill routes diagram visualization requests.

This skill enables the agent to output spatial, parallel, comparable, or interactive content using single-file HTML instead of Markdown. It acts as a router, using a decision framework to determine HTML usage and dispatching to one of 9 sub-skills for requests like comparison, planning, review, reporting, interpretation, slides, editing, or visualization, reusing templates to produce runnable artifacts.

This sub-skill manages design systems and component display. It's used for extracting design tokens for team reference or reviewing component variants on a contact sheet, covering design system references (e.g., design-tokens.html) and component variant displays. It activates for requests like "design system", "design tokens", "component variants", or "display component library".

The "Exploration and Planning" sub-skill is used when users need to decide between multiple implementation/design options or write an engineering RFC. It offers paradigms like three-scheme comparisons (compare.html), visual design directions, and implementation plans (plan.html), loading when the parent skill html-effectiveness handles "comparison/selection/RFC/plan" requests.

Research and Learning sub-skill. Activated when the user asks 'How does X work in this repo?' (with TL;DR, steps, and FAQ) or requests an explanation of an abstract concept (with interactive visualization). It loads when the parent skill detects requests like 'explain', 'teach me', or 'learn'.

This sub-skill, 'Code Review and Understanding,' is for PR reviews, PR writing (author side), or understanding unfamiliar code module request paths/call stacks. It includes PR review (diff.html), PR writing (pr.html), and module diagrams, loading when parent skill routes match 'review/PR/audit/how this code works' requests.