Results for “project create”

Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context documents: add one to any other Project for immediate deep awareness of the source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project," "extract project context," "generate a project summary for another project," "I need to share this project's context," "prepare this project for cross-project reference," or "document this project." Also use when the user is preparing to work across Projects and needs portable context. Do NOT use for session handoffs, project audits, or Memory optimization (use rootnode-session-handoff, rootnode-project-audit, or rootnode-memory-optimization respectively, if available).

The English summary is being prepared. Showing the original description.

Find and identify the CDecoyProjectile_Create factory in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the decoy projectile spawn factory. It is a non-virtual, direct-call static factory found via the entity classname string "decoy_projectile" it references (excluding the RTTI class string "CDecoyProjectile"). Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CDecoyProjectile_Create.py preprocessor (xref_strings FULLMATCH:decoy_projectile). Trigger: CDecoyProjectile_Create, CDecoyProjectile::Create, decoy projectile Create

The English summary is being prepared. Showing the original description.

xUnit test project creation and setup specialized skill. Used when creating test projects, setting up project structure, configuring NuGet packages, and organizing test folders. Covers csproj setup, package management, project structure, xunit.runner.json configuration, etc. Keywords: xunit project, xunit setup, create test project, test project setup, create test project, project structure, project structure, folder structure, xunit package, nuget packages, testing packages, how to create test project, xunit configuration

The English summary is being prepared. Showing the original description.

Create and maintain project documents in conductor/ covering the product, technology stack, development workflow, and work units. Extract context from existing code, check document consistency before implementation, and update documentation as the project evolves.

• Set up context documents for a new project
• Document an existing codebase for onboarding
• Check project documents before implementation

Create one new Muse skill with a self-contained SKILL.md and validate it. Build a project skill in the workspace, or prepare a personal skill draft with the command needed to install it.

• Create a skill for one Muse project
• Prepare a personal skill for multiple projects
• Turn requested procedures into a SKILL.md

Manage users, team workspaces, and projects in KubeSphere through its API. Create accounts and resources, invite members, inspect existing access, and assign or change built-in permission roles with minimum access as the default.

• Create user accounts with limited default access
• Create team workspaces and projects on selected clusters
• Invite members and assign built-in permission roles

Package a finished local web project for GitHub with a tailored README and a preview from the running project. Audit files before pushing, publish compatible projects through GitHub Pages, and verify the repository and live demo.

• Share a local HTML, CSS, or JavaScript experiment
• Prepare a README and a preview from the running project
• Publish a compatible web project on GitHub Pages

Use when you act as Leader and maintain durable TeamHarness project state for Quick Task or Project Work: create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state. Do not use to create Matrix task rooms or send messages.

The English summary is being prepared. Showing the original description.

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding templates (use template-discovery), producing a detailed side-by-side comparison of templates (use template-comparison), authoring custom templates (use template-authoring), deciding cross-parameter defaults such as which framework to pair with native AOT or whether to keep HTTPS when auth is enabled (use template-smart-defaults), modifying existing projects or adding NuGet packages to existing projects.

The English summary is being prepared. Showing the original description.

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding templates (use template-discovery), producing a detailed side-by-side comparison of templates (use template-comparison), authoring custom templates (use template-authoring), deciding cross-parameter defaults such as which framework to pair with native AOT or whether to keep HTTPS when auth is enabled (use template-smart-defaults), modifying existing projects or adding NuGet packages to existing projects.

The English summary is being prepared. Showing the original description.

Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.

The English summary is being prepared. Showing the original description.

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding or comparing templates (use template-discovery), authoring custom templates (use template-authoring), modifying existing projects or adding NuGet packages to existing projects.

The English summary is being prepared. Showing the original description.

Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.

The English summary is being prepared. Showing the original description.

Initialize an Adobe App Builder project end-to-end without Developer Console UI clicks. Creates the Console project and workspace, subscribes APIs (including those needing a product profile), maps user intent to the right template, runs non-interactive `aio app init`, and guides post-init customization. Use whenever the user mentions creating an App Builder app, scaffolding a project, `aio app init`, setting up an Experience Cloud extension, adding actions or web assets, creating a Console project or workspace, adding APIs, or bootstrapping App Builder — even if they don't say "App Builder". Also for SPA templates, AEM extensions, API Mesh, Asset Compute workers, and MCP server projects. Also handles debugging init failures — template not found, `aio app init` hangs or times out, Node version mismatches, npm install failures, post-init build errors, `aio login` issues, `aio app run` showing nothing, or `aio console project create` / `workspace create` / `workspace api add` errors.

The English summary is being prepared. Showing the original description.

Set up a new project's dedicated folder and conventional file layout when its location remains unresolved. Respect limits on inspecting existing files and create the smallest runnable structure needed for the requested product.

• Start a new project without a settled location
• Set up a project without inspecting existing files
• Keep project files out of a general-purpose folder

Scan a codebase to create project documentation and project-specific agent instructions. The first run examines the whole project; later runs focus on changed files, with human confirmation required before updating agent instructions after architectural changes.

• Create documentation when starting agent-assisted development
• Refresh project documentation after architecture changes
• Check changed code for documentation drift

Create a Spring Boot Java project skeleton with Maven, database connection settings, and Docker Compose services. Adds dependencies for API documentation and architecture tests, then checks the generated project with a Maven test command.

• Start a Java 21 Spring Boot project
• Prepare local PostgreSQL, Redis, and MongoDB services
• Add API documentation and architecture test dependencies

Create a Kotlin Spring Boot project with database connections, API documentation, and local services managed through Docker Compose. Set up dependencies and configuration files, then run Gradle tests to check the initial project.

• Starting a Kotlin Spring Boot project
• Setting up local Redis, PostgreSQL, and MongoDB services
• Adding API documentation and architecture test dependencies

Create a Mastra project at a specified version and check its Studio in Chrome. Test page loading, agent chat, tool execution, and workflows, then report passed and failed checks, encountered errors, and screenshots.

• Checking a newly created Mastra project
• Testing initialization with a specified version or package manager
• Checking Studio chat, tools, and workflows

Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.

• Clarify a new project idea through questions
• Define requirements and a phased roadmap
• Save project context and workflow preferences

Manage Apps Script projects through gog: inspect code and metadata, list versions and deployments, download projects locally, create new projects, and run deployed functions with explicit account selection and checks before changes.

• Inspect Apps Script project code and metadata
• Download a project to a local directory
• Check project versions and deployments

Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes `vs project`; otherwise stop without taking action.

The English summary is being prepared. Showing the original description.

Use when you need to create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling. This should trigger for requests such as Create a Micronaut Maven project; Bootstrap Micronaut project with SDKMAN; Generate a new Micronaut service; Create Micronaut 4 Maven project; Scaffold Micronaut service with Java 25. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Use when you need to create a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI tooling. This should trigger for requests such as Create a Quarkus Maven project; Bootstrap Quarkus project with SDKMAN; Generate a new Quarkus service; Create Quarkus 3 Maven project; Scaffold Quarkus service with Java 25. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.