Loading...
Loading...
Found 11 Skills
Use when starting Auth0 integration in any framework - detects your stack (React, Next.js, Vue, Angular, Express, React Native) and routes to correct SDK setup workflow
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and give me the link', or 'Push this live'. No authentication required - returns preview URL and claimable deployment link.
Detect Chrome extension framework/stack, find proper docs, implement features, and debug across service worker, content script, and popup contexts.
Automated brownfield codebase analysis. Detects project type, frameworks, dependencies, architecture patterns, and generates comprehensive project profile. Essential for Conductor integration and onboarding existing projects.
Integrate CometChat into any app. Auto-detects your platform and framework, then walks you through picking and applying a chat experience. Start here — do not invoke platform-specific skills directly. Trigger with "/cometchat", "integrate cometchat", or "add chat to my app".
Explain how CE.SDK Web features work — concepts, architecture, and workflows. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user says "explain", "how does X work", "walk me through", "what is", "describe", or wants to understand a CE.SDK concept at a conceptual level for Web development. Generates custom markdown explanations with diagrams and code examples. Not for looking up existing docs (use docs-{framework}), not for writing implementation code (use build). <example> Context: User wants to understand how text layers work user: "Explain how text layers work in CE.SDK" assistant: "I'll use /cesdk:explain to generate a detailed explanation." </example> <example> Context: User needs a concept explained in their context user: "How does the block hierarchy work for video editing?" assistant: "Let me use /cesdk:explain to create a custom explanation for video block hierarchy." </example> <example> Context: User needs to understand a workflow user: "Walk me through the asset loading pipeline" assistant: "I'll use /cesdk:explain to explain the asset pipeline." </example>
Architectural reference for WorkOS AuthKit integrations. Fetch README first for implementation details.
Deploy applications to Vercel with automatic framework detection
Inspect an existing repo and generate OpenEditor onboarding config for it. Use when Codex needs to make a project OpenEditor-compatible by inferring framework or platform from the file tree, creating or updating `.logic-editor.json`, creating `oe-swift.json` for iOS or SwiftUI projects, or explaining which config fields still need manual confirmation.
[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.