tundraray-overture

Plugin tundraray-overture from marketplace cascade-code-general-misc-4 in joshuarweaver/cascade-code-general-misc-4. Commands read from the repo's manifest — 1 month ago.

Skills (33)

• typescript-rules-backend

  This skill provides backend TypeScript development rules including functions-over-classes design, NestJS/TypeORM patterns, layered error handling, streaming, and memory management. Automatically loaded when implementing backend TypeScript services, APIs, or when "NestJS", "backend TypeScript", "API

• typescript-testing-backend

  This skill provides backend testing rules with Vitest, real DB/API integration patterns, and service-level testing conventions. Automatically loaded when writing backend tests, reviewing test quality, or when "backend test", "service test", "API test", "integration test", "database test", or "backen

• documentation-criteria

  This skill should be used when the user asks to "create a PRD", "write an ADR", "create a design doc", "make a work plan", "create task files", or needs guidance on document templates, creation criteria, or determining which documents are required for a given change scope.

• game-analysis-criteria

  This skill provides templates, analysis frameworks, and quality criteria for game reverse-engineering and competitive analysis. Used when analyzing external games for mechanics, technology, marketing, retention, and market positioning. Loaded by game-researcher agent and game-analyze command.

• subagents-gamedev-orchestration

  This skill guides subagent coordination through game development workflows. Automatically loaded when orchestrating multiple agents, managing workflow phases, determining autonomous execution mode, or when "orchestration", "workflow phases", "scale determination", "stop points", or "autonomous mode"

• javascript-expert

  Use when building JavaScript applications with modern ES2024+ features, async patterns, or Node.js development. Invoke for vanilla JavaScript, browser APIs, performance optimization, module systems, security hardening.

• nestjs-expert

  Use when building NestJS applications requiring modular architecture, dependency injection, or TypeScript backend development. Invoke for modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma, CQRS, advanced DI, security hardening, database patterns.

• nextjs-developer

  Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.

• playwright-expert

  Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing, CI/CD pipeline optimization.

• postgres-expert

  Use when optimizing PostgreSQL queries, configuring replication, designing partitioning strategies, hardening security, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, transaction isolation, performance monitoring.

• ai-development-guide

  This skill provides technical decision criteria, anti-pattern detection, debugging techniques, and quality check workflow. Automatically loaded when making technical decisions, detecting code smells, performing quality assurance, or when patterns like "code smell", "anti-pattern", "technical debt",

• brand-system-guide

  This skill enforces brand design standards including OKLCH color palette, AI gradient usage, accessibility compliance (WCAG 2.1 AA), dark mode patterns, and CSS utility classes. Automatically loaded when implementing UI components, styling, ensuring visual consistency, or when "brand colors", "OKLCH

• coding-principles

  This skill provides language-agnostic coding principles for maintainability, readability, and quality. Automatically loaded when implementing features, refactoring code, reviewing code quality, or when the user mentions "clean code", "best practices", "code quality", or "maintainability".

• expert-analysis-guide

  Multi-perspective expert analysis framework for pre-design evaluation. Automatically loaded when orchestrating expert analysis, spawning parallel expert agents, or when "expert analysis", "multi-perspective", or "parallel analysis" are mentioned.

• frontend-ai-guide

  This skill provides frontend-specific technical decision criteria, anti-patterns, debugging techniques, and quality check workflow. Automatically loaded when making frontend technical decisions, performing React/TypeScript quality assurance, or when "React anti-pattern", "frontend code smell", or "c

• implementation-approach

  This skill provides implementation strategy selection framework with meta-cognitive approach, verification levels, and integration point definitions. Automatically loaded when planning implementation strategy, selecting development approach, defining verification criteria, or when "vertical slice",

• integration-e2e-testing

  This skill provides integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Automatically loaded when designing integration tests, E2E tests, reviewing test quality, or when "integration test", "E2E test", "end-to-end", "test skeleton", or "acce

• project-context

  This skill provides project-specific context including project nature, technology stack, and implementation principles. Automatically loaded to understand project constraints and conventions. Should be customized for each project via /setup-context.

• rule-editing-guide

  9 principles for writing effective rules that maximize LLM execution accuracy. Use when creating or modifying skills, agent prompts, or command instructions.

• security-checks

  Security patterns and detection rules for automated code review. Automatically loaded when performing security reviews, checking for vulnerabilities, or when "security check", "vulnerability", "CVE", "security patterns", or "security audit" are mentioned.

• skill-optimization

  Optimization patterns and grading system for skill quality assessment. Automatically loaded when creating new skills, evaluating skill quality, reviewing skill content, or when "skill optimization", "skill quality", "BP pattern", "skill grading", or "skill assessment" are mentioned.

• subagents-orchestration-guide

  This skill guides subagent coordination through implementation workflows. Automatically loaded when orchestrating multiple agents, managing workflow phases, determining autonomous execution mode, or when "orchestration", "workflow phases", "scale determination", "stop points", or "autonomous mode" a

• task-analyzer

  This skill should be used when the user asks to "analyze this task", "determine task complexity", "select skills for task", "estimate work scale", or needs guidance on metacognitive task analysis. Returns skills with confidence scores and metadata.

• technical-spec

  This skill provides technical design rules including environment variable management, architecture design, and build/testing commands. Automatically loaded when discussing architecture, environment variables, build commands, or when "tech stack", "architecture pattern", "environment config", or "bui

• testing-principles

  This skill provides language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Automatically loaded when writing tests, designing test strategies, reviewing test quality, or when the user mentions "TDD", "test coverage", "unit tests", or "test pat

• type-safety-standards

  Frontend type safety patterns for React/TypeScript including runtime validation with Zod, discriminated unions, branded types, type guards, and performance optimization. Automatically loaded when implementing API integrations, form handling, state management with strict typing, or when "Zod schema",

• typescript-rules

  This skill provides React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Automatically loaded when implementing React components, TypeScript code, frontend features, or when "React component", "TypeScript types", "state management

• typescript-testing

  This skill provides frontend testing rules with Vitest, React Testing Library, and MSW. Automatically loaded when writing frontend tests, reviewing test quality, or when "Vitest", "React Testing Library", "MSW", "component test", or "frontend test coverage" are mentioned.

• ajtbd-methodology
• product-execution
• strategy-documentation-criteria
• strategy-orchestration-guide
• strategy-overture

Slash commands (22)

• /tundraray-overture:add-integration-tests

  Add integration/E2E tests to existing backend codebase using Design Doc

• /tundraray-overture:audit

  Interactive codebase audit to find and remove dead code and suspicious areas

• /tundraray-overture:brand-context

  Inject brand-specific design system into brand-system-guide skill

• /tundraray-overture:build

  Execute decomposed tasks in autonomous execution mode

• /tundraray-overture:create-plan

  Create work plan from design document and obtain plan approval

• /tundraray-overture:create-skill

  Create a new skill through guided interactive dialog with quality review

• /tundraray-overture:design

  Execute from requirement analysis to design document creation

• /tundraray-overture:diagnose

  Investigate problem, verify findings, and derive solutions

• /tundraray-overture:front-build

  Execute frontend implementation in autonomous execution mode

• /tundraray-overture:front-design

  Execute from requirement analysis to frontend design document creation

• /tundraray-overture:front-plan

  Create frontend work plan from design document and obtain plan approval

• /tundraray-overture:front-reverse-design

  Generate frontend Design Docs from existing codebase using existing PRD

• /tundraray-overture:front-review

  Design Doc compliance validation with optional auto-fixes

• /tundraray-overture:implement

  Orchestrate the complete implementation lifecycle from requirements to deployment

• /tundraray-overture:refine-skill

  Implement user skill change requests with maximum precision optimization

• /tundraray-overture:reverse-engineer

  Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow

• /tundraray-overture:review

  Design Doc compliance validation with optional auto-fixes

• /tundraray-overture:setup-context

  Inject project-specific context into project-context skill SKILL.md

• /tundraray-overture:sync-skills

  Synchronize skill metadata and optimize rule-advisor precision after skill edits

• /tundraray-overture:task

  Execute tasks following appropriate rules with rule-advisor metacognition

• /tundraray-overture:update-doc

  Update existing design documents (Design Doc, PRD, ADR) with review workflow

• /tundraray-overture:uxdoc

  Execute from requirement analysis to UX Requirement Documentation (UXRD) creation

Subagents (27)

• acceptance-test-generator

  Generates high-ROI integration/E2E test skeletons from Design Doc ACs. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.

• cleanup-executor

  Safely removes confirmed dead code with git backup, build verification, and dependency-order deletion. Use after codebase-scanner findings are reviewed and approved for removal.

• code-reviewer

  Validates Design Doc compliance and implementation completeness from third-party perspective. Use PROACTIVELY after implementation completes or when "review/implementation check/compliance" is mentioned. Provides acceptance criteria validation and quality reports.

• code-verifier

  Validates consistency between PRD/Design Doc and code implementation. Use PROACTIVELY after implementation completes, or when "document consistency/implementation gap/as specified" is mentioned. Uses multi-source evidence matching to identify discrepancies.

• codebase-scanner

  Scans for dead code, orphan files, unused exports, and suspicious areas. Use PROACTIVELY when audit/cleanup/dead-code analysis is needed. Reports findings without making changes.

• design-sync

  Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.

• document-reviewer

  Reviews document consistency and completeness, providing approval decisions. Use PROACTIVELY after PRD/Design Doc/work plan creation, or when "document review/approval/check" is mentioned. Detects contradictions and rule violations with improvement suggestions.

• expert-analyst

  Parallel multi-perspective analysis from expert viewpoint. Use when orchestrator needs pre-design expert evaluation of a specific aspect (Security, API Design, Architecture, Performance, Data Modeling, Testability, Error Handling, UX Impact).

• integration-test-reviewer

  Verifies consistency between test skeleton comments and implementation code. Use PROACTIVELY after test implementation completes, or when "test review/skeleton verification" is mentioned. Returns quality reports with failing items and fix instructions.

• investigator

  Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports only observations without proposing solutions.

• prd-creator

  Creates and updates Product Requirements Documents (PRD) in docs/prd/. Responsible for defining product requirements, user stories, success metrics, feature scope, and MoSCoW prioritization. Use PROACTIVELY when "requirements", "user story", "feature definition", "what to build", "product scope", or

• quality-fixer-frontend

  Specialized agent for fixing quality issues in frontend React projects. Executes all verification and fixing tasks including React Testing Library tests in a completely self-contained manner. Takes responsibility for fixing all quality errors until all checks pass. MUST BE USED PROACTIVELY when any

• quality-fixer

  Specialized agent for fixing quality issues in software projects. Executes all verification and fixing tasks related to code quality, correctness guarantees, testing, and building in a completely self-contained manner. Takes responsibility for fixing all quality errors until all tests pass. MUST BE

• requirement-analyzer

  Performs requirements analysis and work scale determination. Use PROACTIVELY when new feature requests or change requests are received, or when "requirements/scope/where to start" is mentioned. Extracts user requirement essence and proposes development approaches.

• rule-advisor

  Selects optimal rulesets for tasks and performs metacognitive analysis. MUST BE USED before any implementation task starts (CLAUDE.md required process). Analyzes task essence with task-analyzer skill and returns structured JSON.

• scope-discoverer

  Discovers PRD/Design Doc scope from existing codebase. Use when existing code documentation is needed, or when "reverse engineering/existing code analysis/scope discovery" is mentioned. Identifies targets through multi-source discovery.

• security-reviewer

  Reviews implementation for security compliance against Design Doc security considerations and coding-principles Security Principles. Use when "security review", "security check", "vulnerability assessment", or "security audit" is mentioned. Provides structured security findings with severity classif

• solver

  Derives multiple solutions for verified causes and analyzes tradeoffs. Use when verifier has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.

• task-decomposer

  Reads work plan documents from docs/plans and decomposes them into independent, single-commit granularity tasks placed in docs/plans/tasks/<plan-name>/. PROACTIVELY proposes task decomposition when work plans are created.

• task-executor-frontend

  Executes frontend implementation completely self-contained following task files from docs/plans/tasks/<plan-name>/. Use when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

• task-executor

  Executes implementation completely self-contained following task files from docs/plans/tasks/<plan-name>/. Use when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

• technical-designer-frontend

  Creates and updates frontend ADR (docs/adr/) and Design Documents (docs/design/). Responsible for frontend architecture, component hierarchy, state management, React/TypeScript patterns, and UI component design. Use PROACTIVELY when "component architecture", "React design", "frontend structure", "st

• technical-designer

  Creates and updates ADR (docs/adr/) and Design Documents (docs/design/). Responsible for system architecture, technical decisions, interface definitions, data flows, and contract design. Use PROACTIVELY when "architecture", "technical design", "system design", "API design", "data model", "ADR", or "

• ui-spec-designer

  Creates UI Specifications from PRD and optional prototype code. Analyzes acceptance criteria, maps to screens/components, and creates state-display matrices. Use when "UI specification", "component spec", "screen design", "state matrix", or "ui-spec" is mentioned.

• ux-designer

  Creates and updates UX Requirement Documentation (UXRD) in docs/uxrd/. Responsible for user experience design, interaction patterns, user flows, wireframes, accessibility requirements (WCAG), and visual specifications. Use PROACTIVELY when "UX", "user experience", "wireframe", "user flow", "interact

• verifier

  Critically evaluates investigation results and identifies oversights using ACH and Devil's Advocate methods. Use when investigator has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.

• work-planner

  Creates and updates work plan documents in docs/plans/. Responsible for implementation planning, phase breakdown, dependency mapping, risk identification, and progress tracking. Use PROACTIVELY when "implementation plan", "work breakdown", "task planning", "phasing", or "work plan" is mentioned.

Similar plugins