superliaye
- 33 skills
- 0 followers
- 1 hour ago last updated
- ▌ E2e Validate · superliaye bundleStack-aware end-to-end validation. Discovers the repo's test/build harness, runs the closest smoke recipe, and verifies a change against declared success criteria — including UI feature visibility via screenshots. Use when verifying that code changes actually run and fulfill their requirements, or when the user asks to validate/smoke-test a change. Usable standalone or as a reviewer leaf inside an orchestrated loop.
- ▌ Design Critique · superliayeGet structured design feedback on how a UI looks — visual hierarchy, typography, spacing, color, consistency, polish. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
- ▌ Loop Build · superliaye bundleDay-to-day build flow. The resident confirms plan intent plus a sparse acceptance contract, hashes the exact contract, then spawns a build agent that may refine implementation hypotheses while gating review on bound acceptance and source-state evidence. It handles contract defects, UI critique, conditional code review, and feedback. Use for /loop-build, an agreed plan, or resuming after planning.
- ▌ Loop Retro · superliayeSession retrospective that mines the current session — the main transcript plus every subagent transcript — for concrete ways to improve the kit capabilities (skills/agents) that ran. Spawns a retro agent to read the large transcripts off the resident's context and write its findings to a per-run file: per capability, what worked and where its instructions caused friction, each tied to transcript evidence. Edits no code or capability. Auto-runs at the end of a /full-loop-* flow, or invoke directly after a session that exercised kit skills/agents.
- ▌
- ▌ My Port Code · superliayeKeep code moves and refactors focused, with disciplined changes to imports, documentation, and comments.
- ▌ Product Critique · superliayeGet structured feedback on how a product is used — task flows, friction, first-time comprehension, the job it does, value delivery, error recovery, information architecture. Trigger with "critique this flow", "is this usable?", "where will users get stuck?", or when sharing a feature/flow for a usability read.
- ▌ Critique Committee · superliayeCritique a UI on both axes at once — a committee of the design-critic (how it looks) and the product-critic (how it's used) run in parallel, with findings presented grouped by lens. Use for "critique committee", "full critique", "review this design and its usability", when both critic agents are installed.
- ▌ Loop Plan Manual · superliaye bundleA human-in-the-loop plan.md + sparse acceptance.md authoring flow before /loop-build. It runs parallel research, puts every release decision to the human through /grill-with-docs, defers evidence-dependent mechanisms as plan hypotheses, and reviews the artifacts before stopping with exact paths. Use for /loop-plan-manual or a fully human-decided plan before building.
- ▌
- ▌ Grill To Design Doc · superliaye bundleGrills a feature or architecture design by delegating the interrogation to /grill-with-docs, then writes a design-doc deliverable modeled on a full feature-design template. Use when the user says "grill my design", "write a design doc", "design doc for <feature>", or wants to stress-test a feature/architecture in the design phase before building.
- ▌ Calibrate System Prompt · superliayeCalibrate an AI agent's system prompt and tool/function descriptions in any repo and for any model provider. Reads the full prompt plus every tool definition, makes surgical edits that SHRINK net token count without weakening behavior, then spawns parallel reviewers to confirm nothing breaks and the size actually dropped. Use when: "calibrate the system prompt", "this tool/function description is too verbose", "trim the agent prompt", "the agent keeps misusing tool X", "tune the prompt instructions", "reduce prompt tokens". Not for: adding new capabilities to a prompt, writing new skills, or debugging a live production incident.
- ▌ Loop Plan Semiauto · superliayeA minimal-human plan.md + sparse acceptance.md authoring flow before /loop-build. It runs parallel research, lets a three-lens committee resolve release decisions when unanimous, defers evidence-dependent mechanisms as plan hypotheses, and reviews the artifacts. A split, an "Other" vote, or a proposed semantic acceptance change escalates to the human. It stops with exact artifact paths. Use for /loop-plan-semiauto or a plan with minimal human interaction.
- ▌ Grill With Committee · superliayeA semi-automated grilling session: /grilling forms each decision frontier, a three-lens committee resolves answers when unanimous, and /domain-modeling captures glossary and ADR effects. Any split or "Other" vote escalates to the human. Standalone it writes a per-run grill.md digest with committee or human provenance. Use for a minimal-human stress test or as /loop-plan-semiauto's grill phase.
- ▌ My Slidev · superliayeAuthor or fix a Slidev slide deck with an autonomous export-and-verify loop. First it shapes the talk — a narrative arc and a slide-by-slide breakdown of what each slide proves — then delegates the drawing to my-slidev-agent, which drafts Slidev markdown, exports each slide to PNG, reads the images back to catch code spilling off the slide, clipped or overlapping text, an overfull slide, or a blank render, and gates on a two-axis acceptance (truth vs the source, projected-slide readability) before returning. Use when building or improving a slide deck, turning a talk outline or repo code into slides, or when a deck has slides that overflow, clip, or render blank.
- ▌ Newspaper · superliaye bundleMaintain a live, editable newspaper-style canvas for meaningful progress, decisions, risks, findings, code, tables, metrics, and local media during a long-running task.
- ▌ My Aggressive Clean Up · superliayeAggressively remove the dead code left behind after a feature flag, killswitch, experiment flight, or any conditional code path is retired — the orphaned state, types, variables, imports, styles, and comments that existed only to serve the removed branch, plus the repo-wide footprint (duplicate flag checks, now-constant arguments, dead consumer-side reads). Headlines the wrong-branch hazard: which side survives depends on the flag's polarity and terminal value. Use after graduating/retiring/removing a flag or collapsing a conditional, or when asked to clean up thoroughly after a code path is removed.
- ▌ Loop Review Committee · superliayeReviews a committed or worktree change through the applicable subset of five separate lenses — architecture, documented rules, correctness, spec conformance, and Fowler smells. Pins one immutable review payload, reports every run/skip decision, runs selected reviewers in capacity-aware parallel batches, and keeps their findings grouped by lens. Use for a multi-perspective code review, committee review, or non-interactive review from /loop-build.
- ▌
- ▌ Illustrate · superliayeCreate a visual explanation that lets a reader grasp something fast — a code change, a system, a concept, a plan, or data. Defaults to low fidelity, such as a one-screen poster, and goes deeper when asked. Use when the user asks to illustrate or visualize something, explain it visually, or show what changed.
- ▌ My Mermaid · superliayeAuthor or fix a Mermaid diagram with an autonomous render-and-verify loop. First it picks the diagram type that fits the source — it names the shape of the information and chooses from the live Mermaid catalog instead of defaulting to a flowchart — then delegates the drawing to my-mermaid-agent, which drafts render-safe Mermaid, renders headlessly to a PNG (the engine native VSCode uses), reads the image back to fix clipped or overlapping labels, and gates on a two-axis acceptance (truth vs the source, human readability) before returning. Use when creating or improving a Mermaid diagram, deciding which diagram type best fits, or when a diagram has cut-off text or is hard to read.
- ▌ My Present · superliayeCreate, revise, or review a presentation, slide deck, talk script, or announcement for any audience. Use when the user asks to make, update, restructure, or critique slides, a deck, a talk, speaker notes, or an announcement or update post.
- ▌ Project Sync · superliayeSynchronizes project tracker statuses and concise weekly updates from Jira and linked Slack, pull requests, and documents, using changes since the previous sync. Use when the user wants to refresh a delivery tracker before a meeting or remove manual source-to-tracker synchronization.
- ▌ Project Review · superliayeReviews a project delivery tracker for risks, missing work, dependency problems, and decisions that need attention. Use when the user wants a project-level assessment, a meeting decision brief, or an explanation of what could prevent a deliverable from succeeding.
- ▌ My Dissolve Doc · superliayeDissolve a finished one-time doc — an ADR, PRD, plan, spec, design note, or handoff whose work has already shipped — by relocating the durable knowledge it still holds (decisions, rationale, gotchas, domain terms) into permanent homes next to the code, dropping what the code already records or was only build scaffolding, then removing the stale husk so it can't mislead a later agent. The caller names the target doc; this is the careful teardown. Use when a planning or spec doc has served its purpose and now risks going stale or stealing focus, or when asked to dissolve, retire, or fold away a one-time doc.
- ▌ My Domain Vocab · superliaye bundleVocabulary trainer that builds a non-native English speaker's working vocabulary of their field from documents they read. Use when the user feeds documents (design docs, Slack, PR comments, transcripts) to learn their terms, wants a vocabulary review session, or asks to inspect, fix, or undo their vocabulary state.
- ▌ Loop Check Readiness · superliayeRead-only audit of whether a coding agent can actually get a fast, deterministic, agent-runnable feedback loop in a repo — judging both what the repo affords (tests, build, type-check, lint, CI, and a reachable, drivable UI for visual checks) and whether the agent can close that loop unattended with the tools and skills it has (no interactive auth, human clicks, or non-headless steps). Reports gaps and opportunities with a remediation for each; it inspects and reports only, changing no files and building no loop. Use when starting work in an unfamiliar repo, when the user asks whether a project is set up for success or has a good feedback loop, or to audit or grade its feedback signals before relying on an agent loop.
- ▌ Serenity Chokepoint Market Research · superliaye bundleSource-grounded research operating system for analyzing markets, value chains, and companies by finding durable supply-chain chokepoints. Distilled from the public posts of Serenity (@aleabitoreddit). Use when researching an industry, supply chain, or potential investment theme to locate where physical/technical/regulatory bottlenecks create asymmetric, mispriced exposure. NOT a trading signal.
- ▌ Web Visual Loop · superliaye bundleAutomate and visually verify a browser-rendered web UI using agent-browser via Chrome DevTools Protocol. Built for the local edit→reload→re-verify dev loop, but the connect + verification spine work against any URL (local, staging, production). Use when iterating on a UI and wanting a visual feedback loop, or to verify that a route renders, a flow works, or a page didn't regress. Triggers include "visual feedback loop for the web app", "screenshot the dev server", "verify the UI renders", "test this route", "iterate on the design".
- ▌ Desktop App Loop · superliaye bundleAutomate and visually verify an ARBITRARY foreign desktop app you did NOT build and did NOT launch in debug mode (e.g. the OpenAI Codex desktop app). A tiered, best-fidelity-first recipe — CDP relaunch, then OS-native accessibility read-back, then a vision computer-use fallback — for clicking through a packaged app's UI and reading back state with no cooperation from the app. Model-agnostic and OS-agnostic (Windows + macOS). Use when the user needs to drive or test a third-party/packaged desktop app, read a setting back from a foreign GUI, automate an app with no remote-debugging port, "control Codex app", "test this desktop app I didn't build", "read back a dropdown selection from a native app", or when electron-visual-loop fails because you don't control the launch.
- ▌ Prepare Peer Feedback · superliayeSearch your enterprise data to find and summarize the concrete things you worked on with a specific colleague, so you can recall context before writing feedback. Use when the user wants to recall what they collaborated on with a target person — for peer feedback, performance reviews, 360s, or connects — and needs an evidence-backed summary of meetings, emails, chats, files, decisions, and action items grouped by project or theme.
- ▌ Project Tracker Update · superliayeCreates and maintains project delivery trackers in Google Sheets from project scope, documents, and requested changes. Use when the user wants to create a tracker, add or restructure deliverables and work items, change project classifications, or apply planning decisions to an existing tracker.
- ▌ Electron Visual Loop · superliaye bundleAutomate and visually verify Electron desktop apps using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, set up a visual feedback loop for an in-development Electron renderer, automate a desktop app (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.), connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", "visual feedback loop", "screenshot the Electron window", or any task requiring automation of a native Electron application.