Coding & Dev Tools

tss-blue-ai-lab Skill

Draft and, after approval, capture an observed reusable lesson in a skill's gotchas.md, proposing the file when it is missing. Use after a verified bug, architecture error, process failure, or misunderstanding when the lesson can be generalized without exposing project or user information.

tss-blue-ai-lab Skill

Clean up and improve existing code safely. Restructure without changing behavior. Use when: code is messy, duplicated, hard to read, or needs modernization.

tss-blue-ai-lab Skill

Implement authentication and authorization from scratch. Covers signup, login, sessions, JWT, role-based access, and protected routes. Use when: adding auth to a new or existing app.

tss-blue-ai-lab Bundle

Create and run Maestro UI test flows for the app in this repo. Use when writing Maestro YAML flows or verifying app behavior on a device/emulator.

tss-blue-ai-lab Skill

Interactively review and consolidate existing gotchas.md files within an explicitly selected skills root. Use when lessons have accumulated, overlap, conflict, contain stale or sensitive context, or need clearer scope and conditions.

tss-blue-ai-lab Skill

Generate new reusable skills from git history, coding patterns, and team practices. The meta-skill: teaches the AI to create new skills. Use when: you have recurring patterns worth capturing, want to codify team knowledge, or need to create custom workflows for your project.

tss-blue-ai-lab Bundle

Use when reviewing code for bugs with finder, challenger, and referee roles, especially when independent review is needed to reduce false positives.

cryptopafi Skill

Interview the user relentlessly about a plan, design, or decision until reaching shared understanding. Resolves each branch of the decision tree one-by-one, providing recommended answers. Use when user says '/grill-me', 'grill me', 'stress-test this plan', 'challenge my design', 'interview me about this', or wants to validate a decision before implementation.

cryptopafi Bundle

Use when Pafi asks for “MoA candidate mode”, “MoA/council QA”, “compare default vs council vs MoA”, “is this worth MoA?”, or when a request affects Hermes routing, profile/SOUL/skill policy, architecture, sensitive final QA, RUO/Supabase safety, OpenClaw retirement, or high-stakes strategy. This skill classifies whether MoA-style synthesis or a council critique pattern is worth the cost and returns a decision packet. It does not enable live MoA routing by itself.

cryptopafi Bundle

Validate raster banner ads before delivery with deterministic checks plus a forced visual gate. Use when reviewing, QA-ing, exporting, or preparing final SMSads, RCS, WhatsApp, push, in-app, Rewards Affiliates, casino display, or other raster ad banners. ANTI-PATTERN: Do not use for generating banner concepts, writing copy, or subjective design critique alone; use imagegen/gpt-image-banner/banner-critique for those.

cryptopafi Bundle

Calculate RUO Peptides/PeptraLabs restock recommendations (read-only) from current stock, empirical customer-sale velocity, open restocks, a conservative single-number lead time, COA economic-batch floor, 2-year shelf-life cap, and a Bucharest/Ibiza transfer-first gate. Use for weekly reorder planning, after a customer order to decide whether to restock, or when Pafi asks what to order next. ANTI-PATTERN: Do not create supplier orders or mutate Supabase; do not treat staff/internal transfers, gifts, losses, or supplier substitutions as customer demand; do not use per-patient protocol vials as an aggregate rate or fold assumed stack demand into the default recommendation.

iopsystems Skill

Open a new **arc** — a narrative unit of change in the knowledge-iop vault that spans weeks to quarters. Arcs have a beginning, middle, and end. Use this when the user says things like "let's start an arc for X", "open the Y arc", "we're kicking off a project on Z", "this deserves its own arc". Arcs group briefs, inquiries, and decisions under a shared charter — the situation, the tension, the direction of resolution. If the effort is permanent (not going to close), use `define-scope` instead. If it's a one-off, maybe it just needs a brief.

iopsystems Skill

Write the **synthesis** that closes an inquiry — read every submitted exploration, reconcile them against the framing, and produce the inquiry's resolved take. Use this when the user says things like "the barrier has released", "let's synthesize the inquiry", "we have all the explorations now", "resolve inquiry X". This skill assumes the barrier condition is met and all intended explorations have been submitted; it will refuse to synthesize a `status: open` inquiry. Synthesis is the only artifact that reads *across* explorations — everything before it is isolated.

iopsystems Skill

Define a new **scope** — a stable reference frame (service, domain, surface, cross-cutting concern) that the vault cares about for years rather than the duration of a narrative arc. Use this when the user says things like "we need a scope for X", "add a scope", "register the billing service", "document this as a domain we care about". Scopes are flat (no hierarchy), they don't have arcs' narrative lifecycle, and they retire rather than close. Don't create a scope lightly — scope proliferation is a smell. If it's a short-lived effort, use `open-arc` instead.

iopsystems Skill

Open a bounded parallel **inquiry** — the knowledge-iop vault's barrier-mode coordination primitive for cases where multiple people should explore a question independently before anyone synthesizes. Use this when the user says things like "let's explore alternatives", "I want N people to try this independently", "we need parallel drafts", "let's not converge too early", or when a problem has multiple credible approaches and premature convergence would foreclose options. An inquiry is a *directory*: framing up front, isolated exploration files, synthesis after the barrier releases. If the question has one clearly best answer already, use `propose-design` instead — inquiries are for genuine ambiguity.

iopsystems Skill

Scope, frame, and design a feature end-to-end — especially one that spans more than one repo. Runs a multi-turn Q&A covering problem, user value, constraints, surface area, key decisions, and cross-repo coordination, then fans the output out into the right places: paired problem/design briefs in the knowledge-iop vault (always), an optional design doc in the feature repo (`docs/design/<slug>.md`), and draft per-repo tracking issues. Use this when the user says things like "plan a feature", "scope this work", "I need a design for X", "let's kick off Y", "we need an RFC for this", or any time work needs both centralized knowledge capture and repo-local grounding. If the user only wants to capture a problem with no solution in mind, use `frame-problem` directly instead.

iopsystems Skill

Query the knowledge-iop vault as a habit before drafting anything. Before you write a new problem-brief, design-brief, inquiry, decision, discussion, scope, or arc, first check whether a relevant artifact already exists so you can supersede, relate to, or frame from it — rather than orphan your work. Use this whenever the user says things like "what do we know about X", "is there already a brief on Y", "show me the design for Z", "find related artifacts", "what's the status of...", or before any phase skill (frame-problem, propose-design, record-decision, ...). The underlying programmatic tools are vault_search, vault_edges, and vault_check_transition — this skill teaches when to reach for each.

iopsystems Skill

Draft a **problem brief** — the "what actually is the problem" half of the paired briefs convention in knowledge-iop. A problem brief is written before any solution is proposed. Use this whenever the user says things like "we need a problem brief", "let's frame the problem", "what are we even solving", "capture the constraints", "I want to document a problem we can't solve yet", or any time they're about to design something but the problem hasn't been stated in one place. A problem brief can be orphan-of-solution — it's valuable even without a design. After framing a problem, the natural next step is `propose-design` (which `frames:` this brief).

iopsystems Skill

Draft a **design brief** — the "how do we solve it" half of the paired briefs convention in knowledge-iop. Every design brief must declare `frames:` pointing at a problem brief (or `frames: none` with a reason, discouraged). Use this whenever the user says things like "I need a design brief", "let's design a solution for X", "propose a design", "draft the design half", "how should we approach this". If no matching problem-brief exists in the vault, this skill will direct you to `frame-problem` first — solutions without framing are the anti-pattern the vault is built to prevent.

iopsystems Bundle

Draft the pull-request body as a guide for the human reviewing it: where to look more closely, what was tested and what was not, which calls were rather than deduction, and what will only show up in production. Use when asked to "draft the PR body", "write the PR description", "make this reviewable", "write a review guide", or whenever opening or updating a pull request. It runs on every change; what it publishes is proportional to the change, and a change with nothing to direct attention to earns one sentence rather than a guide. Beta — its ranking and publish rules are asserted rather than measured, so record friction and confirmation through `engineering-journal`. Symptoms that this skill applies: a description that retells the diff, a reviewer who reads files in whatever order the diff listed them, "all tests pass" with no statement of what the tests do not cover, a change whose risky decisions are invisible because they look like ordinary code, or an author who resolved an ambiguous requirement silently

iopsystems Skill

Author a single **exploration** within an open inquiry — one explorer's independent take on the question, drafted in isolation from other explorers. Use this when the user says things like "I want to contribute to inquiry X", "let me write my take on this", "add my exploration", "submit my draft". An exploration is intentionally drafted without seeing others' work — that's the barrier-mode coordination pattern. Submission freezes the content; synthesis comes later via the `synthesize` skill once the inquiry's barrier condition is met.

iopsystems Bundle

Hold code comments and docstrings to a strict quality bar. Use whenever writing or editing comments — adding a comment to new code, being asked to "document this", "add comments", or "make this reviewer-ready" — and as a dedicated staleness sweep before opening or updating a pull request. Symptoms that this skill applies: comments that restate the adjacent code, the same design explanation sprinkled across several sites, docstring boilerplate on small internal helpers, derivation walkthroughs, war-story narration, comments describing behavior a design pivot has since deleted, commented-out code kept "just in case", ticketless TODOs, banner comments, docstrings written only to silence a linter, an invariant reduced to a pointer at the very site where a wrong edit would silently break it, or a comment asserting what the code does, has, or lacks that nobody checked against the code.

iopsystems Bundle

Use when a user has approved a catalog skill template to seed, customize, or upgrade, or explicitly asks to perform one of those actions for a project-local installed instance.

iopsystems Bundle

Draw the layout of a memory or wire format that already exists in code — a byte anatomy of one encoded instance, the per-variant conventions of a shared encoding, or the linkage between blocks. Use when asked to "diagram the format", "show the byte layout", "draw the header", "picture the on-disk structure", "explain the encoding", or when a format reference, design record, or pull request needs a figure of a structure a reader cannot hold in their head. Beta — the conventions come from one format in one repository, so record friction and confirmation through `engineering-journal`. Symptoms that this skill applies: a byte grid drawn by hand from a specification, a figure whose offsets no longer match the encoder, a byte grid routed through a graph layout engine, a figure that cannot say whether it shows what ships or what is planned, or a figure that looks right in a browser and breaks in the rasterizer that publishes it.

aiagentwithdhruv Bundle

Complete video editing toolkit - silence removal, auto-captions, vertical crop, YouTube clipping, 3D transitions, and social media compression. Use when user asks to edit video, remove silences, add captions/subtitles, crop to vertical/shorts, download YouTube clips, compress video, or create video teasers.

aiagentwithdhruv Bundle

Auto-label Gmail emails into Action Required, Waiting On, and Reference categories. Use when user asks to label emails, triage inbox, categorize emails, or organize Gmail.

aiagentwithdhruv Bundle

Scrape Google Maps for B2B leads with deep website enrichment and contact extraction. Use when user asks to find local businesses, scrape Google Maps, generate contractor lists, or build local service business databases.

aiagentwithdhruv Skill

Run Claude orchestrator locally with Cloudflare tunneling. Use when user asks to run locally, start local server, or test webhooks locally.

aiagentwithdhruv Bundle

Scrape Upwork jobs and generate personalized proposals with cover letters. Use when user asks to find Upwork jobs, create Upwork proposals, or apply to Upwork listings.

aiagentwithdhruv Skill

Send a message to Dhruv's Telegram. Use when user says "send to telegram", "telegram me", "notify me", or wants to receive any text/note/reminder on Telegram.

aiagentwithdhruv Bundle

Monitor and interact with Skool communities - read posts, create posts, reply to comments, like content, and search. Use when user asks to check Skool, read community posts, interact with Skool, or manage Skool community.

aiagentwithdhruv Bundle

Generate a premium mockup website for a prospect using the buildinamsterdam.com template style. Use when user asks to design a website, create a mockup, or build a prospect website.

aiagentwithdhruv Bundle

Generate title variants for YouTube videos from outlier analysis. Use when user asks to create title variations, generate YouTube titles, or adapt video titles.

aiagentwithdhruv Bundle

Generate PandaDoc proposals from client information or sales call transcripts. Use when user asks to create a proposal, generate a quote, draft a contract, or prepare a client document.

aiagentwithdhruv Bundle

Find viral YouTube videos in your niche for competitive intelligence. Use when user asks to find YouTube outliers, monitor competitors, or track viral videos.

aiagentwithdhruv Bundle

Create 3D pan/swivel transition effects for videos using Remotion. Use when user asks to add 3D transitions, create swivel effects, or add video transitions.