ugudlado

Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.

QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.

Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.

Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.

Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.

Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.

Review design.md and tasks.yaml for completeness and quality. Use when reviewing a design before implementation.

Produce design.md and tasks.yaml from discovery. Use when designing a feature, drafting an approach, or breaking work into tasks.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.

Expert in backend architecture, service patterns, testing, and API development using Express.js, TypeScript, and Drizzle ORM. Use when implementing backend services, APIs, controllers, database queries, error handling, testing server code, or writing migrations.

Expert in web app frontend architecture, React patterns, TypeScript, TanStack Query, Zustand, and component development with strong type safety. Use when building UI components, implementing data fetching, managing state, writing forms, styling with Tailwind, testing React components, or integrating with backend APIs.

Expert in mobile app architecture using Expo, React Native, TypeScript, and Zustand. Use when building mobile screens, implementing navigation, managing state, styling components, integrating with backend APIs, or handling platform-specific functionality.

Use when working on the VS Code extension — building, packaging, versioning, installing, type-checking, or developing extension features. Triggers when user mentions "vscode extension", "build extension", "package vsix", "extension version", "vsce", "extension development", or when modifying files under src/.

Use when working with GitHub — creating releases, managing issues, pull requests, checking CI status, uploading release assets, or any gh CLI operations. Triggers when user mentions "github release", "gh release", "upload to github", "create release", "github pages", "pull request", "gh pr", "github issue", or any GitHub repository management task.

This skill should be used when the user asks to 'create a hook rule', 'write a YAML rule', 'add a match rule', 'add a script rule', 'add a prompt rule', 'block a command', 'deny a tool', 'add a hook', 'configure hook behavior', 'list my hooks', 'show registered hooks', 'hooksmith list', 'hooksmith eval', 'hooksmith convert', 'hooksmith init', 'convert hooks to rules', 'migrate hooks', 'import hooks from settings', 'convert settings.json hooks', or is working with hooksmith YAML rule files. Provides the CLI interface, rule file format, result-event compatibility, and examples for match, run, and prompt mechanisms.

Prepare a release — changelog, version bumps, and git tag

This skill should be used when running any shell command that has an RTK equivalent — including "git status", "ls", "grep", "find", "cat/head/tail", "pnpm test", "cargo build", "curl", "gh", "docker", "kubectl", "vitest", "pytest", "tsc", "eslint", and any other CLI operation where token savings apply. Also use when the user asks about "rtk gain", "token savings", "rtk discover", or "why use rtk".