Results for “kodo”

Vibe Code Orchestrator (VCO) is a governed runtime entry that freezes requirements, plans XL-first execution, and enforces verification and phase cleanup.

Transform code files into learning resources by adding educational comments that explain syntax, idioms, and design choices.

COCO: Microsoft COCO: Common Objects in Context

You are an expert in Koa, the minimalist web framework created by the Express team. You help developers build APIs and web services using Koa's async/await middleware stack, context object, and composable architecture — providing a lightweight foundation where you add only what you need through middleware, without bundled routing or templating.

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

Language-specific super-code guidelines for go.

Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.

Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.

Switches Claude Code into a teaching-first mode for unfamiliar technologies, explaining concepts and commands step by step without writing code until approved.

Generates premium website design images, then deeply analyzes them to implement faithful frontend code for hero sections, landing pages, and marketing sites.

Code Cleanup

Measures code quality, identifies code smells, and implements quality gates using static analysis and technical debt tracking.

Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Kotest — flexible, idiomatic Kotlin testing framework. Multiple specification styles (StringSpec, FunSpec, BehaviorSpec, DescribeSpec, FeatureSpec, FreeSpec), rich matcher library, property-based testing, data-driven tests, coroutine support, KMP-friendly. Drop-in alternative or complement to JUnit. USE WHEN: user mentions "Kotest", "io.kotest", "shouldBe", "StringSpec", "BehaviorSpec", "DescribeSpec", "kotest property testing", "Arb.list", "forAll", "kotest matchers", "kotlin tests" DO NOT USE FOR: JUnit-specific patterns - use junit skill (or framework-specific test skills) DO NOT USE FOR: Flow testing - use `testing/turbine` DO NOT USE FOR: Compose snapshot tests - use `testing/compose-snapshot` DO NOT USE FOR: Mobile E2E - use `testing/maestro`

Analyze a codebase with specialized agents and propose refactoring tickets.

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable applications.

Runs Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.

Go programming patterns and idioms

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.

Assists with software engineering tasks including writing, editing, and explaining code, searching codebases, running commands, managing files, debugging, and implementing features.

Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.

Write idiomatic Kotlin 1.9+ with null safety, sealed classes, data classes, extension functions, delegates, collections, inline/reified generics, and expression syntax. Use for Kotlin language constructs, Java-to-Kotlin migration, lazy delegates, data classes, backing properties, or inline/reified generics; keep language constructs in scope even inside response models, and defer coroutine configuration, Android Context/framework, Retrofit/OkHttp client setup, and other library-specific recipes.

Enforces idiomatic Kotlin conventions for null safety, immutability, sealed classes, coroutines, extension functions, DSL builders, and Gradle Kotlin DSL.

KOMODO v1.0 — Momentum Event Consensus. Uses leaderboard_get_momentum_events (real-time threshold crossings) to detect when 2+ quality SM traders cross momentum thresholds on the same asset/direction within 60 minutes. Confirmed by market concentration + volume. Enters with the momentum. Replaces MANTIS v1.0 and SCORPION v1.1 (both used stale position data).