lttr
- 32 skills
- 0 followers
- 1 week ago last updated
- ▌ Aiwork Protocol · lttrStructure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
- ▌ Grill With Docs · lttr bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ Playwright CLI · lttr bundleAutomate browser interactions, test web pages and work with Playwright tests.
- ▌ Ticket Create · lttrCreate an Azure DevOps work item (Technical task / User Story / Bug …) with a Markdown description, parent link, area/iteration, and tags, in a single `az rest` call. Trigger when the user says "create azdo ticket", "new work item", "create technical task", "child ticket under
- ▌ Code Review Diff · lttr bundleReview code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.
- ▌ Feature Branch · lttrCreate a feature branch from an Azure DevOps ticket. Fetches ticket title, slugifies, creates `feature/<id>-<slug>`, and optionally transitions ticket to Active. Trigger when user says "feature branch", "create branch", "/dev-azdo:feature-branch", or provides a ticket id/URL to start work on.
- ▌ Ticket Comments · lttrAdd, update, or delete a comment on an Azure DevOps work item (the Discussion thread) via the dedicated Comments REST API, with Markdown rendering. Trigger when the user says "comment on ticket
- ▌ Browser Tools · lttr bundleUse this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.
- ▌ Video To Article · lttr bundleUse this skill when the user wants to convert a lecture, presentation, or talk video into text formats (transcript, outline, or article). Trigger when user mentions processing video recordings, creating transcripts from lectures, or generating articles from recorded presentations.
- ▌ Code Review · lttr bundleReview code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.
- ▌ Changelog · lttr bundleShow recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.
- ▌ Triage · lttr bundleTriage requirements, specs, or tickets. Detect input (pasted text, markdown path, tracker ticket id/URL, or empty prompt). Explore codebase + docs, score completeness, ask clarifying questions, write a markdown report. Trigger when user says "triage", "review this spec", "is this requirement complete", or provides a ticket/spec to assess.
- ▌ To Spec · lttrTurn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.
- ▌ Showme · lttrOpen a real (headed) browser, drive it to a specific state in a web app — a feature, a flow, a particular screen, or a bug — then leave the window open for the user to click around in, with a short note on what to try and what to watch for. Use when the user wants to "show me X", "take me to that state/screen", "let me click around in it", "open a browser I can play with", "set up the repro", "drive me to <feature/flow/situation>", or describes any app state they want to experience firsthand.
- ▌ Docs Checker · lttr bundleAudit context files (CLAUDE.md, .claude/ tree, READMEs, docs) for broken references and verifiably stale content. Runs a deterministic offline link/path checker first, then a bounded semantic review where every finding must cite evidence. Reports findings; fixes only on request.
- ▌ Ticket · lttrTransition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/dev-azdo:ticket", or wants to move a work item between states (active, code-review, ready, closed).
- ▌
- ▌ Prototype · lttr bundleBuild a throwaway prototype that answers one design question. Plain HTML/CSS/JS in the task's .aiwork/ folder by default, or UI variants inside the app (Nuxt/Vue, ...) on a prototype branch when they must sit against real layout and data. Use for "does this state model feel right" or "what should this look like".
- ▌
- ▌ Skill Creator · lttrGuide for creating and editing Claude Code skills. Use when user wants to create a new skill, create a new slash command (skills are the unified primitive - commands live in skills/ now), update an existing skill, or needs help structuring a SKILL.md file.
- ▌ To Tickets · lttrBreak a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.
- ▌ Memory Promote · lttrAudit this repo's auto-memory files and suggest promoting each one to a more persistent layer — user or repo CLAUDE.md, an existing or new skill, a settings.json hook, or a checked-in reference doc. Use when the user says "audit memory", "promote memory", "clean up memories", "memory-promote", or wants to move ephemeral memory into durable config.
- ▌ Plugin Creator · lttr bundleThis skill should be used when creating, modifying, or managing Claude Code plugins and plugin marketplaces. Trigger when working with plugin manifests (plugin.json, marketplace.json), creating plugin directory structures, adding plugin components (commands, skills, agents, hooks), version bumping, or when discussing plugin development workflows.
- ▌ Insights · lttr bundleGenerate codebase activity summaries (daily/weekly/catchup/view) from Azure DevOps PRs, work items, local git, and optionally Confluence. Trigger when user says "/dev-azdo:insights", asks "what happened", "codebase activity", "team summary", or wants a PR/commit roll-up.
- ▌ Page Bridge · lttr bundleInject a floating toolbar into a running dev page so the user can point at elements and comment on them, and have that arrive as a live notification. Use when iterating on a UI together in the browser, when the user says "page bridge", or asks to show you which element they mean.
- ▌ Pr Comments · lttrManage Azure DevOps PR comments — post new code comments, read and assess existing threads. Trigger when user says "/dev-azdo:pr-comments", asks to add/post a comment on a PR, review PR feedback, or check PR comment status. Input is PR id/URL, or empty to use current branch's PR.
- ▌ Implement Spec · lttrImplement a whole spec by orchestrating subagents over its ticket graph; auto-detects the most recent task folder when no argument is given.
- ▌ Nuxt · lttr bundleThis skill should be used when working on Nuxt projects (v3+). Use it for building Vue applications with Nuxt's file-based routing, server-side rendering, and auto-import features. Trigger when working with .vue or .ts files in Nuxt directories (pages/, server/, composables/, middleware/), nuxt.config.ts, or when the project contains a nuxt dependency in package.json. Also trigger for questions about Nuxt concepts like composables, auto-imports, server routes, SSR/SSG patterns, or file-based routing.
- ▌ Tdd · lttr bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌
- ▌ Pr · lttr bundleManage Azure DevOps pull requests — create, checkout, list, complete. Trigger when user says "/dev-azdo:pr <op>", "create PR", "checkout PR 123", "list PRs", "complete PR", or otherwise asks to operate on an AZDO pull request.
- ▌ Pick · lttr bundlePick an element from the browser by clicking it (starts the dev server if needed) and get back its CSS selector, tag, classes, and text. Manual only.