Architectural code analysis for design quality. Evaluates simplicity (Rich Hickey), functional core/imperative shell (Gary Bernhardt), and coupling (Constantine & Yourdon). Use for design review or architectural assessment.

deep-debug

>

Generates step instruction files and syncs slash commands from the job.yml specification. Use after job spec review passes.

Reviews job.yml against quality criteria using a sub-agent for unbiased validation. Use after defining a job specification.

Creates a rule file that triggers when specified files change. Use when setting up documentation sync, code review requirements, or automated commands.

Creates file-change rules that enforce guidelines during AI sessions. Use when automating documentation sync or code review triggers.

Locate symbol definitions quickly (precise for Python via AST; conservative candidates for other languages) and print a bounded context packet.

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

**Description**: Validate completed work against issue requirements and acceptance criteria. Use when finishing work on an issue to ensure all requirements are met.

Review what should be delegated

Create a Delegation Pack (delegation brief, decision rights, context handoff, check-in cadence, review plan, debrief). Use for delegation, letting go, empowering reports, and avoiding micromanagement.

Create structured GitHub Issues for client deliverables after clarity phases establish shared understanding.

A demo skill that helps with documentation

Mandates the usage of UV when installing dependencies to ensure consistency and efficiency across all environments.

Reviews package dependencies for security vulnerabilities, outdated versions, and license compliance. Use when user asks about dependencies, security audits, or before releases.

Check for required dependencies (Chrome DevTools MCP, OpenRouter API) before running commands that need them. Use at the start of /implement, /review, /validate-ui commands to provide helpful setup guidance.

Detect and resolve package dependency conflicts before installation across npm/yarn/pnpm, pip/poetry, cargo, and composer. Auto-trigger when installing/upgrading packages. Validates peer dependencies, version compatibility, security vulnerabilities. Auto-resolves safe conflicts (patches, dev deps), suggests manual review for breaking changes. Prevents conflicting versions, security vulnerabilities, broken builds.

Review code for proper DI patterns using DryIoc. Ensures no static singletons, validates constructor injection and service lifetimes. Use when reviewing code, refactoring static access, or debugging DI issues.

Scan codebase to identify opportunities to replace custom implementations with well-maintained open source libraries. Creates worktree, implements changes, and submits PR for review. Multi-phase workflow with parallel analysis agents.

Enforce dependency security scanning and SBOM generation. Use when adding dependencies, reviewing package.json, or during security audits. Covers OWASP dependency check, npm audit, and supply chain security.

Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs.

Deploy applications to Railway. Use when deploying services, databases, or full-stack applications to Railway PaaS. Covers Railway CLI and configuration.

Deploy workflow for Vercel and Supabase Edge Functions

Expert DevOps automation consultant for building production-grade CI/CD deployment pipelines using Vercel, GitHub Actions, and Railway. Implements build/test/preview/production workflows, automated rollbacks, canary deployments, blue-green strategies, environment promotion, secrets management, health checks, smoke testing, and live monitoring. Use when deploying web applications, setting up CI/CD pipelines, configuring automated deployments, implementing deployment strategies, managing production releases, or troubleshooting deployment issues.

Pre-deployment validation checklist and automated readiness assessment.

Ensure safe, reliable deployments with comprehensive checklists.

Pre-deployment verification steps and checks

Phase sizing, scope boundaries, and anti-patterns. Load when evaluating whether a phase is well-formed or needs splitting.

Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories.

Plan-Build-Review cycle and agent handoffs. Load when transitioning between agents or understanding workflow progression.

Generate comprehensive PR descriptions following repository templates

Structure and field ownership for progress.yaml. Load when reading or updating phase progress state.

Structure and sections for review.md. Load when creating review scaffolds or recording review findings.

Core Ushabti concepts and development lifecycle. Load when starting any Ushabti workflow or orienting to the framework.

Generate a PR description for the current branch. Writes Markdown to .git/magit/posts/new-pullreq for use with magit-forge.

Compare doc versions across git history. Use when reviewing changes, tracking evolution, or understanding modifications.

design-jira-state-analyzer

Build and present HTML/CSS design mockups with a local preview server. Use when prototyping website designs, iterating on visual concepts, or presenting design options.

>

>

Reviews finished and in-progress digital products to assess adherence to design specifications and discover potential issues with those specifications. Validates implementation against design intent, identifies visual and interaction discrepancies, and provides actionable feedback for design and engineering teams.

Generate status reports for design documentation. Use when creating documentation summaries, tracking progress, or preparing documentation reviews.

Review UI components for design system compliance, accessibility, and visual consistency

Facilitate a cross-functional design review capturing decisions, feedback, and implementation guidance.

Review and analyze design docs for health, quality, and improvement opportunities. Use when auditing design documentation, checking doc health, or identifying areas for improvement.

Verify code implementation aligns with design specifications. Use after implementing features, during code reviews, or when refactoring to ensure architectural compliance. Compares design docs with actual code.

Review design system usage and gaps

[Design System] Validate that code and styles use official design tokens instead of hard-coded values. Use when (1) reviewing CSS/SCSS/Tailwind/styled-components for hard-coded colors/spacing, (2) checking SwiftUI/UIKit for raw color/font values, (3) auditing Unity styles for magic numbers, (4) enforcing design system compliance, (5) user asks to 'check design tokens', 'validate tokens', 'find hard-coded values', or 'audit design system usage'.

Guides REST and GraphQL API design, endpoint patterns, request/response schemas, versioning, and API best practices. Use when building APIs, designing endpoints, or reviewing API contracts.