AI & ML

eroslifestyle Bundle

Multi-agent orchestrator that delegates all work to specialized subagents. Enforces parallelism, tracks progress, and coordinates agent teams for complex tasks.

eroslifestyle Skill

Display detailed session metrics and agent performance. Use /metrics for the full dashboard.

tony363 Skill

Comprehensive MCP orchestration skill integrating PAL MCP (reasoning, consensus, debugging) and Rube MCP (500+ app automations). Central hub for all MCP-powered workflows.

aspiers Bundle

Find Linear issues ready for an AI agent to pick up. Equivalent of `bd ready` for Linear workflows. Use when starting a session to find claimable work, or when asked "what's next" or "find work".

aspiers Skill

General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.

aspiers Skill

Decompose an approved implementation plan into self-contained Linear issues with zero guesswork. Use when breaking down a plan into actionable Linear tasks via the MCP server.

aspiers Skill

Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.

aspiers Skill

Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.

aspiers Skill

Turns an existing Product Requirements Prompt at .ai/[feature]/prp.md into a step-by-step task list of parent tasks and sub-tasks, saved to .ai/[feature]/tasks.md and committed. Use when a PRP is ready to be broken down into implementable work, or when planning how a feature will be built before any implementation starts. To write the PRP itself first, use prp- generation.

eroslifestyle Skill

Create a multi-agent execution plan for complex tasks. Use /multi-plan for parallel agent coordination planning.

eroslifestyle Skill

Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability. Use for pre-processing user requests, expanding vague prompts, and optimizing for orchestrator execution.

lucasilverentand Bundle

Use when the user asks to create, update, review, or refactor an agent skill, including requests like "turn this workflow into a skill", "make a skill for this", "fix this SKILL.md", "add references to this skill", "make this skill work in Codex and Claude", or "split this bloated skill". Creates skill directories, writes portable SKILL.md frontmatter and workflows, adds references, validates structure and token budgets. For adding executable helpers, use the tooling skill.

lucasilverentand Bundle

Designs REST, GraphQL, or gRPC APIs from requirements — picks the right protocol for the use case, models resources and operations, defines schemas (Zod for internal, OpenAPI/GraphQL SDL/proto for specs), and writes the spec to .context/architecture/api/. Use when the user asks to design an API, sketch out endpoints, model a schema, plan a service's interface, or says things like "what should the API look like for X", "design endpoints for Y", or "how should clients talk to this service".

lucasilverentand Bundle

Designs the data layer — schemas, entities, relationships, ID strategy, naming, tenancy, timestamps, indexes, audit logging, and migrations. Turns a set of domain concepts into a concrete Drizzle schema with all the small decisions that compound into either a clean data layer or a mess. Use when the user asks to design a schema, model the data, plan the database, add tables, review an existing schema, or says things like "what should the database look like", "design the schema for X", "add a table for Y", or "how should I store Z". Does NOT cover system decomposition (use architecture) or API design (use api-design).

lucasilverentand Bundle

Mines recent Codex or Claude agent conversations and git history for struggles, repeated corrections, rework patterns, and taste signals — then turns findings into new skills or updates to existing ones. Use when retrospecting on recent coding sessions, extracting learnings, identifying skill gaps, improving skills from real usage patterns, codifying recurring preferences, or when the user says "retro this repo", "mine recent conversations", "what should become a skill", or "find repeated agent mistakes".

aspiers Bundle

Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.

aspiers Skill

Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.

aspiers Bundle

Review every Beads issue waiting on a person, one at a time, using the interactive questionnaire UI rather than plain-text prompts. Use when asked to go through blockers, clear the human queue, answer beads waiting on the user, triage `bd human list`, or unblock agent work that needs a decision.

aspiers Skill

Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.

aspiers Bundle

Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).

tony363 Skill

Deep research on any topic combining real-time web search (Rube MCP) with multi-model consensus analysis (PAL MCP). Produces structured reports with sourced findings and confidence assessments.

tony363 Bundle

Feature implementation with intelligent persona activation, task orchestration, and MCP integration. Use when implementing features, APIs, components, services, or coordinating multi-agent development. Triggers on requests for code implementation, feature development, or complex task orchestration.

tony363 Bundle

Interactive multi-model consensus code review using PAL MCP. Reviews commits, staged changes, or branch diffs with user-directed scope and interactive decision points.

lucasilverentand Bundle

Facilitates structured project-intent interviews and A/B/C option narrowing before planning work. Use when the user asks to refine an app, product, repo, automation, or project idea, feels lost across many projects, wants Codex to interview them, wants A/B/C choices, needs an LLM alignment packet, wants to decide whether to build, pause, merge, or kill a project, or wants to prepare a Linear planning project before creating docs, issues, or implementation work.

lucasilverentand Skill

Guides a full system design from idea to spec — sequences requirements gathering, architecture decomposition, data modeling, API design, and document writing into a coherent workflow with clear handoffs. Use when the user asks to "design a system", "build X from scratch", "architect something end-to-end", "plan a new service", or has a broad design ask that spans multiple concerns. Also use when the user says things like "I need to build X" without specifying which aspect to start with. This is the entry point for any design task that isn't clearly scoped to a single skill (data model only, API only, etc.).

lucasilverentand Bundle

Generates and maintains a hierarchical .context/ directory with architecture overviews, coding conventions, domain glossaries, and dependency maps that give any LLM working in the project the right background. Use when setting up a new project for AI-assisted development, when the user asks to create or update context docs, when onboarding a new LLM tool to an existing codebase, or when the user says the AI doesn't understand their project.

camoa Bundle

Use when testing code, skills, commands, or configs through mental execution — trace logic line-by-line with concrete values to find bugs, logic errors, edge cases, contract violations, and AI hallucinations. Use when user says "paper test", "trace this", "find bugs", "check for edge cases", "audit this code", "verify AI code", "test this skill", "test this agent", "validate this implementation", "review this logic", "check dependencies", "check this config", "walk through this code", "step through this", "dry run", "sanity check", "red team this", "poke holes in this". MUST verify external calls — never assume methods exist. Use proactively before deploying changes or after AI generates code.

camoa Skill

Use when a phase command (research/design/implement) needs to load methodology references, online dev-guides, and project playbooks before task work begins. **v4.10.0+: hybrid detection** — a deterministic phase-aware methodology floor + lexical catalog candidates via scripts/dev-guides-detect.sh, plus semantic matches from the guides-matcher agent. Delegates guide fetching to dev-guides-navigator. Loads playbook layers via scripts/playbook-load-deterministic.sh. Cross-references conflicts. Records loaded guide IDs into session_context.json loadedGuides[] to prevent re-loads.

priivacy-ai Skill

Start here for Spec Kitty. Orient CLI users and supported agent-harness users; choose the right command, skill family, and recovery path.

aspiers Skill

Create Claude Code slash commands, OpenCode command files, and Pi prompt templates that delegate to the right subagent or skill. Use when creating new commands or refactoring existing ones to follow platform conventions.

matrixfounder Skill

Guidelines for fast-tracking trivial tasks (typos, UI tweaks, simple bugfixes).

matrixfounder Bundle

Use when high-assurance reliability is required (Bug fixes, Critical Features, Quality Hardening).

nintendadev Bundle

Create an implementation plan for a feature — a dependency-ordered, actionable task list for the project. Has four modes: fast (a quick single-pass plan), full (a richer plan that can also create a git branch), ultra (a multi-file bundle — a manifest plus one deeply specified file per phase — for execution by a smaller model), and add (extend an existing plan with more tasks). Pick the mode from the user's wording: "full plan" runs full; "quick plan" or "fast plan" runs fast; "ultra plan", "ultraplan" or "ultra-plan" runs ultra; a plain "create a plan" with no qualifier defaults to fast; "add to the plan" or "extend the plan" runs add. Use whenever the user wants to plan a feature or task, e.g. "create a plan", "create a full plan", "create a quick plan", "run an ultra plan for the inventory system", "plan this feature", "add this to the plan", "extend the plan", "add a phase to the plan". Ultra runs only when the user names it — never because the feature looks large.

nintendadev Skill

Add a short, project-specific rule, convention, or override to .unikit/RULES.md — the quick-capture inbox for this project's rules; each invocation appends a rule, automatically loaded by /unikit-implement before execution (later promotable into the knowledge base via /unikit-memory migrate-rules). Works only with a rule typed as a prompt — it does NOT read files, folders, URLs, or PDFs. Cross-checks against the knowledge base (RULES_INDEX.md) to avoid duplicating core/stack entries. Use for fast, one-line conventions and corrections: "add a rule", "remember this", "convention", "always do X", "never use Y", "from now on do Z", or when the user corrects agent behavior and wants it remembered. If the user points to a source (file, folder, URL, PDF, article, book) or wants to research/document framework usage, use /unikit-memory; for architecture decisions use ARCHITECTURE.md.

nintendadev Bundle

Curate the project's knowledge base and memory in .unikit/memory/ — the indexed reference library of coding standards and framework usage patterns. ALWAYS use this skill whenever the user adds knowledge from a source: a URL, a file, a folder path, a PDF, an article, or a book — any path/link/document is a strong signal for the knowledge base, not a quick rule. Also use it to research or document how the project uses a framework, or to add a researched core/stack knowledge entry. Sub-commands by phrasing: "migrate the rules" or "promote rules" runs migrate-rules; "optimize the knowledge base" or "optimize the rules" runs optimise (extract large sections into references); "validate" re-syncs RULES_INDEX.md; "--module <id>" targets a module. For a quick one-line convention or correction typed as a prompt ("always do X", "never use Y", "remember this") with no source, use /unikit-rules; for architecture decisions use ARCHITECTURE.md.

camoa Skill

Use when an orchestrator must build exactly ONE contract-conformant work-order in clean context — gates it through wo-compile.sh assert-dispatchable (fail-closed; never spawn on a non-zero gate), checkpoints the shared code worktree, spawns one fresh standard Task-tool subagent whose prompt is the self-contained work-order body, treats the collected transcript as untrusted data, commits the worktree only if it shows changes, and returns the disk-derived collect-handle JSON. A per-work-order atom: no loop, no verdict, no /review; read-only on the work-order BODY, and its ONLY status write is the `ready→in_progress` flip (after its re-gate, before it commits — the crash-safety hinge). Invoked per-WO by the lifecycle_controls loop; runs in the orchestrator's main context (its single Task spawn is the one supported depth-1 level).