yonatangross
- 184 skills
- 0 followers
- 303 repo stars
- 2 days ago last updated
- ▌ Disk Cleanup · yonatangross bundleFrees the disk that agents and worktrees leave behind: caches, merged worktrees, Docker build cache, old logs. Dry run lists safe, regenerable and ask-first items with sizes; --apply after you confirm. Use when the disk is nearly full. Never deletes branches.
- ▌ Swarm Migrate 2 · yonatangrossCross-repo migration swarm: one coordinator and a subagent per repo apply the same change, open PRs, wait for CI, and log to a shared ledger. Use for org-wide dependency bumps or codemods. Not for one repo (use implement).
- ▌ Design To Code 2 · yonatangross bundleMockup to React component via Stitch, 21st.dev and Storybook MCP, reusing existing components first. Use when building UI from a mockup or screenshot. To call Storybook MCP tools alone, use storybook-mcp-integration.
- ▌ Visualize Plan 2 · yonatangross bundleRenders planned changes as before/after architecture, risk heat maps, execution order and dependency graphs in ASCII, HTML or NotebookLM. Use when reviewing a plan. Not for an inline chart (use glyph).
- ▌ Ork Glyph · yonatangross bundleRender an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets, comparisons, rankings, pipelines, or requests to show something visually. Do not use for definitions, conceptual explanations, one-sentence answers, or requests for a saved page or file.
- ▌ Component Search 2 · yonatangross bundleSearches the 21st.dev registry for production React components, ranked with install steps. Use when looking for a UI component or an alternative to one.
- ▌ Review Artifact Comments · yonatangross bundleWorks through review comments in a plan or research artifact: replies, resolves, hands off to iterate-plan or iterate-research, approves when none are open. Use when an artifact file has reviewer comments.
- ▌ Design Stylecards 2 · yonatangross bundleCatalog of named aesthetic recipes: shadow stacks, glass, gradients, type scales as copy-paste values. Use for polished elevation, glassmorphism, mesh backgrounds or any make-it-look-like-X ask.
- ▌ Design Context Extract 2 · yonatangross bundleExtracts design DNA from screenshots, URLs or recordings: colors, type, spacing, components and motion as tokens or Tailwind config. Use when asked to extract or audit a design or match a visual identity.
- ▌ Implement 2 · yonatangross bundleBuilds a new feature with parallel backend, frontend, test and security agents in worktrees, then verifies. Use when asked to build, add or scaffold a feature, endpoint or component. Not for fixing, reviewing or testing existing code.
- ▌ Review Pr 2 · yonatangross bundlePR review by parallel agents (quality, security, tests, architecture, performance) with conventional comments and an approve or request-changes verdict. Use when a pull request needs a reviewer. Not for design scores (use assess).
- ▌ Write Prd 2 · yonatangross bundleProduct Requirements Documents: 8-section template, user stories, acceptance criteria, go/no-go. Use when writing a PRD or user stories.
- ▌ Brainstorm 2 · yonatangross bundleDesign ideation with parallel agents: 10+ ideas, feasibility filter, devil's-advocate scoring, trade-offs. Use when brainstorming or comparing alternatives. Not for building or fixing code (use implement or fix-issue) or scoring a design (use assess).
- ▌ CI Sentinel 2 · yonatangrossManually dispatched classifier for every open PR with a failed check: runs ci-debug headless, posts a collapsed verdict per PR. Proposes only, never pushes. Use for all red PRs; for one run, use ci-debug.
- ▌ Design Ship 2 · yonatangrossTurns a claude.ai/design link into a PR: design-import, then cover, then expect, then open the PR. Use when a design should come back as a PR. For files on disk only, use design-import.
- ▌ Prd To Goal 2 · yonatangross bundleTurns a PRD, issue or spec into one copy-paste /goal line of AND-joined boolean checks. Use when running /goal against a spec.
- ▌ Release Sync 2 · yonatangrossAfter a version tag, syncs CHANGELOG and release notes to NotebookLM and the knowledge base, optionally a podcast. Use after tagging a release.
- ▌ Design Import 2 · yonatangrossScaffolds React components from a Claude Design bundle and stops at files on disk. Use when handed a claude.ai/design URL or bundle. For a full PR with tests and browser checks, use design-ship.
- ▌ Error Analysis · yonatangross bundleClusters real LLM traces (Langfuse or JSONL) into a confirmed failure taxonomy with counts, then proposes pass/fail evals. Use to learn what to measure before writing evals. Not for CI failures.
- ▌ Explore 2 · yonatangross bundleMulti-angle codebase exploration by parallel agents: structure, data flow, architecture, health. Use to map an unfamiliar repo. NOT for task research files (use create-research).
- ▌ Create Research · yonatangross bundleDocuments how code works today for a task's questions, with file:line citations. Use before planning a change; describes, never proposes. NOT for mapping a repo (use explore).
- ▌ CI Debug 2 · yonatangrossDiagnoses one failing CI run or PR check against an 11-pattern playbook and proposes the exact fix, never applying it unasked. Use when a GitHub Actions job failed. Not for sweeping all red PRs (use ci-sentinel) or app test failures.
- ▌ Remember 2 · yonatangross bundleWrite-side memory: stores decisions, patterns and outcomes in the knowledge graph. Use when something worth keeping was learned or decided. To search use memory; to consolidate use dream.
- ▌ Iterate Research · yonatangross bundleRe-checks a create-research file when a claim is challenged or the question widens, citing file:line afresh. Use after review comments on research.
- ▌ Create Pr 2 · yonatangross bundleOpens a GitHub PR after pre-flight checks (tests, lint, types, security) with a conventional title and summary. Use only when asked for this skill; an everyday gh pr create stays plain tooling.
- ▌ Fix Issue 2 · yonatangross bundleFixes a GitHub issue: parallel root-cause analysis, a fix with tests, a PR linked back to the issue, and prevention notes. Use when fixing a bug, regression or reported issue.
- ▌ Assess 2 · yonatangross bundleRates code, designs or approaches 0-10 across quality dimensions with pros, cons and fixes. Use when evaluating or comparing options. Not for fixing or building (use implement or fix-issue), PR review (use review-pr) or running tests (use verify).
- ▌ Commit 2 · yonatangross bundleCreates Conventional Commits with scope detection, co-author lines and hook compliance; blocks secrets and generated-only files. Use when asked to commit, save progress or write a commit message, not for incidental commits.
- ▌ Doctor 2 · yonatangross bundleDiagnoses OrchestKit and project health: manifests, hooks, skills, agents, MCP servers, CC version and permissions, with severity and remedies. Use to run doctor checks, diagnose issues or check project health before a release.
- ▌ Expect 2 · yonatangross bundleDiff-aware browser testing: maps the git diff to affected pages, plans and runs targeted checks via agent-browser. Use when testing UI changes before merge. Not for writing tests (use cover), grading a suite (use verify) or unit tests.
- ▌ Memory 2 · yonatangross bundleRead-side memory: search past decisions, load context, timelines and graph views. Use when finding what memory holds. To store use remember; to clean up use dream.
- ▌ Verify 2 · yonatangross bundleGrades work for merge: runs unit, integration and E2E suites plus security and type checks, scores 0-10 with a VERIFIED vs CLAIMED manifest. Use when deciding if work can ship. Not for adding missing tests (use cover).
- ▌ Freeze · yonatangross bundleConfines file edits to one directory until lifted: an Edit, Write, MultiEdit and NotebookEdit hook refuses any path whose real location, symlinks followed, falls outside the frozen dir. Argument: the dir, or off. Use when a change must stay inside one package, module or worktree.
- ▌ Careful · yonatangross bundleBlocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kubectl delete and terraform or tofu destroy, including inside ssh remote commands, and makes Claude ask the operator. Use before touching production, a shared branch, a live database or a cluster.
- ▌ Create Plan · yonatangross bundleWrites an implementation plan file (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, file changes and runnable success criteria. Use when research is done and a reviewable plan is needed before code.
- ▌ Auto 2 · yonatangross bundleDefault front door for goal-shaped requests: classifies a plain-English goal and routes it to the right skill. Use for do this, figure out, I want, help me, fix, build, improve. Not for browsing skills (use help).
- ▌ Help 2 · yonatangross bundleOrchestKit skill directory by category. Use when looking for the right skill or workflow.
- ▌ Iterate Plan · yonatangross bundleRevises a create-plan file from its review comments or new instructions, keeping comments and bumping the revision. Use when a plan got feedback; never to start one.
- ▌ Prompt Focus · yonatangross bundleShows where your attention went from your own Claude Code and Codex prompts over 20 weeks, as a local counts-only report. Use when asking where your focus goes.
- ▌ Cover 2 · yonatangross bundleWrites tests that do not exist yet across unit, integration and end-to-end tiers, healing failures up to 3 times. Use when code lacks tests. Not for grading existing tests (use verify) or running a suite.
- ▌ Dream 2 · yonatangross bundleNightly memory consolidation: prunes stale entries, merges duplicates, resolves contradictions, rebuilds MEMORY.md. Use when memory needs cleanup. To store use remember; to search use memory.
- ▌ Setup 2 · yonatangross bundleOnboarding wizard: scans the codebase and stack, recommends skills and MCP servers, scores readiness. Use when setting up OrchestKit in a project or rescanning after big changes.
- ▌
- ▌ Devops Deployment 2 · yonatangross bundleCI/CD pipelines, containerization, Kubernetes, and infrastructure as code patterns
- ▌
- ▌ Ork Assess 2 · yonatangross bundleAssess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution.
- ▌ Ork Verify 2 · yonatangross bundleVerify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.
- ▌ Ork Explore 2 · yonatangross bundleMap an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
- ▌ Ork Implement 2 · yonatangross bundleMake an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.
- ▌ Ork Review Pr 2 · yonatangross bundleReview a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
- ▌ Ork Brainstorm 2 · yonatangross bundleCompare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
- ▌
- ▌ Ork Assess · yonatangross bundleAssess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution.
- ▌ Ork Verify · yonatangross bundleVerify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.
- ▌ Ork Explore · yonatangross bundleMap an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
- ▌ Ork Implement · yonatangross bundleMake an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.
- ▌ Ork Review Pr · yonatangross bundleReview a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
- ▌ Ork Brainstorm · yonatangross bundleCompare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
- ▌ Yonyon · yonatangrossQuery the public yonyon.ai agent API from the command line or over MCP. Use when a user asks about Yonatan Gross, his work, projects, services, availability or fit; when they want the portfolio project list; when they want to book an intro call; or when they want the yonyon.ai MCP server wired into a client. No authentication and no configuration are required.
- ▌ Etf Analyzer · yonatangross bundleAnalyze ETFs — holdings composition, sector and geographic exposure, expense ratio, and index-tracking error. Use when the user asks about an ETF ticker (SPY, QQQ, VTI, etc.), wants to compare two ETFs, check overlap between funds, or understand what an ETF holds and costs. Provides top-holdings breakdown, overlap percentage, cost comparison, and tracking-error context. Do NOT use for individual-stock analysis (use global-stock-analysis) or Israeli mutual funds.
- ▌ Global Stock Analysis · yonatangross bundleAnalyze US and global stocks (NASDAQ, NYSE, S&P 500 constituents) with technical, fundamental, and sentiment signals. Use when the user asks about international stocks, tickers like AAPL/NVDA/MSFT, S&P 500 or NASDAQ names, or wants RSI/MACD/moving-average or valuation analysis on a non-Israeli symbol. Provides indicator computation (RSI, MACD, Bollinger Bands, EMA 20/50/200, CCI), fundamental ratios, and a structured buy/hold/sell rationale. Do NOT use for Israeli TASE stocks (use tase-stock-analysis) or cryptocurrency.
- ▌ Sp500 Nasdaq Screener · yonatangross bundleScreen the S&P 500 and NASDAQ-100 universe by technical and fundamental criteria to surface candidate stocks. Use when the user wants to filter or rank US stocks — 'S&P 500 names with RSI below 30', 'NASDAQ stocks above their 200-day average', oversold/overbought scans, or sector-relative screens. Returns a ranked table with the matched criteria per symbol. Do NOT use for single-symbol deep analysis (use global-stock-analysis) or Israeli TASE screening.
- ▌ Post Call · yonatangross bundleTurn one client call into a reviewed document with the call facts, a short recap message and a one-page scope, drafted in the client's language (Hebrew by default). Use right after a call when a text transcript exists (a file, or a Wispr Flow meeting through its MCP) and you want the follow-up written before you forget it. NOT for preparing a call (prep-call), for a status board (client-context), or for recording the outcome in the client's state log (sync-call-state). Model-invocable, so fire it yourself when the goal matches; drafts only, nothing is sent; state what you are about to do and get the operator's confirmation before the mutating step; never fire it as a background checkpoint.
- ▌ Prep Call · yonatangross bundleBuild a one-page cheatsheet for the next call with a client from what the client folder already holds. Who they are, where things stand, the open threads, two to four goals for the call, the questions to ask, what to say when they push on price, timing or scope, and the one next step to propose, in the client's language and register (Hebrew by default). Use right before a scheduled call, once clients/NAME/ exists, whether it is the first call or the fifth. NOT for drafting the recap and scope after a call (post-call), for a status board when no call is ahead (client-context), or for writing an outcome into the state log (sync-call-state). Reads local files, an optional CRM export and Wispr Flow meeting titles; writes one new file and never overwrites. Model-invocable, so fire it yourself when the goal matches; do not fire it speculatively or as a checkpoint.
- ▌ Client Context · yonatangross bundleRender a fixed status board for one client from the files in clients/NAME/ (profile, state log, post-call docs, cheatsheets, outreach, notes), the client's row in an optional CRM export, and Wispr Flow meeting titles when that MCP server is connected. The board shows stage, last contact with staleness, direction agreed, open threads, next steps and the sources consulted. Use as the opening read before touching a known client, or to answer where you stand with them. A disagreement between sources is flagged with both values, never resolved. NOT for a pre-call cheatsheet (prep-call), for drafting a recap and scope after a call (post-call), or for changing the stage or the state log (sync-call-state). Read-only, nothing is written. Model-invocable, so fire it yourself when the goal matches; do not fire it speculatively or as a checkpoint.
- ▌ Sync Call State · yonatangross bundleRecord the outcome of a reviewed post-call document in the client's local state, from one confirmation and a visible diff. Computes one new entry for clients/NAME/state.md and, when the call carried a stage signal, a change to the single stage line in profile.md; shows both as a diff, asks Apply / Edit / Cancel, and writes only on Apply. Use after you reviewed the post-call doc and want the client's log and stage to say what was agreed. NOT for drafting the recap or the scope (post-call), for a status board (client-context), or for preparing the next call (prep-call). Model-invocable, so fire it yourself when the goal matches; state what you are about to do and get the operator's confirmation before the mutating step; never fire it as a background checkpoint.
- ▌ Webapp Testing · yonatangross bundlePlaywright testing with autonomous test agents (planner, generator, healer) and visual regression testing
- ▌ Pgvector Search · yonatangross bundleProduction hybrid search with PGVector 0.7+ and BM25 using Reciprocal Rank Fusion, metadata filtering, and HNSW indexing for semantic retrieval
- ▌ Ascii Visualizer · yonatangross bundleCreate beautiful ASCII art visualizations for plans, architectures, workflows, and data
- ▌
- ▌ AI Native Development · yonatangross bundleBuild AI-first applications with RAG pipelines, embeddings, vector databases, agentic workflows, and LLM integration. Master prompt engineering, function calling, streaming responses, and cost optimization for 2025+ AI development. Includes local LLM inference with Ollama for 93% CI cost reduction.
- ▌ Streaming API Patterns · yonatangross bundleImplement real-time data streaming with Server-Sent Events (SSE), WebSockets, and ReadableStream APIs. Master backpressure handling, reconnection strategies, and LLM streaming for 2025+ real-time applications.
- ▌ Golden Dataset Curation · yonatangross bundleQuality criteria, workflows, and multi-agent analysis patterns for curating high-quality golden dataset entries
- ▌ Database Schema Designer · yonatangross bundleUse this skill when designing database schemas for relational (SQL) or document (NoSQL) databases. Provides normalization guidelines, indexing strategies, migration patterns, and performance optimization techniques. Ensures scalable, maintainable, and performant data models.
- ▌ Performance Optimization · yonatangross bundleFull-stack performance analysis, optimization patterns, monitoring strategies, React 19 concurrent features, and bundle analysis for 2025+ development
- ▌ Golden Dataset Management · yonatangross bundleBackup, restore, and validate golden datasets for AI/ML systems - ensuring test data integrity and preventing catastrophic data loss
- ▌ Golden Dataset Validation · yonatangross bundleValidation rules, schema checks, duplicate detection, and coverage analysis for golden dataset integrity
- ▌ Figma Design Handoff · yonatangross bundleFigma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev workflows, or comparing production UI against Figma designs.
- ▌ Interaction Patterns · yonatangross bundleUI interaction design patterns for skeleton loading, infinite scroll with accessibility, progressive disclosure, modal/drawer/inline selection, drag-and-drop with keyboard alternatives, tab overflow handling, and toast notification positioning. Use when implementing loading states, content pagination, disclosure patterns, overlay components, reorderable lists, or notification systems.
- ▌ Multi Surface Render · yonatangross bundleMulti-surface rendering with json-render — one JSON spec produces React web, Next.js, React Native, Ink terminal UIs, PDFs, emails, Remotion videos, OG images, and 3D scenes. Covers renderer target selection, registry mapping, and platform APIs (renderToBuffer, renderToStream, renderToFile). Use when generating output for several platforms or creating PDF reports, email templates, demo videos, or social images from one component spec.
- ▌ Architecture Patterns · yonatangross bundleArchitecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.
- ▌ Web Research Workflow · yonatangross bundleUnified decision tree for web research and competitive monitoring. Auto-selects WebFetch, Tavily, or agent-browser based on target site characteristics and available API keys. Includes competitor page tracking, snapshot diffing, and change alerting. Use when researching web content, scraping, extracting raw markdown, capturing documentation, or monitoring competitor changes.
- ▌ Design Context Extract · yonatangross bundleExtract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design, analyze animations or scroll behavior, or keep new pages matching an established visual identity.
- ▌ Documentation Patterns · yonatangross bundleTechnical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
- ▌ Animation Motion Design · yonatangross bundleAnimation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
- ▌ Issue Progress Tracking · yonatangross bundleGitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or completing work with a PR.
- ▌ Monitoring Observability · yonatangross bundleMonitoring and observability patterns for Prometheus metrics, Grafana dashboards, Langfuse v4 LLM tracing (as_type, score_current_span, should_export_span, LangfuseMedia), and drift detection. Use when adding logging, metrics, distributed tracing, LLM cost tracking, or quality drift monitoring.
- ▌ Task Dependency Patterns · yonatangross bundleTask Management patterns with TaskCreate, TaskUpdate, TaskGet, TaskList tools. Decompose complex work into trackable tasks with dependency chains. Use when managing multi-step implementations, coordinating parallel work, or tracking completion status.
- ▌ Storybook MCP Integration · yonatangross bundleReference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a mockup into a new component and consumes these tools as one stage, use design-to-code.
- ▌ Architecture Decision Record · yonatangross bundleADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
- ▌ Scope Appropriate Architecture · yonatangross bundleRight-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.
- ▌ React Server Components Framework · yonatangross bundleUse when building Next.js 16+ apps with React Server Components. Covers App Router, Cache Components (replacing experimental_ppr), streaming SSR, Server Actions, and React 19 patterns for server-first architecture.
- ▌ Dev · yonatangross bundleOne-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install hints when prerequisite binaries are missing.
- ▌ Auto · yonatangross bundleIntent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another skill (no recursion). Triggers on: auto, do this, figure out, just make, I want, help me, fix, build, improve, any goal description.
- ▌ Help · yonatangross bundleOrchestKit help directory with categorized skill listings. Use when discovering skills for a task, finding the right workflow, or browsing capabilities.
- ▌ Cover · yonatangross bundleGenerate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after implementation. Do NOT use to grade tests that already exist (use /ork:verify) or to run a suite without writing anything new.
- ▌ Dream · yonatangross bundleNightly memory consolidation — prunes stale entries, merges duplicates, resolves contradictions, rebuilds MEMORY.md index. Use when memory files have accumulated over many sessions and need cleanup. Do NOT use for storing new decisions (use remember) or searching memory (use memory).
- ▌ Glyph · yonatangross bundleRender an answer as ASCII art plus semantic emojis inline, right now, with no setup questions. Use for a fast visual take on status, comparisons, trade-offs, architecture, or any ad-hoc 'show me X visually' ask. For a full multi-artifact plan playground, use visualize-plan instead.
- ▌ Setup · yonatangross bundlePersonalized 7-phase onboarding wizard that scans the codebase, detects tech stack, recommends skills and MCP servers, and generates an improvement plan with readiness score. Includes safety checks and project-scoped configuration. Use when setting up OrchestKit for a new project or rescanning after major changes.
- ▌ Assess · yonatangross bundleAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.