faion-ml-ops
ML operations: fine-tuning (LoRA, QLoRA), model evaluation, cost optimization, observability.
faion-ml-engineer
ML/AI orchestrator: LLM integration, RAG, ML Ops, agents, multimodal.
faion-marketing-manager
Marketing orchestrator: GTM, content, growth, conversion optimization.
faion-market-researcher
Market research: TAM/SAM/SOM sizing, competitor analysis, pricing research, trend analysis.
faion-llm-integration
LLM APIs: OpenAI, Claude, Gemini, local LLMs, prompt engineering, function calling.
faion-javascript-developer
JavaScript/TypeScript: React, Node.js, Next.js, modern JS patterns.
faion-infrastructure-engineer
Infrastructure: Docker, Kubernetes, Terraform, AWS/GCP, IaC, containerization.
faion-improver
Session-based continuous improvement: investigate system, find gaps, brainstorm, apply fixes, log improvements, commit, create skills from experience. 5 methodologies.
faion-accessibility-specialist
Accessibility: WCAG compliance, assistive technologies, inclusive design.
faion-ppc-manager
PPC advertising: Google, Meta campaigns, optimization, reporting.
faion-pm-traditional
Traditional PM specialist: PMBoK knowledge areas (scope, schedule, cost, risk, quality, stakeholder, resources), EVM, WBS, project lifecycle, PMBoK 7/8 framework. 22 methodologies.
faion-communicator
Communication: stakeholder dialogue, Mom Test, conflict resolution, feedback, storytelling.
faion-gtm-strategist
GTM strategy: product launches, positioning, pricing, partnerships, customer success.
faion-hr-recruiter
HR recruiting: talent acquisition, employer branding, interviews, onboarding, DEI.
faion-ai-agents
AI agents: autonomous agents, multi-agent systems, LangChain, LlamaIndex, MCP.
faion-brainstorm
Multi-agent brainstorming: structured diverge-converge-review cycles for technical and product ideation.
atlassian-cli
Use for installing, upgrading, authenticating, and using Atlassian Command Line Interface (ACLI, `acli`) for Atlassian Cloud. Triggers include Jira CLI tasks (work items, projects, boards, sprints), Atlassian Admin CLI tasks (user/org admin via API key), Rovo Dev CLI usage, enabling shell completion, scripting/CI usage, and troubleshooting `acli` errors or trace IDs.
video-agent-skills
Provide candid, practical feedback on a video file using Gemini. Use when the user wants critique or production feedback on a video.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
prose-gen
>
ui-wip
>
web-animation-design
>
agentation-self-driving
Autonomous design critique mode using the Agentation annotation toolbar. Use when the user asks to "critique this page," "add design annotations," "review the UI," "self-driving mode," "auto-annotate," or wants an AI agent to autonomously add design feedback annotations to a web page via the browser. Requires the Agentation toolbar to be installed on the target page and agent-browser skill to be available.
opensrc
>
notify
>
jira
>
improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
hi
>
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
gitlab-create-merge-request
>
find-skills
>
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
agent-browser
>
agent-browser-aircall-local
>
refactor-agents-markdown
>
ui-skills
>
capture-skill
Capture learnings, patterns, or workflows from the current conversation into a new or existing skill. Use when the user wants to save what was learned, discovered, or built during a conversation as a reusable skill for future sessions. Triggers include "capture this as a skill", "save this for next time", "turn this into a skill", or when a useful workflow, pattern, or piece of domain knowledge emerged during the conversation.
explore-codebase
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-area, very-thorough for architecture audits. Triggers: explore, find files, where is, how does X work.
review
Comprehensive code review orchestrator. Runs multiple focused review analyses (bugs, types, maintainability, simplicity, coverage, docs, AGENTS.md) and consolidates findings. Use before PR or after implementation. Triggers: review, code review, review my changes, PR review.
spec
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, migrations, performance, documentation, or any other work type. Triggers: spec, requirements, define scope, what to build.
web-research
Conduct structured web research with hypothesis tracking. Synthesizes information from multiple sources into actionable findings. Use for technical research, API docs, best practices. Triggers: web research, look up, search for, find documentation.
bugfix
Systematic bug investigation and fix workflow. Gathers symptoms, forms hypotheses, investigates root cause, implements fix, and verifies. Use for debugging, fixing errors, or troubleshooting. Triggers: debug, fix bug, troubleshoot, why is this broken.
sync-from-vibe-workflow
Sync skills from claude-code-plugins vibe-workflow to this codex-workflow repo. Adapts Claude Code features to Codex equivalents. Use when vibe-workflow has updates to sync.
review-type-safety
Audit TypeScript/typed code for type safety issues. Identifies any abuse, missing type guards, and opportunities to make invalid states unrepresentable. Read-only. Triggers: review types, type safety, check types, typescript review.
fix-review-issues
Orchestrate fixing issues found by $review. Handles issue discovery, user confirmation, plan creation, and execution via $implement. Triggers: fix review issues, fix findings, address review feedback.
review-testability
Audit code for testability design patterns. Identifies business logic entangled with IO, hard-coded dependencies, and mocking friction. Suggests functional core / imperative shell separation. Read-only analysis. Triggers: review testability, testable code, mocking issues, dependency injection.
review-simplicity
Audit code for over-engineering, premature optimization, and cognitive complexity. Identifies unnecessary abstractions, YAGNI violations, and overly complex solutions. Read-only analysis. Triggers: review simplicity, over-engineering, complexity check, YAGNI.
review-maintainability
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
Page 1316 of 1592 · 79598 results
