Loading...
Loading...
Found 3,443 Skills
This skill should be used when the user asks to "create Dataverse tables", "set up the data model", "setup dataverse", "create tables for my site", "setup dataverse schema", "create the database", "build my data model", or wants to create Dataverse tables, columns, and relationships for their Power Pages site based on a data model proposal.
oh-my-agent project setup verification and configuration
Single entry point for one-shot, end-to-end DatoCMS project setup orchestration — the only skill that bundles prerequisites, chains related recipes, and takes a greenfield or partially configured project to a working state in one pass. Covers five setup lanes: (1) frontend foundation (bootstrap a new Next.js/Nuxt/SvelteKit/Astro integration from scratch); (2) frontend features (draft mode, visual editing, web previews, content link, real-time updates, responsive images, SEO, robots/sitemaps, site search, revalidation/cache tags — applied together with their prerequisites); (3) migrations (CLI profiles, baseline migrations, shared histories, release workflow, sandbox reset loops, diff-based generation); (4) onboarding imports (WordPress, Contentful — content plus assets); (5) platform automation (CMA scripting patterns and project-level automation). Use when the user wants a named outcome scaffolded in full rather than a single file patched, when multiple related features need to land together (e.g. "set up visual editing" implies draft mode + content link + web previews), or when the request is a broad "set up X" that needs routing to the smallest matching recipe bundle.
Bootstrap a nao agent for a project — gather warehouse + scope + extra-context info in one round, look up the warehouse-specific config from nao docs, write nao_config.yaml, run nao init + nao sync, set up the LLM key, and generate the first RULES.md. Use when the user has just decided to use nao on a new project. Only for first-time setup; for editing rules, generating tests, or reviewing an existing context, use write-context-rules / create-context-tests / audit-context.
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Print a summary of the Cyrus setup and offer to start the agent.
Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Adopt the Memory Kit in THIS repository — scaffold the memory layers, decide how the kit coexists with Claude Code's native auto memory, and install safe permission rails. Use when the user says "/memory-kit:setup", "set up the memory kit", "adopt the kit here", "настрой кит", or when a session starts in a repo where the kit plugin is installed but no .claude/memory/MEMORY.md exists.
Set up the Better TypeScript linter in Node.js/npm or Bun TypeScript projects, including single-package repositories and monorepos. Use when asked to add, install, configure, or create a lint script for @better-typescript/better-typescript.
Set up or refresh UX Skills for a new or existing project by capturing product intent, learning users and evidence, the design system, engineering environment, accessibility expectations, terminology, and consequential decisions. Use only when the user explicitly asks to set up, initialize, connect, learn, or refresh UX Skills/project context; do not activate during ordinary UX work.
Use when bootstrapping a new Rust monorepo workspace from commit 1 — when the project has more than one binary crate (e.g. an API server and a background worker), when shared types must be consumed by two or more members without duplicating code, or when a single-crate layout would force one binary to carry another's compile-time dependencies. Triggers — a team wants shared wire contracts between a backend service and a worker process; a shared infrastructure primitive crate must stay independent of both consumers; the Cargo.toml at the repository root has no `[workspace]` section yet. Not applicable for single-crate projects (see rust-project-setup).