Loading...
Loading...
Found 8,755 Skills
Choose before `admin` when the user needs **Shopify CLI** to run or fix something now: validate app or extension config on disk (`shopify.app.toml`, `shopify.app.<name>.toml`, `shopify.extension.toml`) with **`shopify app config validate --json`** (not Admin GraphQL; MCP has no TOML validator); run or troubleshoot store workflows (`shopify store auth`, `shopify store execute`); inventory or product changes by handle, SKU, or location name; or CLI setup, auth, upgrade issues. Emphasize **commands and operational steps**, not only authoring GraphQL. Skip for API-only understanding or codegen with no CLI execution. Examples: validate before deploy; run an existing query via CLI; list products; missing `shopify store execute`.
Phase 3 of the issue workflow —— Fix code precisely according to confirmed root causes and solutions, verify the results, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow —— no verification closure means the workflow is incomplete. Two entry points: the standard path is triggered from cs-issue-analyze (with existing {slug}-analysis.md), and the fast track is triggered directly from cs-issue-report (without {slug}-analysis.md, as the root cause was identified by AI through code reading during the report phase). Trigger scenarios: User says "Start fixing the bug", "Fix according to the analysis", "Start modifying the code". During the fix, only modify the files specified in the solution; do not make incidental optimizations or introduce new abstractions —— these actions will cause the scope to expand to an untraceable extent.
Build, debug, or plan work with The Prompting Company through its API, MCP Server, CLI, or SDK entrypoints. Use when the user needs public routes, OpenAPI schema guidance, TypeScript SDK integration, CLI workflows, MCP setup, content APIs, app publishing APIs, public markdown access, simulations, visibility analytics, authentication, or API key scopes.
Orchestrate the public UGC creative production line from product or research evidence through creator logic, storyboard, image/video/audio generation handoffs, montage planning, and QA. Use this when the user asks for a repeatable UGC-style ad or creator video workflow rather than one isolated media asset.
Use when running video data augmentation and auto-labeling workflows on OSMO: flow selection, preflight, submit-time interpolation, monitoring, and output retrieval. Trigger keywords: video data augmentation, data enrichment, auto labeling, VDA demo, OSMO workflow, pseudo labeling.
Edit and design the materials provided by users (webpage URLs / PDFs / DOCX files / Markdown / plain text / screenshots / pasted content) into a beautiful, offline-accessible and shareable **single-file HTML web article**. Based on the reacticle component protocol: instead of writing raw HTML/CSS manually, use semantic components + theme-constrained Raw free layers; follow the small harness workflow of source → planning → double confirmation → generation → final review → repair, and produce long articles with 100% information retention by default. Trigger scenarios: convert URLs/PDFs/DOCX files/articles into web articles / long-form articles / briefings / explanatory articles / visual articles / tutorials / review and retrospectives / program analyses, with triggers like 'render this as a beautiful web article / turn this into a web article / generate a shareable HTML long-form article / reacticle article'. Only generate articles, not backends, forms, dashboards, product prototypes or general web apps.
Use when authoring TypeScript libraries - covers project setup, package exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and release workflows. Patterns extracted from 20+ high-quality ecosystem libraries.
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
Build Python APIs on Cloudflare Workers using pywrangler CLI and WorkerEntrypoint class pattern. Includes Python Workflows for multi-step DAG automation. Prevents 11 documented errors. Use when: building Python serverless APIs, migrating Python to edge, or troubleshooting async errors, package compatibility, handler pattern mistakes, RPC communication issues.
Primary Python tool for 40+ bioinformatics services. Preferred for multi-database workflows: UniProt, KEGG, ChEMBL, PubChem, Reactome, QuickGO. Unified API for queries, ID mapping, pathway analysis. For direct REST control, use individual database skills (uniprot-database, kegg-database).
AI-agent readiness auditing for project documentation and workflows. Evaluates whether future Claude Code sessions can understand docs, execute workflows literally, and resume work effectively. Use when onboarding AI agents to a project or ensuring context continuity. Includes three specialized agents: context-auditor (AI-readability), workflow-validator (process executability), handoff-checker (session continuity). Use PROACTIVELY before handing off projects to other AI sessions or team members.
Migration-first database development workflow using Drizzle ORM for TypeScript/J...