Run merges and conflict resolution inside a dedicated git worktree so the MAIN tree is never touched — isolation is the whole point. Lists existing worktrees and current context first, creates or reuses the right isolated workspace, tags a backup and performs the merge/rebase/ cherry-pick there, validates the result…
Run 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…
Author 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…
Delegate 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…
Get 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…
Build 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…
Write 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…
Instrument 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/…
Draft 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…
Prepare 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/…
Prepare 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…
Build 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.…
Prepare 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 ≤…
Prepare 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…
Put 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…
Refresh a Cargo WORKSPACE or package monorepo's durable AI context — a self-contained CLAUDE.md per member that Claude lazy-loads, plus a thin project-wide root, so a change in any member has local guidance without bloating the root. Discovers each member's real reachable surface, key files, wiring, and inter-member…
Refresh 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…
Build 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…
Build 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…
Write 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…
Convert a local AGENT.md into a Claude Code optimized agent — an AUDIT-then-rewrite that ties every change to real Claude agent-runtime behavior, not taste. Inventories the agent, checks it against the runtime reference (the whole body becomes the system prompt; role identity stays, procedure moves to skills), writes…
Convert a local skill into a Claude Code optimized shape — an AUDIT-then-rewrite that ties every change to real Claude skill-runtime behavior, treating FRONTMATTER as the highest-leverage routing surface. Inventories the skill, checks it against the runtime reference (Claude routes and budgets skills from metadata…
Gate 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…
Turn a request into a SCHEDULABLE task DAG — atomic tasks with real dependencies, not planning prose: challenge scope and pick a planning mode with the user first, explore the real repo so no path is invented, then decompose into atomic TASK-NNN entries — each with a ≤3-file write scope, 2-3 testable acceptance…
★not rated 5 1mo agoA190 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: