← all publishers

preetamnath

@preetamnath source repo

Report this profile Claim this profile

• 42 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Jtbd · preetamnath

   Frame a vague goal as the job to be done, so the outcome is explicit before you build or choose. TRIGGER when: user says 'what's the job', 'JTBD', 'frame the outcome', 'what are we actually trying to do'; or a goal, feature, or decision is stated as a solution with the progress underneath it unnamed.
   0
   installs
2. ▌
   Tldr · preetamnath

   Respond in one sentence, or the number the user specifies. TRIGGER when: user says 'TL;DR', 'tldr', 'respond in one sentence', 'respond in 2 sentences', 'respond in N sentences', 'say that in 1/2 sentences', 'give me your last response in 1 sentence'. SKIP when: user wants the last response re-explained in simpler language (explain-simply).
   0
   installs
3. ▌
   Triage · preetamnath

   Verify a panel's findings against their artifact: each gets a consider / skip verdict and a confidence. TRIGGER when: a fan-out skill needs its findings verified before walking them with the user; user says 'triage these findings', 'verify which of these are real', 'which are worth acting on'.
   0
   installs
4. ▌
   Handoff · preetamnath

   Compress the live conversation into minimal, copy-paste-ready handoff prompt(s) — context referenced by file path, not pasted — so a fresh chat picks up cleanly. TRIGGER when: user says handoff, handover, new-chat / fresh-chat prompt, prompt to continue or resume elsewhere; user asks for separate prompts to explore N threads in their own chats.
   0
   installs
5. ▌
   Grill Me · preetamnath

   Stress-test a plan, design, or decision — challenge assumptions, expose gaps, force specificity. TRIGGER when: user says 'grill me' or 'stress-test this'; user wants their plan or decision pushed on.
   0
   installs
6. ▌
   Vet Fact · preetamnath

   Judge whether a candidate current-guidance fact earns a durable instruction line: keep only what prevents a likely wrong answer; cut derivable, historical, setup, or default restatements. TRIGGER when: user asks 'does this belong in AGENTS.md / a rule / the docs', 'is this worth keeping/writing down', or 'should this be a comment'; vetting or pruning current guidance before placement or shaping. SKIP when: evaluating or placing active state or dated evidence (place-fact).
   0
   installs
7. ▌
   Find Gaps · preetamnath

   Surface what a draft, answer, or code is missing — parallel subagents each apply a different lens, scoring findings by impact and confidence, then walk them one at a time. TRIGGER when: user says 'find gaps', 'what did I miss', 'analyze from multiple angles', 'what am I overlooking'; user has an in-progress artifact and an open-ended mandate to improve it. SKIP when: building one answer (best-answer); trust-checking an answer you have (validate-answer).
   0
   installs
8. ▌
   Trim Spec · preetamnath

   Trim a spec, ADR set, or design doc down to what a builder needs, without losing a fact. TRIGGER when: user says a spec is 'too long' or 'bloated'; user asks what to remove from it, or wants it cut to 'just what we need to build'.
   0
   installs
9. ▌
   Agent Soul · preetamnath bundle

   Load a personality archetype that shapes the agent's voice — greetings, status, closings, pushback tone — while keeping plans, diffs, and recommendations neutral. TRIGGER when: user says load a soul/personality/voice/archetype; user says give me a voice; user asks for a specific persona (e.g. gordon-ramsay, yoda); user says switch/swap/change soul; user says serious mode or resume personality.
   0
   installs
10. ▌
    Place Fact · preetamnath

    Route guidance, state, or evidence already worth keeping to one canonical owner and the narrowest reliable delivery boundary. TRIGGER when: user asks 'where should this go', 'which file/rule/home does this belong in', 'is this in the right place', or 'should this be a pointer'; placing or re-homing kept material.
    0
    installs
11. ▌
    Write Plan · preetamnath

    Sequence a locked spec into dependency-ordered, wave-grouped tasks. TRIGGER when: user says 'build the plan' or 'sequence this'; a spec needs slicing into parallel-safe waves.
    0
    installs
12. ▌
    Best Answer · preetamnath

    Build the single strongest answer to one open question — a diverse panel of subagents attacks it, a clean-room judge maps their disagreement, then you synthesize one grounded answer better than any single take. TRIGGER when: user says 'best answer', 'fan out and synthesize', 'give me the strongest answer'; user has a hard question and no answer yet. SKIP when: validating an answer you already have (validate-answer); surfacing problems in a draft (find-gaps).
    0
    installs
13. ▌
    Refine File · preetamnath

    Audit one current-guidance instruction file for worth, placement, and clarity. TRIGGER when: user says 'refine/audit this file', 'prune and tighten this doc', or 'what here is worth keeping'; a skill, agent prompt, AGENTS.md, Claude path rule, maintained current document, or workflow needs one pass. SKIP when: shape-only tightening with no worth/place question (tighten-file).
    0
    installs
14. ▌
    Tech Design · preetamnath

    Turn a locked product/UX spec into technical design — the HOW: architecture, data shapes, signatures, file layout. TRIGGER when: user asks how to implement a spec'd feature; user wants architecture, data-shape, or file-layout decisions; user says 'tech design' or 'design the implementation'. SKIP when: product scope or UX is unclear; implementation is trivial and obvious; only wave ordering remains.
    0
    installs
15. ▌
    Deep Modules · preetamnath

    The deep-module primitive: a small interface hiding lots of behaviour. Apply the lens to judge or shape one interface, or audit a codebase for shallow modules (returns a ranked table). TRIGGER when: user says 'deep modules', 'is this a deep module', 'find shallow modules', 'audit from the deep-module lens'; a skill needs the deep-module vocabulary.
    0
    installs
16. ▌
    Execute Chat · preetamnath

    Execute work already agreed in the current chat without a plan.md. TRIGGER when: the user explicitly asks to use execute-chat.
    0
    installs
17. ▌
    Execute Plan · preetamnath

    Implement a feature by executing its wave-grouped plan.md. TRIGGER when: user says 'run the plan', 'execute the plan', or 'implement it'; a plan.md has unchecked waves ready to build.
    0
    installs
18. ▌
    Interview Me · preetamnath

    Socratically interview the user to move an open question — a decision, strategy, trade-off, or research direction — from ambiguity to clarity. TRIGGER when: user says 'interview me' or asks to be interviewed; user wants to think a decision or trade-off through Socratically. SKIP when: clarifying the scope of a buildable feature meant to produce a spec (product-interview).
    0
    installs
19. ▌
    Memory Prune · preetamnath

    Prune project memory files: keep memory-native records, route guidance, state, and evidence to canonical owners, then trim or delete absorbed sources. TRIGGER when: user says 'prune my memories', 'clean up memory', 'what memories should be promoted', or 'review my memory dir'. SKIP when: routing one fact (place-fact), or auditing one instruction file or AGENTS.md (refine-file).
    0
    installs
20. ▌
    Tighten File · preetamnath

    File-level tightening pass on an instruction file (CLAUDE.md, skill, agent prompt, style guide) using `tighten-instruction` as the lens. TRIGGER when: user says 'tighten/simplify this file/skill/CLAUDE.md', 'cut this down', 'titan instruction on this file'; user points at a verbose instruction file and wants it leaner.
    0
    installs
21. ▌
    Compress File · preetamnath

    Compress one instruction file to the leanest STRUCTURE that still delivers its purpose — dissolve sections that restate others, fold unique survivors into the section that governs them. TRIGGER when: user says 'why is this so long', 'strip the fat', 'de-duplicate this skill/doc', 'these sections overlap'.
    0
    installs
22. ▌
    Explain Deeply · preetamnath

    Explain a feature, flow, or concept: read the source of truth, lead with the answer, and diagram each idea the answer depends on. TRIGGER when: user says explain/walk me through/ELI5/help me understand; user wants to understand how a feature, flow, or system works. SKIP when: user wants your last response restated more simply (explain-simply); user wants a diagnosis, fix, or action; user wants a one-line definition they can already apply; a quick spot-check or confirmation.
    0
    installs
23. ▌
    Explain Simply · preetamnath

    Re-explain your last response in the simplest language. TRIGGER when: user says 'explain simply', 'explain in simpler words', 'explain in fewer words', 'use easy to understand words', 'simplify that', 'answer concisely and simply', 'dumb it down'.
    0
    installs
24. ▌
    Prove Behavior · preetamnath

    Decide whether automated tests should change, choose the smallest valuable evidence, and prove it detects the named material defect. TRIGGER when: code changes observable behavior a test could protect; adding, changing, deleting, or reviewing tests; checking that a test detects its claimed defect. SKIP when: only running existing checks or live post-ship verification (test-completed-plan).
    0
    installs
25. ▌
    Second Opinion · preetamnath

    Second opinion on one concrete proposal: stress-test it, rank alternatives, or both. TRIGGER when: user says 'second opinion', '2nd opinion', 'rate my fix', or 'weigh in on my approach'; user wants a candidate edit/decision evaluated. SKIP when: multiple decisions on a larger artifact — use `validate-answer`.
    0
    installs
26. ▌
    Check Coherence · preetamnath

    Cold-read one changed instruction file for clarity and internal coherence. TRIGGER when: user asks for a cold read, coherence check, or final clarity-and-coherence pass after edits.
    0
    installs
27. ▌
    Design Critique · preetamnath

    Critique an existing UI and return ranked, evidence-backed fixes. TRIGGER when: user explicitly asks for a design critique, broad UI review, or ranked design improvements. SKIP when: the user provides a screenshot to diagnose, measure, fix, or verify a specific issue instead of requesting a design review.
    0
    installs
28. ▌
    Fix Verify Loop · preetamnath

    Resolve confirmed P0/P1 findings in at most two fix-and-verify attempts, then escalate. TRIGGER when: review findings or test failures need resolution; user says 'fix these findings' or 'resolve the P0s'. Per-finding resolution only; the caller owns regressions.
    0
    installs
29. ▌
    Sentry Analysis · preetamnath

    Diagnose the root cause of a Sentry issue from its error logs, breadcrumbs, and codebase context. TRIGGER when: user shares a Sentry issue, error, or link and asks why it happens or how to fix it; user says 'analyze this Sentry error', 'find the root cause', 'debug this stack trace'.
    0
    installs
30. ▌
    Shopify Dev MCP · preetamnath

    Routes Shopify Dev MCP lookups for surfaces the bundled Shopify skills don't cover. TRIGGER when: user needs docs or GraphQL for Storefront API, customer, partner, payments-apps, functions, hydrogen, liquid, or custom-data (metafields/metaobjects). SKIP for Admin GraphQL or App Home markup (`shopify-admin` and `shopify-polaris-app-home` cover those); SKIP for `@shopify/post-purchase-ui-extensions-react` — the MCP doesn't index that legacy SDK (use `post-purchase-ui-extension`).
    0
    installs
31. ▌
    Structure Prose · preetamnath

    Reshape one prose block into a labeled list or table when it fuses several independent rules — form only, content verbatim. TRIGGER when: user says 'break this up', 'wall of text', 'should this be a list/bullets', 'structure this paragraph'; a dense block buries rules a reader needs to jump to.
    0
    installs
32. ▌
    Two Pass Review · preetamnath

    Two-pass code review — a review pass hardened by an adversarial verification pass that suppresses false positives. TRIGGER when: user wants final review of completed code changes; any review where a false positive would cost real time. SKIP when: reviewing a non-code artifact (reviewer); a quick spot-check during iteration.
    0
    installs
33. ▌
    Validate Answer · preetamnath

    Trust-check an answer, plan, or decision you already have — multiple identical independent reads converge per question, agreement signals confidence and splits flag what's contested, then walk each decision. TRIGGER when: user says 'validate', 'trust-check', 'is this right', 'pressure-test my decision'; user has a near-final answer or a few focused decisions to confirm. SKIP when: no answer yet, want one built (best-answer); surfacing what's missing (find-gaps).
    0
    installs
34. ▌
    Generate Mockups · preetamnath

    Generate UI mockups as one-file HTML, no build, grounded in the project's real design language — PREVIEW a feature's screens or states, or COMPARE directions for one choice and pick one. TRIGGER when: you want a UI screen, flow, or set of states rendered, or to compare 2+ visual directions you'd judge better by seeing than by ASCII; user says 'mock this up', 'show me the screens', 'show me the states', 'show me the options', 'which looks better'. SKIP when: one direction is obviously right; the choice is logic/data/architecture, not visual; ASCII conveys it (AskUserQuestion preview); inventing one aesthetic from a blank canvas (frontend-design).
    0
    installs
35. ▌
    Product Interview · preetamnath

    Define WHAT to build — product scope and UX — before technical design. TRIGGER when: user asks for a product interview or to design a new feature; product scope or UX is unclear; an external PRD needs transcribing into the canonical spec. SKIP when: product/UX is settled; the change is trivial; only implementation is unclear; user says 'just do it'.
    0
    installs
36. ▌
    Durable Docs Update · preetamnath

    After coding work, sweep comments in changed files and sync only related durable guidance through WORTH → PLACE → SHAPE. TRIGGER when: user asks to update/sync durable docs, code comments, or AGENTS.md after work; an executor skill reaches close-out.
    0
    installs
37. ▌
    Map Design Language · preetamnath

    Research a project's design language and write or refresh a lean meta/DESIGN.md of facts — surfaces, toolkits, tokens, styling models, docs pointers — that grounds mockups and new UI. TRIGGER when: user asks to map, document, or bootstrap the design language, or to create/refresh meta/DESIGN.md; a skill needs grounding facts and meta/DESIGN.md is missing or stale. SKIP when: meta/DESIGN.md exists and is current (just read it); inventing a new aesthetic from a blank canvas (frontend-design).
    0
    installs
38. ▌
    Test Completed Plan · preetamnath

    Run the live testing phase after execute-plan ships a build — drive the spec's '### Post-ship verification' checklist (the human-gated ACs the diff can't prove) to pass/fail across three tiers: unit/frontend, real authenticated app, and server-log/DB. TRIGGER when: a shipped spec's Post-ship verification list needs behavioral testing; user says 'test the completed plan', 'run the testing phase', or 'verify the shipped spec'. SKIP for code review (use two-pass-review) or re-verifying code-gated ACs settled at the ship gate.
    0
    installs
39. ▌
    Tighten Instruction · preetamnath

    Make an instruction line read cold: clarify it into plain words, then tighten it to one positive line. TRIGGER when: user says 'tighten/clarify this rule/fact', 'make this leaner/simpler/clearer', 'titan instruction' in a skill, CLAUDE.md, agent prompt, or rule file.
    0
    installs
40. ▌
    Multi Agent Analysis · preetamnath

    Dispatch 1–3 subagents to analyze or verify something, then judge their findings yourself. TRIGGER when: user asks for 'multi-agent analysis', 'use subagents to analyze/verify', or 'use parallel subagents' to investigate something.
    0
    installs
41. ▌
    Post Purchase UI Extension · preetamnath

    SDK reference for `@shopify/post-purchase-ui-extensions-react` — Shopify's post-purchase upsell surface (the screen between payment and the thank-you page). Distinct from modern `<s-*>` checkout-extensions, which have no post-purchase target. TRIGGER when: code imports `@shopify/post-purchase-ui-extensions-react`; user mentions post-purchase offer, post-purchase page, post-purchase upsell, post-purchase-ui-extensions, ShouldRender, applyChangeset, or `Checkout::PostPurchase::*`; user edits files under `extensions/*post-purchase*/`.
    0
    installs
42. ▌
    Audit Transcripts For Learnings · preetamnath

    Audit past Claude Code transcripts in a chosen scope and date window to extract reusable patterns, then walk each one to promote it into a slash command, CLAUDE.md rule, memory entry, or new skill. TRIGGER when: user wants to mine past sessions for reusable workflow patterns, recurring corrections, or validated approaches worth capturing; user asks how often a skill ran across sessions.
    0
    installs