← all publishers

jlave-dev

@jlave-dev source repo

Report this profile Claim this profile

• 22 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Yagni · jlave-dev bundle

   Plan or perform ruthless YAGNI repo cleanup. Use when asked to identify or remove stale docs, unused code/deps, duplicate scripts/config/deploy paths, dead flags/routes, speculative abstractions/product surfaces, misleading tests, or implementation/docs drift while preserving active decisions and guardrails.
   0
   installs
2. ▌
   Find Orders · jlave-dev bundle

   Use when the user asks to find Amazon orders, invoices, return windows, warranty details, reorder links, delivery status, or purchase history. Works from the user's signed-in Amazon account when available and treats order work as read-only unless the user explicitly confirms a separate account-changing action.
   0
   installs
3. ▌
   Shop Amazon · jlave-dev bundle

   Use when the user asks to shop on Amazon, compare Amazon products, research purchase options, or build a product shortlist. Verifies product-page ASIN/title/price/rating/review data and ranks options by user criteria, favoring review count when ratings are close.
   0
   installs
4. ▌
   Save Note · jlave-dev bundle

   Save relevant thread context as Markdown files in a local notes directory. Use when the user asks to save a note, capture or remember conversation context, preserve decisions, summarize an active thread for later, or turn explicit, implied, or inferred thread context into a local .md note. For durable planning documents, use save-plan instead.
   0
   installs
5. ▌
   Save Plan · jlave-dev bundle

   Save durable planning documents as Markdown files in $HOME/plans. Use when the user asks to save a plan, write this down as a plan, put planning work in the plans directory, preserve a migration/design/review/implementation plan, hydrate an agreed plan with detail, or update an existing saved plan.
   0
   installs
6. ▌
   Write Reviews · jlave-dev bundle

   Use when the user asks to draft, refine, or submit an Amazon product review for a purchased item. Verifies the product/order context when possible, drafts in the user's requested tone, and submits only after explicit user approval.
   0
   installs
7. ▌
   Write Prompt · jlave-dev bundle

   Turn rough intent into a copy-ready prompt sized to the task. Use when the user asks to write or refine a prompt, invokes $write-prompt, or says promptify; not to execute the underlying task.
   0
   installs
8. ▌
   Create Readme · jlave-dev bundle

   Create or update accurate README.md files. Use when asked to draft, rewrite, audit, or refresh a README for a repository, package, app, library, CLI, service, dataset, or docs folder.
   0
   installs
9. ▌
   Sdlc Evidence · jlave-dev bundle

   Use when an Agent SDLC implementation has a PR or review verdict and the workflow needs current-head checks, local verification, attached proof, simulator evidence, blocker classification, PR body updates, or GitHub issue Agent State refresh before review or merge.
   0
   installs
10. ▌
    Sdlc Reviewer · jlave-dev bundle

    Use when acting as an independent software reviewer for an SDLC thread workflow, especially when another thread sends a code-change handoff and expects severity-ranked findings plus an explicit review verdict.
    0
    installs
11. ▌
    Sdlc Preflight · jlave-dev bundle

    Use when an Agent SDLC issue is ready to dispatch or resume and the orchestrator must verify the issue, dependency mode, branch, worktree, base ref, active issue/PR overlap, and hard-stop conditions such as detached HEAD or wrong checkout.
    0
    installs
12. ▌
    Create Agents Md · jlave-dev bundle

    Create, update, audit, or split AGENTS.md files for repositories and subdirectories. Use when Codex needs repo-specific agent instructions for commands, conventions, validation, architecture boundaries, monorepo routing, safety, or review workflows.
    0
    installs
13. ▌
    Refactor UI · jlave-dev bundle

    Use when editing frontend code to remove clutter, leaky copy, redundant UI, duplicate actions, nested cards, or over-explained screens while preserving behavior.
    0
    installs
14. ▌
    Sdlc Merge Queue · jlave-dev bundle

    Use when Agent SDLC PRs are approved and marked merge-ready, and an orchestrator should merge one or more PRs in dependency order while verifying current-head checks, issue Agent State, review verdicts, and handing conflicts or failed checks back to workers instead of fixing inline.
    0
    installs
15. ▌
    Sdlc Orchestrate · jlave-dev bundle

    Use when the user wants Agent SDLC to continue an issue or pull request to the next workflow role automatically, including preflight, dispatch, evidence refresh, review, docs, or merge queue routing from GitHub issue/PR state.
    0
    installs
16. ▌
    Sdlc Review Loop · jlave-dev bundle

    Use when running an Agent SDLC implementer/reviewer loop for a git-backed change, including generating a handoff, reusing the singleton reviewer thread, classifying review verdicts, iterating fixes, and keeping evidence/issue state current.
    0
    installs
17. ▌
    Sdlc Issue Intake · jlave-dev bundle

    Use when turning a rough feature request, bug report, cleanup idea, or agent task into a scoped GitHub Issue for Agent SDLC workflows, including active-work overlap checks, dependency classification, labels, branch naming, CI tiering, and a worker dispatch prompt saved into the issue.
    0
    installs
18. ▌
    Reason From Evidence · jlave-dev bundle

    Investigate evidence with explicit hypotheses and justified conclusions. Use when debugging systems, analyzing incidents or reports, reducing possible explanations, finding missing evidence, or separating proof, consistency, probability, and speculation.
    0
    installs
19. ▌
    Sdlc Dispatch Issue · jlave-dev bundle

    Use when an orchestrator should pick or receive an Agent SDLC GitHub Issue whose preflight has passed, create the implementation branch/worktree, spawn the worker thread from the issue's saved Worker Dispatch prompt, or record worker state back on the issue without doing worker fixes inline.
    0
    installs
20. ▌
    Map Project Decisions · jlave-dev bundle

    Map a greenfield software project's components and separate human-owned product or architecture decisions from safe, reversible, or testable choices the agent should make. Use when starting a new app, service, CLI, integration, or major subsystem.
    0
    installs
21. ▌
    Audit Rendered UI · jlave-dev bundle

    Use when reviewing screenshots or rendered frontend UI for leaky copy, redundancy, visual clutter, responsive fit, broken assets, or handoff polish.
    0
    installs
22. ▌
    Reference Ruler UI · jlave-dev bundle

    Use when matching a frontend implementation to a concrete visual reference: image-to-code UI work, mockup or screenshot replication, screenshot-driven polish, pixel-fidelity repair loops, or generated mockups that need faithful implementation.
    0
    installs