ultra-skill

Plugin ultra-skill from marketplace ultra-skill in amirudinR/Ultra-Skill. Commands read from the repo's manifest — 1 month ago.

Skills (46)

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• ultra-observability

  Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the availabl

• ultra-ci-cd

  Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

• ultra-deprecation

  Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

• ultra-documentation

  Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

• ultra-shipping

  Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

• ultra-finishing-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

• ultra-git-workflow

  Structures git workflow practices with workspace isolation. Use when making any code change. Use when committing, branching, resolving conflicts, organizing parallel workstreams, cutting a release, choosing a semver bump, tagging, or writing a changelog.

• ultra-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

• ultra-brainstorming

  You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Combines divergent→convergent ideation with hard-gate design-first workflow. Turns raw ideas into approved specs through structured dialogue.

• ultra-interview-me

  Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invo

• ultra-spec-driven-dev

  Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are clear enough to formalize after ideation. The spec is the shared source of truth between you and the human engineer — code without a spec is guessin

• ultra-api-design

  Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

• ultra-context-engineering

  Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

• ultra-incremental-impl

  Delivers changes incrementally in thin vertical slices with plan-driven execution. Use when implementing any feature or plan that touches more than one file, or when executing a written implementation plan with review checkpoints.

• ultra-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• ultra-source-driven-dev

  Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

• ultra-subagent-dev

  Use when executing implementation plans with independent tasks in the current session by dispatching fresh subagents per task with two-stage review.

• ultra-using-skills

  Use when starting any session or when you need to discover which Ultra Skill applies to the current task. This is the meta-skill that governs how ALL skills in the Ultra Skill collection are discovered, loaded, and invoked.

• ultra-writing-skills

  Use when creating new Ultra Skills, editing existing skills, or verifying skills work before deployment

• ultra-impact-gain

  Show ultra-ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ultra-impact-gain, "ultra gain", "what does ultra save", "show ultra impact", "ultra scoreboard".

• ultra-ponytail

  Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before

• ultra-yagni-audit

  Whole-repo audit for over-engineering. Like ultra-ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete fro

• ultra-yagni-debt

  Harvest every `ultra:` and `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals left behind get tracked instead of rotting into "later means never". Use when the user says "yagni debt", "/ultra-yagni-debt", "what did yagni defer", "list the shortcuts", "u

• ultra-planning

  Decompose work into ordered, bite-sized tasks with dependency graphs and vertical slices. Use when you have a spec or clear requirements and need a detailed plan before touching code.

• ultra-writing-plans

  Write comprehensive implementation plans for isolated execution. Use when you have a spec or requirements for a multi-step task and need a detailed, executable plan for an engineer with zero codebase context.

• ultra-code-review

  Conducts multi-axis code review merging correctness, over-engineering detection, and review reception best practices. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it e

• ultra-code-simplify

  Simplifies code for clarity using pragmatic YAGNI principles. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

• ultra-performance

  Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

• ultra-security

  Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

• ultra-verify-before-done

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• ultra-browser-testing

  Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MC

• ultra-doubt-driven-dev

  Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be che

• ultra-tdd

  Two-mode Test-Driven Development — Standard (pragmatic) and Strict (iron law). Use when implementing logic, fixing bugs, or changing behavior. Default: Strict mode. Switch to Standard mode only for low-risk, well-understood work.

• ultra-banner-design

  Multi-platform banner design — social media covers, ad banners, website heroes, print. 22 art direction styles. Uses Ultra Design Engine for design intelligence, style search, and color/typography recommendations. Design-to-code workflow with HTML/CSS → PNG export.

• ultra-brand-identity

  Brand voice, visual identity, logo generation concepts, CIP (Corporate Identity Program) mockups, iconography system, color palette + typography for branding. Integrates with Ultra Design Engine design intelligence for data-driven brand decisions.

• ultra-design-system

  Design system generation using Ultra Design Engine intelligence — three-layer token architecture (primitive→semantic→component), CSS variables pattern, design system persistence (Master + Overrides), mobile-first responsive approach, component specs, pre-delivery checklist.

• ultra-frontend-eng

  Production-quality frontend engineering — component architecture, file structure, React patterns, accessibility, responsive design, state management. Cross-references ultra-ui-styling, ultra-design-system, ultra-brand-identity for full design system integration.

• ultra-slides

  Strategic HTML presentation creation with Chart.js data visualization, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies. Integrates with Ultra Design Engine for brand-aligned design tokens, color palettes, typography, and chart recommendations.

• ultra-ui-styling

  Comprehensive UI styling skill — searches 67 UI styles (glassmorphism, brutalism, neumorphism, etc.), 193 color palettes, 75 font pairings, 1924 Google Fonts, and 1776 design patterns from the Ultra Design Engine database. Uses BM25 search engine for style, color, typography, and design recommendati

• banner-design

  Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist,

• brand

  Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

• design-system

  Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

• design

  Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), soci

• slides

  Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

• ui-styling

  Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialo

Slash commands (14)

• /ultra-skill:ultra-brainstorm
• /ultra-skill:ultra-build
• /ultra-skill:ultra-debug
• /ultra-skill:ultra-impact-gain
• /ultra-skill:ultra-plan
• /ultra-skill:ultra-ponytail
• /ultra-skill:ultra-review
• /ultra-skill:ultra-ship
• /ultra-skill:ultra-simplify
• /ultra-skill:ultra-spec
• /ultra-skill:ultra-test
• /ultra-skill:ultra-webperf
• /ultra-skill:ultra-yagni-audit
• /ultra-skill:ultra-yagni-debt

Subagents (4)

• code-reviewer

  Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.

• security-auditor

  Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

• test-engineer

  QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

• web-performance-auditor

  Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.

Hooks (2)

• SessionStart

  SCRIPT="${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"; [ -f "$SCRIPT" ] || SCRIPT="${CLAUDE_PROJECT_DIR}/.claude/hooks/session-start.sh"; [ -f "$SCRIPT" ]&& bash "$SCRIPT" || true

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

Similar plugins