ulpi-io
- 913 skills
- 0 followers
- 15 repo stars
- last month last updated
- ▌ Azure Infra Engineer · ulpi-io bundleExpert in Microsoft Azure cloud services, specializing in Bicep/ARM templates, Enterprise Landing Zones, and Cloud Adoption Framework (CAF).
- ▌ Codebase Exploration · ulpi-io bundleDeep contextual grep for codebases. Expert at finding patterns, architectures, implementations, and answering "Where is X?", "Which file has Y?", and "Find code that does Z" questions. Use when exploring unfamiliar codebases, finding specific implementations, understanding code organization, discovering patterns across multiple files, or locating functionality in a project. Supports three thoroughness levels quick, medium, very thorough.
- ▌ Git Workflow Manager · ulpi-ioGit workflow and branching strategy expert. Use when establishing team collaboration patterns, optimizing commit practices, or designing scalable version control workflows for better developer experience.
- ▌ Mobile App Developer · ulpi-ioExpert in cross-platform mobile development (React Native/Flutter), bridging native performance with shared business logic.
- ▌ Digitalocean Storage · ulpi-io bundleDigitalOcean storage services including Spaces object storage, Volumes block storage, NFS, Snapshots, and Backups. Use when selecting or managing storage for DigitalOcean workloads.
- ▌ Phoenix API Channels · ulpi-io bundlePhoenix controllers, JSON APIs, Channels, and Presence on the BEAM
- ▌ Vercel Observability · ulpi-io bundleVercel observability for Web Analytics, Speed Insights, logs, tracing, alerts, and observability tooling. Use when monitoring performance or debugging production behavior on Vercel.
- ▌ Alicloud AI Audio Asr Realtime Test · ulpi-ioMinimal realtime ASR smoke test for Model Studio Qwen ASR Realtime.
- ▌ Alicloud AI Audio Tts Voice Clone Test · ulpi-ioMinimal voice cloning TTS smoke test for Model Studio Qwen TTS VC.
- ▌ Alicloud Security Kms Test · ulpi-ioMinimal smoke test for KMS skill. Validate auth and read-only key listing path.
- ▌
- ▌ Sentry Feature Setup · ulpi-ioConfigure specific Sentry features beyond basic SDK setup. Use when asked to monitor AI/LLM calls, set up OpenTelemetry pipelines, or create alerts and notifications.
- ▌
- ▌ Logo Design Guide · ulpi-ioLogo design principles and AI image generation best practices for creating logos. Covers logo types, prompting techniques, scalability rules, and iteration workflows. Use for: brand identity, startup logos, app icons, favicons, logo concepts. Triggers: logo design, create logo, brand logo, logo generation, ai logo, logo maker, icon design, brand mark, logo concept, startup logo, app icon logo
- ▌ SEO Content Brief · ulpi-ioSEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
- ▌ Baoyu Danger Gemini Web · ulpi-io bundleGenerates images and text via reverse-engineered Gemini Web API. Supports text generation, image generation from prompts, reference images for vision input, and multi-turn conversations. Use when other skills need image generation backend, or when user requests "generate image with Gemini", "Gemini text generation", or needs vision-capable AI generation.
- ▌ Google Search Console · ulpi-ioWhen the user wants to analyze Google Search Console data, use GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "title tag," "meta description," "GSC data analysis," "Search Console API," or "searchanalytics.query."
- ▌ Indie Hacker Strategy · ulpi-ioWhen the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company."
- ▌ Backend Code Review · ulpi-io bundleReview backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
- ▌ Orpc Contract First · ulpi-ioGuide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
- ▌ Flutter Adaptive UI · ulpi-io bundleBuild adaptive and responsive Flutter UIs that work beautifully across all platforms and screen sizes. Use when creating Flutter apps that need to adapt layouts based on screen size, support multiple platforms including mobile tablet desktop and web, handle different input devices like touch mouse and keyboard, implement responsive navigation patterns, optimize for large screens and foldables, or use Capability and Policy patterns for platform-specific behavior.
- ▌ Asc Metadata Sync · ulpi-ioSync and validate App Store metadata and localizations with asc, including legacy metadata format migration. Use when updating metadata or translations.
- ▌ Angular Best Practices · ulpi-io bundleCurated Angular best practices for building performant, maintainable Angular 17+ applications. Covers Signals, RxJS, performance, SSR, testing, forms, routing, and architecture. Library-specific add-ons available for NgRx, SignalStore, TanStack Query, Material, PrimeNG, Spartan UI, and Transloco. Do not use for AngularJS (1.x), React, Vue, or non-Angular TypeScript projects.
- ▌ Knowledge Synthesizer · ulpi-ioExpert in aggregating, processing, and synthesizing information from multiple sources into coherent insights. Use when building knowledge graphs, ontologies, RAG systems, or extracting insights across documents. Triggers include "knowledge graph", "ontology", "synthesize information", "GraphRAG", "insight extraction", "cross-document analysis".
- ▌ Workflow Orchestrator · ulpi-ioExpert in designing durable, scalable workflow systems using Temporal, Camunda, and Event-Driven Architectures.
- ▌ Create Cowork Plugin · ulpi-io bundleGuide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
- ▌ Digitalocean Overview · ulpi-io bundleDigitalOcean platform overview for account setup, projects, tooling (Control Panel, doctl, API, Terraform), and service selection across compute, storage, databases, networking, management, and teams. Use when onboarding or planning DigitalOcean usage.
- ▌ Agent Device · ulpi-io bundleAutomates interactions for iOS simulators/devices and Android emulators/devices. Use when navigating apps, taking snapshots/screenshots, tapping, typing, scrolling, or extracting UI info on mobile targets.
- ▌ Alicloud Data Lake Dlf Test · ulpi-ioMinimal smoke test for DataLake skill. Validate metadata discovery and one read-only API call.
- ▌ Sentry Pr Code Review · ulpi-ioReview a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.
- ▌
- ▌ Background Removal · ulpi-ioRemove backgrounds from images with BiRefNet via inference.sh CLI. Model: BiRefNet (high accuracy background removal). Use for: product photos, portraits, e-commerce, transparent PNGs, photo editing. Triggers: remove background, background removal, remove bg, transparent background, cut out image, background remover, rembg, product photo editing, cutout, transparent png, bg removal, photo cutout
- ▌ Case Study Writing · ulpi-ioB2B case study writing with STAR framework, data visualization, and research. Covers structure, customer quotes, metrics presentation, and distribution formats. Use for: customer success stories, portfolio pieces, sales enablement, marketing content. Triggers: case study, customer story, success story, b2b case study, client testimonial, customer case study, portfolio case study, use case, customer win, results story
- ▌ Brand Visual Generator · ulpi-ioWhen the user wants to define, audit, or apply visual identity (typography, colors, spacing, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font choices," "spacing system," "design tokens," "motion," "distinctive design," or "frontend aesthetics."
- ▌ Contact Page Generator · ulpi-ioWhen the user wants to create, optimize, or audit contact page and forms. Also use when the user mentions "contact page," "contact form," "get in touch," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form."
- ▌ Landing Page Generator · ulpi-ioWhen the user wants to create, optimize, or audit campaign landing pages for paid ads or other traffic. Also use when the user mentions "landing page," "PPC landing page," "SEM landing page," "conversion page," "campaign page," "lead capture page," "landing page optimization," "LP conversion," "single-page funnel," or "squeeze page."
- ▌ Social Share Generator · ulpi-ioWhen the user wants to add, optimize, or audit social share buttons (share article to X, LinkedIn, Facebook, etc.). Also use when the user mentions "share buttons," "social share," "share to X," "share to LinkedIn," "social sharing," "share icons," "share widget," "native share," "Web Share API," or "share intent URLs."
- ▌ Testimonials Generator · ulpi-ioWhen the user wants to add, optimize, or design customer testimonials, reviews, or case study sections. Also use when the user mentions "testimonials," "reviews," "customer quotes," "social proof," "case studies," "testimonial section," "customer reviews," "review schema," "testimonial design," or "social proof section."
- ▌ Trust Badges Generator · ulpi-ioWhen the user wants to add or optimize trust badges, "Trusted by" logos, security seals, or social proof elements. Also use when the user mentions "trust badges," "trusted by," "security badges," "payment logos," "social proof," "trust seals," "SSL badge," "customer logos," "as seen in," or "trust signals."
- ▌ Godot Gdscript Patterns · ulpi-ioMaster Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.
- ▌ Hybrid Cloud Networking · ulpi-ioConfigure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.
- ▌ Openapi Spec Generation · ulpi-ioGenerate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
- ▌ AI Tool Compliance · ulpi-io bundleAutomation skill for designing, verifying, and improving auth, cost, logging, and security compliance based on the internal AI tool mandatory implementation guide (P0/P1). Supports the full lifecycle of RBAC design, Gateway principles, Firestore policy, behavior logs, cost transparency, and the criteria verification system.
- ▌ Database Administrator · ulpi-io bundleSenior Database Administrator with expertise in PostgreSQL, MySQL, MongoDB, and enterprise database systems. Specializes in high availability architectures, performance tuning, backup strategies, and database security for production environments.
- ▌ Documentation Engineer · ulpi-ioTechnical documentation and knowledge management expert. Use when creating comprehensive documentation systems, improving developer knowledge sharing, or building documentation-driven development workflows.
- ▌ Event Driven Architect · ulpi-ioExpert in designing asynchronous, decoupled systems using Event-Driven Architecture (EDA). Specializes in AsyncAPI, Event Mesh, and CloudEvents standards. Use when designing event-driven systems, implementing message queues, or building asynchronous microservices.
- ▌ Refactoring Specialist · ulpi-ioExpert in improving code structure without changing behavior. Specializes in Design Patterns, SOLID principles, and Anti-Corruption Layers.
- ▌ Vercel Security Access · ulpi-io bundleVercel security and access controls including RBAC, SSO, deployment protection, firewall, bot defense, audit logs, and 2FA. Use when securing Vercel projects or managing access.
- ▌ AI Content Pipeline · ulpi-ioBuild multi-step AI content creation pipelines combining image, video, audio, and text. Workflow examples: generate image -> animate -> add voiceover -> merge with music. Tools: FLUX, Veo, Kokoro TTS, OmniHuman, media merger, upscaling. Use for: YouTube videos, social media content, marketing materials, automated content. Triggers: content pipeline, ai workflow, content creation, multi-step ai, content automation, ai video workflow, generate and edit, ai content factory, automated content creation, ai production pipeline, media pipeline, content at scale
- ▌ AI Image Generation · ulpi-ioGenerate AI images with FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image
- ▌ AI Music Generation · ulpi-ioGenerate AI music and songs with Diffrythm, Tencent Song Generation via inference.sh CLI. Models: Diffrythm (fast song generation), Tencent Song Generation (full songs with vocals). Capabilities: text-to-music, song generation, instrumental, lyrics to song, soundtrack creation. Use for: background music, social media content, game soundtracks, podcasts, royalty-free music. Triggers: music generation, ai music, generate song, ai composer, text to music, song generator, create music with ai, suno alternative, udio alternative, ai song, ai soundtrack, generate soundtrack, ai jingle, music ai, beat generator
- ▌ AI Podcast Creation · ulpi-ioCreate AI-powered podcasts with text-to-speech, music, and audio editing. Tools: Kokoro TTS, DIA TTS, Chatterbox, AI music generation, media merger. Capabilities: multi-voice conversations, background music, intro/outro, full episodes. Use for: podcast production, audiobooks, voice content, audio newsletters. Triggers: podcast, ai podcast, text to speech podcast, audio content, voice over, ai audiobook, multi voice, conversation ai, notebooklm alternative, audio generation, podcast automation, ai narrator, voice content, audio newsletter, podcast maker
- ▌ AI Video Generation · ulpi-ioGenerate AI videos with Google Veo, Seedance, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 1.5 Pro, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative
- ▌ Newsletter Curation · ulpi-ioNewsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, and sending cadence. Use for: email newsletters, link roundups, weekly digests, curated content, creator newsletters. Triggers: newsletter, email newsletter, newsletter curation, weekly digest, link roundup, curated newsletter, newsletter writing, newsletter format, subscriber growth, newsletter strategy, content curation, newsletter template
- ▌ AI Product Photography · ulpi-ioGenerate professional AI product photography and commercial images. Models: FLUX, Imagen 3, Grok, Seedream for product shots, lifestyle images, mockups. Capabilities: studio lighting, lifestyle scenes, packaging, e-commerce photos. Use for: e-commerce, Amazon listings, Shopify, marketing, advertising, mockups. Triggers: product photography, product shot, commercial photography, e-commerce images, amazon product photo, shopify images, product mockup, studio product shot, lifestyle product image, advertising photo, packshot, product render, product image ai
- ▌ Rust · ulpi-io bundleWrite and change Rust the way THIS workspace already does it, NOT by generic defaults — a systems-programming reference carrying the real crate boundaries, error model, and conventions for storage engines, binary formats, Arrow/DataFusion, search and vector indexing, async concurrency, testing, and unsafe discipline, so a change lands idiomatic and review-ready instead of merely compiling. Use when a task touches this workspace's Rust crates and should follow its systems-level conventions rather than boilerplate.
- ▌ Lokei · ulpi-io bundlePut local dev surfaces behind trusted HTTPS `.test` domains — real certs and DNS, not localhost:port — with the `lokei` CLI: framework-aware `run`, public tunnels via `share`/`--expose`, `docker up` and `.test.yaml` multi-service orchestration, and `doctor`/`routes`/`logs` diagnostics, backed by a one-time setup that mints and trusts a local CA and wires `.test` DNS and port forwarding. Never auto-runs setup, service-install, or uninstall — those wait for approval. Use for local HTTPS, named domains, tunnel sharing, or lokei diagnosis.
- ▌ Start · ulpi-io bundleRoute the start of substantive work to the right execution path — a lightweight INTERNAL intake pass, not a user-facing command and not a universal constitution. Answers four questions fast: does a more specific skill own this, is specialized agent delegation warranted, what is the minimum context needed to avoid a blind edit, and does the work need DAG planning or can it proceed directly — then states the chosen path in one concise update. Invokes the matching skill instead of merely naming it, gathers only the minimum context (no full capability inventory unless asked), and hands real planning to `plan-to-task-list-with-dag` rather than becoming a planner itself. Use internally at task start when no more specific skill has already matched.
- ▌ Browse · ulpi-io bundleDrive a REAL browser and native apps the way a user would — not fetch raw HTML — through the persistent `browse` CLI: one long-lived headless Chromium (plus iOS, Android, and macOS apps via accessibility APIs) where goto, snapshot, click, fill, JavaScript, and screenshot share session state at ~100ms/command and interaction rides stable @eN refs, not brittle selectors. Use when verifying, navigating, or automating live web or app behavior beyond what code-reading or a raw fetch reveals.
- ▌ Bugfix · ulpi-io bundleFix a CONFIRMED bug at its root cause, smallest correct change only — reproduce before you touch code: write a failing reproducer, diagnose the first broken assumption in the data flow, load the matching framework reference and category playbook, apply the minimal fix, then verify the reproducer goes green and run the regression scope. Never writes fix code without a reproducer (or a documented reason one is impossible), never patches the symptom while the root cause stands, and never weakens a test to pass. Use when the user says "fix this bug", "fix the findings", "/bugfix", or asks to repair a confirmed defect.
- ▌ Commit · ulpi-io bundleCreate one or more intentional git commits from the working tree — grounded in the REAL diff, never a guessed message over blind staging. Reads `git diff HEAD` and branch/log context first, scans the changed files for blockers (secrets, conflict markers, stray or debug artifacts), runs the narrowest relevant checks for the changed surface, stages files EXPLICITLY by name, drafts a Conventional Commit subject, then verifies the resulting hash and any leftover working-tree state. Never `git add -A`/`.`, `--no-verify`, `--amend`, or co-author trailers unless asked; stops on secrets or conflict markers and asks before an ambiguous split rather than reporting a clean tree that isn't. Use only when the user explicitly asks to commit.
- ▌ Docker · ulpi-io bundleWrite and change container infrastructure the way THIS project already builds and ships it, not by generic defaults — a Docker reference carrying the real conventions for Dockerfiles, multi-stage builds, Compose services, networking, volumes, health checks, registries, BuildKit, security hardening, CI/CD integration, and debugging. Holds the invariants that keep images small and safe: multi-stage builds, non-root runtime, pinned base images, no baked secrets, a mandatory .dockerignore, and frozen lockfiles — so an image lands small, secure, reproducible, and review-ready instead of merely building. Use when a task touches container configuration, images, or deployment infrastructure.
- ▌ Nestjs · ulpi-io bundleBuild NestJS the way THIS project's module architecture already does it, not by framework defaults — a reference carrying the real module boundaries and dependency-injection discipline behind thin controllers, class-validator DTOs, TypeORM/Prisma data access, guards, interceptors, pipes, exception filters, BullMQ queues, WebSockets, microservices, OpenAPI, and testing, so a change lands idiomatic and review-ready instead of bypassing the framework. Use when a task touches this project's NestJS modules and should follow its DI-driven architecture rather than framework defaults.
- ▌ Nextjs · ulpi-io bundleBuild or review a Next.js App Router surface against the project's installed framework version and established architecture. Covers pages, layouts, async request APIs, server and browser API clients, authentication, client concurrency, Route Handlers, metadata, i18n, accessibility, machine-readable content, and layered testing. Use when a task touches Next.js and must preserve project-specific decisions such as the resolved framework version, backend session protocol, canonical domain, and locked visual theme.
- ▌ Nodejs · ulpi-io bundleWrite Node.js and Bun backend code the way THIS project already does it, not by generic defaults — a TypeScript-first reference that detects the runtime and carries the real conventions for HTTP servers, Zod boundary validation, typed error handling, pino logging, database access, auth, BullMQ queues, caching, async and graceful-shutdown patterns, security, CLI tooling, testing, and observability, so a change lands idiomatic and review-ready instead of merely running. Use when a task touches this project's Node.js or Bun backend and should follow its conventions rather than generic defaults.
- ▌ Codemap · ulpi-ioDiscover code by MEANING and DEPENDENCY structure, not by matching text — with the `codemap` CLI: hybrid vector+BM25 semantic search, symbol lookup, incoming/outgoing dependency tracing, file summaries, PageRank importance, afferent/efferent coupling, and cycle detection over an indexed repo. Only authoritative when the index exists and is fresh — a stale or empty index is called out, not trusted. Use for architecture-aware code discovery instead of plain text search.
- ▌ Laravel · ulpi-io bundleWrite and change Laravel the way THIS project already does it, with Laravel 13 as the recommended baseline for new applications and explicit compatibility handling for existing versions. Carries the real controller/Action/Resource boundaries and conventions for thin controllers, Form Request validation, strict Eloquent, API Resources, Horizon queues, caching, auth, observability, and the Laravel AI/Boost/MCP stack. Use when a task touches this project's Laravel code and should follow its backend conventions rather than generic or outdated framework defaults.
- ▌ Secrets · ulpi-ioManage local service credentials WITHOUT ever exposing their values — the `secrets` CLI adds, rotates, lists, enables, disables, and inspects encrypted integrations (including MCP/agent tooling) through interactive entry, reporting only service names and enablement status. Hard invariant: secret material never enters arguments, logs, or output and `--reveal` is never used — the reporting surface is the service, not the value. Use only on explicit request to wire or inspect credentials.
- ▌ Ast Grep · ulpi-io bundleSearch code by SYNTAX SHAPE, not by text — matching structures grep and regex can't reliably express — with the `ast-grep` CLI: parse to an AST and match with patterns, node kinds, relational rules (`inside`/`has`), and metavariables, inspecting the tree via `--debug-query` and proving the rule on a minimal example before it runs repo-wide. Requires the `ast-grep` CLI; results are spot-checked, not returned as unverified noise. Use when the target is a code structure rather than a literal string.
- ▌ Launch X · ulpi-io bundlePrepare and run a product launch on X (formerly Twitter) end to end — the external link goes in a REPLY, not the main tweet, so reach isn't penalized. Grounds in the real product, then writes a paste-ready package to `.ulpi/launch/x/`: `POST.md` (the launch **thread** — a scroll-stopping hook tweet, the thread body, native media, and the product link in a reply), `PLAN.md` (timing, the **golden-hour** engagement runbook, cross-promotion, and the post-launch plan), and `CHECKLIST.md` (a blocking pre-flight gate). The X runner of the launch-* family: it owns X mechanics, format rules, and the gate, and composes the shared `launch-copy` (thread copy), `launch-outreach` (team amplification, mode `x`), and `launch-analytics` (UTM + conversion tracking), degrading to built-in fallbacks if a companion isn't installed. Reads the shared `.ulpi/launch/positioning.md`. Engagement asks to your own audience are fine (no vote-ring rules), but it avoids what X penalizes — a link in the main tweet, engagement-bait, and bough
- ▌ Browse QA · ulpi-ioTurn a ticket, URL, or plain-language spec into an executed QA run AND reusable regression flows — scenarios and evidence, not ad-hoc clicking — by decomposing the request into happy/error/edge/ exploratory scenarios, driving each against the real target through the `browse` skill (web or iOS/Android/macOS), capturing pass/fail evidence, and recording cleanly-scoped browse flows worth rerunning. Saves a flow only when it is well-scoped and valuable, never noisy half-recordings. Use to QA a feature and leave behind rerunnable coverage.
- ▌ Build Dmg · ulpi-io bundleBuild a distributable macOS DMG from an Xcode project via the bundled local helper — archive → export → package into one signed artifact. Resolves the project/workspace, scheme, team ID, and export options, regenerates the project first when `xcodegen` is detected, then runs `helpers/build-dmg.sh` from the project root instead of inlining xcodebuild. User-only workflow that touches code signing and provisioning: it never GUESSES the signing identity, never overwrites `ExportOptions.plist` without approval, and reports the built DMG path, version, and signing status. Use only when the user explicitly asks to build or package a DMG.
- ▌ Create Pr · ulpi-io bundleOpen a GitHub pull request that matches what the branch ACTUALLY changed — validated against the real base, not the branch name or an optimistic summary. Reads the full diff against the true base branch, blocks on protected-branch/empty-branch/conflict-marker states, invokes `commit` first if the tree is dirty, classifies type/scope/breaking-changes from the diff, runs the narrowest relevant checks, pushes the branch, then creates the PR with `gh` and verifies its number, URL, and state. Never fabricates passing test status or an absent breaking change, and never creates the PR before the branch is on remote; falls back to a prepared title/body/compare URL if `gh` is missing. Use only when the user explicitly asks to open or create a PR.
- ▌ Find Bugs · ulpi-io bundleHunt REAL bugs and security holes in the current branch diff — verified, not a raw model dump: map each changed file's attack and defect surface, run the security-and-logic checklist against it, then verify every candidate against surrounding code, callers, and existing mitigations — runs as a forked review workflow with its own reasoning budget, isolated from the main flow. Reports only findings that survive the false-positive check, severity-ranked with file:line evidence and a fix direction, and states an explicit clean result when nothing real is found; stays read-only and never edits code. Use when the user asks to find bugs, review changes, or audit branch risk.
- ▌ Browse Aeo · ulpi-ioScore a page for how well AI answer engines can CITE it — Answer Engine Optimization, not classic rankings — by pulling structured data, meta, headings, and answer-shaped content via the `browse` CLI (schema/meta/headings/text) into a weighted 0-100 audit, plus a SERP mode that reads Google AI Overviews, Perplexity, and ChatGPT Search snapshots to see who actually gets cited. Never fabricates a score: an un-evaluable dimension is marked N/A, and "appears in AI Overviews" is asserted only after a real SERP check. Use to make a page answer-ready or to check its AI-answer visibility.
- ▌ Browse Geo · ulpi-ioTrack brand and domain VISIBILITY across AI search engines over a whole query set — Generative Engine Optimization monitoring, not a one-page audit — sweeping each query through Google AI Overviews, Perplexity, and authenticated ChatGPT Search via the `browse` CLI (camoufox for Google), recording each citation into a cross-engine visibility matrix with rates, average position, and competing domains. Reports point-in-time truth: ambiguous citations flagged uncertain, nothing fabricated. Use to monitor a brand's AI-answer presence across engines and queries.
- ▌ Browse SEO · ulpi-ioRun a full on-page technical SEO audit from a LIVE render — real rendered signals, not source guesses — extracting meta tags, heading hierarchy, structured data, navigation timing, link structure, and multi-viewport mobile rendering via the `browse` CLI (meta/headings/schema/perf/ links/responsive plus targeted JS checks), then rating each area PASS/WARNING/FAIL with prioritized fixes. The agent interprets the raw signals browse extracts; no scores are invented. Use to audit a page's technical/on-page SEO health.
- ▌ Find Agents · ulpi-ioDiscover, install, and manage AI agents across 43+ coding CLIs and IDEs from ONE source — auto-translated to each client's native format, not hand-ported — with the `agentshq` CLI: `find`, `add`, `list`, `remove`, `check`/`update`, and `init` scaffolding, scoped by `-g` (global) and `--ide` targets. Explicit-user-only and precise: it never installs, removes, or updates agents the user didn't ask for. Use to find agents or manage an existing agent catalog.
- ▌ Kiro Review · ulpi-io bundleGet an INDEPENDENT second opinion from the Kiro CLI run strictly READ-ONLY — a separate reviewer runtime over the real diff, with no write access to the repo. Reads the real diff (branch, a commit, or uncommitted) to build a focused prompt, optionally injects the stack's convention skills (`--skill`, since kiro can't load them itself), then launches kiro via the bundled helper with trust scoped to `fs_read,execute_bash` so it can grep/git to verify findings but never edit. Never uses `--trust-all-tools` (the auto-mode classifier dead-ends read-only tasks on it) or hand-rolls the prompt through the shell; keeps secrets out, treats findings as candidates to verify, and reports an explicit clean result. Use only on explicit user intent or when a user-invoked workflow composes it as the kiro reviewer.
- ▌ Launch Copy · ulpi-io bundleDraft the copy a launch needs, in multiple angles, all bound to the REAL product — never generic placeholders. Produces taglines/headlines, one-liners, short and long descriptions, and the launch post / first comment in feature-led, benefit-led, comparison, and audience-led versions with one recommended each. Reads and reuses `.ulpi/launch/positioning.md` (the platform-agnostic product brief) so the product is described once and reused everywhere; grounds via the `browse` skill + repo when it's absent. Honors the caller's **asset profile** — hard character limits, voice, and compliance rules — to the letter. Shared copy block of the launch-* family, feeding the per-platform runners' posts (`launch-product-hunt` listing, `launch-hacker-news` Show HN, `launch-x` / `launch-linkedin` threads) or run standalone; writes to `.ulpi/launch/<channel>/copy.md` or hands drafts back. Use when a launch needs on-brand, within-limit copy grounded in one real product.
- ▌ Map Project · ulpi-io bundleRefresh a SINGLE app's durable AI context — a thin `CLAUDE.md` router over discovered reference docs so future sessions start knowing the repo without paying for stale guesswork. Detects the framework shape, discovers the real routes, exports, flows, and subsystems from code, rewrites the imported references, then keeps `CLAUDE.md` compact and always-loaded. User-only maintenance workflow that mutates durable project memory: every claim is GROUNDED in the real codebase, never invented, and human-authored rules are preserved rather than overwritten. Use to initialize or refresh one app's context map after meaningful changes.
- ▌ Bugfix Crate · ulpi-ioWork a Rust crate's recorded issue file to green — one finding at a time, disciplined and sequential: for each finding, write the failing regression test first, apply the smallest correct fix, run the full crate's `cargo test` and `cargo clippy -D warnings`, then mark the finding FIXED / Deferred / Not-a-bug in the issue file before moving on. Never marks a finding fixed without its verification pass, never batches findings, and never buries a warning under `#[allow]` or swaps a real fix for a comment — the issue file and crate state stay in sync after every fix. Use only when the user asks to fix findings from an existing crate issue file.
- ▌ Codex Review · ulpi-io bundleGet an INDEPENDENT second opinion from the OpenAI Codex CLI — a separate reviewer runtime run over the real diff, not Claude reviewing its own work. Verifies Codex is available, resolves the scope (branch, a commit, or uncommitted), writes a focused instruction file grounded in the actual change set, runs `codex review` with disk-read sandbox so it can verify findings against source, then summarizes them by priority. Keeps secrets and credential values out of the instruction file, treats findings as candidates to verify locally before any fix, and reports an explicit clean result rather than fabricating one. Use only when the user explicitly asks for a Codex review or cross-review.
- ▌ Review Crate · ulpi-ioDeep-audit ONE Rust crate end to end — read every file, don't sample: enumerate and read the whole crate, run its `cargo test`, check the existing `.ulpi/issues/<crate>.md` to avoid duplicates, then write or append evidence-backed findings (correctness, panic, validation, race, data-corruption, coverage gaps) each with severity and exact file:line — runs as a forked analysis workflow with its own reasoning budget, isolated from the main flow. Only valid if it actually read the entire crate; grounds every finding in real file:line evidence, labels uncertain claims INFERENCE, and never invents issues from intuition or writes outside this repository's issue file. Use when the user asks for a deep review of a single Rust crate.
- ▌ Browse Config · ulpi-ioGenerate camoufox configuration for the `browse` CLI by INTERVIEW, not hand-edited JSON — an AskUserQuestion-guided flow that turns a chosen preset (stealth, fast-scraping, Google-safe, or a fully custom walkthrough) into a valid `browse.json` camoufox section or a named `.browse/camoufox-profiles/<name>.json`, using camelCase keys, merging without clobbering existing fields, and writing proxy credentials to file only. Use to create or tune an anti-detection browse profile before stealth browsing.
- ▌ Claude Review · ulpi-ioGet an INDEPENDENT second-opinion review from a separate Claude agent in a read-only worktree — findings only, never edits to your working copy. Reads the real diff (branch, a commit, or uncommitted) to build a focused, risk-targeted brief, launches the reviewer under worktree isolation with report-only instructions, then summarizes findings by priority with `file:line`, carrying an exclusion list forward on later rounds. Treats returned findings as candidates to verify locally, not truth; states an explicit clean result rather than inventing issues; keeps secrets out of the prompt and never lets the reviewer mutate code. Use only when the user explicitly asks for a Claude review.
- ▌ Code Simplify · ulpi-io bundleReduce a change's complexity WITHOUT altering behavior — lower cognitive load, not line count: read the target plus its callers and tests, take a baseline check, then apply the smallest clarifying edits in safest order (dead code and boolean cleanup → flatten nesting with guard clauses → consolidate duplication → local renames and helper extraction), respecting Chesterton's Fence. Re-runs the baseline after each edit and reverts any change that alters observable behavior or regresses, keeping only the safe improvements — a simplification that changes semantics is a bug, not a cleanup. Use only when the user explicitly asks to simplify or clean up existing code.
- ▌ Cost Estimate · ulpi-io bundleEstimate what a codebase, branch diff, or single commit would COST to build — evidence-driven, not a guess: measure the real scope with the helper scripts (LOC counter + git session analyzer), classify every source line into one productivity bucket, run the cost calculator for engineering hours, organizational overhead, calendar and team-cost views plus Claude ROI, and sanity-check the effective lines/hour — runs as a forked analysis workflow with its own reasoning budget, isolated from the main flow. Keeps raw engineering hours separate from overhead and team multipliers, never presents a number without scope, assumptions, and a confidence level, and never claims region-specific market rates unless the user asked and that research was actually done. Use when the user asks to estimate development cost, effort, engineering hours, or ROI.
- ▌ Go Live Audit · ulpi-io bundleAuthor and run a project-TAILORED pre-launch audit as a bounded multi-agent workflow — a real launch verdict, not a checklist skim: fill the bundled workflow template from the repo's real stack and hard rules, then run Gates (typecheck / test / lint / build in parallel) → Find (one read-only finder per applicable audit dimension) → Dedup (merge shared-root-cause findings) → Verify (adversarial agents try to refute every finding; blockers get a code lens plus a spec lens) → Critic (name uncovered areas, spawn follow-up finders) → a GO / NO-GO / GO-WITH-FIXES report, all fanned out under a MAX_PARALLEL cap. Finders and verifiers stay read-only — the skill audits and reports, never fixes; a gate that didn't actually run is treated as a blocker, never counted clean; secret values are redacted to type and location. Confirms scope and warns about the agent count (typically 40-80) before running.
- ▌ Ship Playbook · ulpi-io bundleTake one feature request from prompt to reviewed, audited delivery in a SINGLE autonomous pass — one runnable Workflow that plans, reviews the plan, builds task by task, cross-reviews the build, and optionally runs a launch audit, then RETURNS the verified findings rather than looping (the user decides any fix round; a Workflow can't ask mid-run, and an autonomous fix-loop is what caused multi-hour grinds). It chains the existing skills — plan-to-task-list-with-dag (a specialist agent per task) → plan-founder-review → a specialist engineer/reviewer build across the DAG → a full claude ∥ codex/kiro cross-review → go-live-audit — and FOLLOWS the graph strictly: every task declares its dependencies, layers must be a topological order, plan review blocks a mis-ordered graph, and a task NEVER builds before its dependencies integrate (no building on a broken base). Per-task review is SLICE-SCOPED (judges only that task's own change against its acceptance criteria, attributing whole-codebase end-state gaps to the ta
- ▌ Browse Stealth · ulpi-ioReach sites that BLOCK ordinary automation — the same navigate/inspect/interact/report loop as the `browse` skill, but on browse's camoufox runtime: a hardened Firefox with C++-level fingerprint spoofing, geoip, and humanized timing that passes Cloudflare Turnstile, Google "unusual traffic", DataDome, and PerimeterX, with named profiles, authenticated sessions, and proxy rotation. Honest about its limit: fingerprint spoofing alone will not defeat IP-reputation blocks — pair it with a residential proxy. Use when a page challenges or 403s a normal browser.
- ▌ Launch Linkedin · ulpi-io bundlePrepare and run a product/company launch on LinkedIn end to end — the launch link goes in the FIRST COMMENT, not the post body, and you never edit the post right after publishing. Grounds in the real product, then writes a paste-ready package to `.ulpi/launch/linkedin/`: `POST.md` (the launch **post** — a strong hook in the first ~2 lines before the "…see more" cut, a skimmable body, the reach-earning format, hashtags, and the product link as the **first comment**), `PLAN.md` (timing, the **golden-hour** engagement runbook, team amplification, and the post-launch plan), and `CHECKLIST.md` (a blocking pre-flight gate). The LinkedIn runner of the launch-* family: it owns LinkedIn mechanics, format rules, and the gate, and composes the shared `launch-copy` (post copy), `launch-outreach` (team amplification, mode `linkedin`), and `launch-analytics` (UTM + conversion tracking), degrading to built-in fallbacks if a companion isn't installed. Reads the shared `.ulpi/launch/positioning.md`. Engagement asks to your ne
- ▌ Launch Outreach · ulpi-io bundleBuild and notify a launch's supporter audience with paste-ready, platform-COMPLIANT outreach — the messages you send to PEOPLE, never the on-listing copy. Recruits an audience before launch, segments it (team · friends · users/waitlist · communities · public followers), and notifies it in timed waves on the day. Drafts the teaser DMs, waitlist and launch-day emails, community heads-ups, 1:1 DMs, and X/LinkedIn amplification posts, and writes them to `.ulpi/launch/<channel>/OUTREACH.md`. Parameterized by a per-platform COMPLIANCE MODE the caller passes (Product Hunt: supporter waves allowed, ask for feedback not upvotes; Hacker News: NO vote mobilization at all); grounds every message in `.ulpi/launch/positioning.md` and NEVER solicits/incentivizes votes or mass-spams. Shared audience block of the launch-* family, invoked by the per-platform runners (`launch-product-hunt`, `launch-hacker-news`, `launch-x`, `launch-linkedin`) or run standalone. Use when a launch needs who-to-tell and what-to-say, compliant to e
- ▌ Git Merge Expert · ulpi-io bundleRun a git merge, PR merge, conflict resolution, or rollback safely — readiness-checked and BACKED UP before anything touches shared history. Assesses branch/CI/review state and conflict risk, tags a backup point before non-trivial merges, resolves conflicts without dropping either side (regenerating lockfiles, not hand-editing), validates the result, then cleans up or rolls back — routing to the worktree specialist when isolated execution is safer. Never claims success with unresolved conflicts or failing validation, prefers `git revert` over `reset` on shared branches, and requires explicit confirmation before destructive rollback, force-push, or branch deletion. Use only when the user explicitly asks to merge, resolve conflicts, or roll back.
- ▌ Laravel Filament · ulpi-io bundleBuild Filament admin panels on the v5 API surface THIS project targets, not deprecated v3 patterns — a reference carrying the current namespaces and conventions for Resources, forms, tables, actions, filters, relation managers, widgets, infolists, panels, and testing, with business logic kept in application Actions, so a change lands idiomatic and review-ready instead of tripping over renamed APIs. Use when a task touches this project's Filament admin panels and should target the v5 surface rather than deprecated patterns.
- ▌ Launch Analytics · ulpi-io bundleInstrument a launch so the traffic spike is ATTRIBUTABLE, not a vanity number — one consistent UTM scheme on every launch link, the conversion funnel (visit → signup → activation) wired into GA4 or the project's existing analytics, and a validate + read-out step. Writes the UTM map + event plan to `.ulpi/launch/<channel>/analytics.md`, parameterized by launch source (e.g. producthunt, hackernews) so each link and report is correctly attributed. Shared measurement block of the launch-* family — invoked by the per-platform runners (`launch-product-hunt`, `launch-hacker-news`, `launch-x`, `launch-linkedin`) to close the loop, or run standalone. Measures durable outcomes (signups, activation), extends the real stack, and NEVER puts PII in links or events. Use when a launch needs UTMs on every link and signup tracking, not just an upvote count.
- ▌ Hand Over To Kiro · ulpi-io bundleDelegate an implementation task to the Kiro CLI and report exactly what it changed — verified against a git baseline, never on kiro's SELF-REPORT. Gathers the context a fresh agent needs, rephrases the request into a self-contained, injection-safe prompt with XML boundary tags, injects the task's kiro convention skills (`--skill`), launches kiro via the bundled helper with trust scoped to the mode (`implement` = least-privilege write, `review` = read-only), then diffs the working tree against a pre-run baseline. Never auto-installs kiro or pipes a remote installer to a shell, never passes raw user input through the shell or defaults to `--trust-all-tools`, and reports partial completion and errors honestly rather than trusting kiro's own summary. Use only when the user explicitly asks to delegate implementation to kiro.
- ▌ Launch Hacker News · ulpi-io bundlePrepare and run a Hacker News "Show HN" launch end to end — HN is STRICTER than every other channel: it **forbids all vote mobilization** (no supporter waves, no asking anyone to upvote, ever). Grounds in the real product (real stack, honest limits), then writes a small, paste-ready package to `.ulpi/launch/hacker-news/`: `POST.md` (the standard `Show HN: <thing> – <plain description>` title + the URL + the founder's technical, no-hype first comment), `PLAN.md` (US-Eastern timing, the first-1–2-hours plan, a thread-engagement plan with prepared answers to hard questions, and the post-launch / second-chance plan), and `CHECKLIST.md` (a blocking readiness gate). The HN runner of the launch-* family: it owns Show HN rules, HN policy, the thread runbook, and the gate, and composes the shared `launch-copy` (title + first comment) and `launch-analytics` (UTM + conversion tracking), degrading to built-in fallbacks if a companion isn't installed. Rewards technical honesty and a present, non-defensive founder; punishe
- ▌ Launch Product Hunt · ulpi-io bundlePrepare and run a Product Hunt launch end to end — COMPLIANT promotion ONLY: never vote manipulation, rings, bought/incentivized votes, or "please upvote". Grounds every word in the real product, then writes a complete, paste-ready package to `.ulpi/launch/product-hunt/`: `LISTING.md` (every PH field — tagline options ≤ the current limit, description, topics, a gallery shot-list, demo-video outline, the maker's first comment), `PLAN.md` (a T-minus countdown + an hour-by-hour Pacific-time launch-day runbook + the post-launch plan), `OUTREACH.md` (segmented supporter outreach + social posts), and `CHECKLIST.md` (a blocking pre-flight gate). The PH orchestrator of the launch-* family: it owns field specs, policy, and the day-of runbook, and composes the shared `launch-copy` (listing), `launch-outreach` (mode `product-hunt`), and `launch-analytics` (UTM + conversion tracking), degrading to built-in fallbacks if a companion isn't installed. Reads the shared `.ulpi/launch/positioning.md`. Treats Product Hunt as a c
- ▌ Plan Founder Review · ulpi-io bundleGate an implementation plan BEFORE agents execute it — catch phantom paths and false reuse, not typos: read the full plan markdown and its companion JSON, reality-check every file path and reuse claim against the actual repo, challenge scope, architecture, the dependency graph, and risk and test coverage, then score each section and render an APPROVE / REVISE / REJECT verdict — runs as a forked review workflow with its own reasoning budget, isolated from the main execution flow. The verdict follows only from evidence-backed findings: never rubber-stamps a non-trivial plan and never invents findings, but a genuinely clean section is allowed to pass; read-only, never edits the plan. Use when the user asks to review or gate a plan before execution.