Results for “projects”

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.

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.

Connect work from multiple AI agents to GitHub Projects. Synchronize task cards and statuses, assign work based on expertise and workload, and generate progress reports so teams can track assignments, priorities, and blockers on shared boards.

• Synchronize agent tasks with GitHub Projects cards
• Assign work based on expertise and workload
• Track sprint progress and blocked tasks

Implement .NET workflows for Azure AI Foundry projects, including agent creation, resource connections, dataset uploads, model deployment inspection, search index management, and evaluations. Examples also cover authentication, asynchronous operations, and resource cleanup.

• Creating and running agents from a .NET application
• Inspecting resource connections and model deployments
• Uploading datasets and managing search indexes

Set up services such as databases and SMS for a project through Stripe Projects. Sync generated credentials into `.env`, connect supported provider accounts, and manage credential rotation, plan changes, and service removal.

• Set up a Postgres database for a project
• Add an SMS service to an application
• Sync service credentials and rotate keys

Review abandoned personal projects through local Git history to identify likely stopping points and recurring patterns. Compare revival candidates, select one worth revisiting, and outline concrete steps from checking whether it still runs to publishing it.

• Taking stock of unfinished personal projects
• Finding recurring reasons projects stall
• Choosing one project to revive and publish

Learn AI engineering by building a project one stage at a time. The tutor guides predictions, learner-written code, automated checks, and reflection, then records progress so the next session can continue from the right stage.

• Learn AI engineering through hands-on projects
• Resume a project from the next unfinished stage
• Find coding mistakes with step-by-step hints

Implement Java workflows for Azure AI Foundry projects using SDK examples for authentication, connected resources, datasets, search indexes, and model evaluations. The skill also covers client setup, paginated resource lists, and error handling.

• List connected Azure resources
• Create or update search indexes
• Implement access to model evaluations

Build Python AI applications on Microsoft Foundry with azure-ai-projects. Provides examples for creating agents, connecting tools, managing conversations and project resources, and running evaluations through Foundry and OpenAI-compatible clients.

• Build an agent that searches uploaded documents
• Implement conversation threads and response handling
• List model deployments and project connections

Create container-based hosted agents in Azure AI Foundry using Python and the Azure AI Projects SDK. Follow examples for resource settings, authentication, version management, and checks needed before treating a deployment as healthy.

• Creating a hosted agent from a custom container image
• Configuring CPU, memory, and environment variables
• Listing and deleting agent versions

Build TypeScript code for Azure AI Foundry projects using its SDK, a library for accessing project services. Create and run agents, inspect connections and deployed models, and manage datasets and search indexes.

• Creating and running agents in TypeScript
• Adding file search or external tools to agents
• Inspecting project connections and deployed models

Coordinate multiple Claude Code workers through an existing Kanban board. This guide describes task dispatch, automated checks before AI review, per-task cost tracking, human intervention, and recovery after restarts; the runtime and integrations require separate installation.

• Coordinating multiple Claude Code workers
• Running automated checks before AI code review
• Monitoring task progress and development costs on a board

Manage complex software and SaaS projects by assessing schedules, budgets, quality, risks, and team capacity. Compare priorities across projects, identify resource constraints, and turn portfolio analysis into executive reports with recommendations for decisions and follow-up.

• Review progress and health across multiple projects
• Assess risks and prioritize response actions
• Rebalance staffing based on team capacity

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

Guide for modernizing and migrating MSBuild project files to SDK-style format. USE FOR: converting legacy .csproj/.vbproj with verbose XML to SDK-style, migrating packages.config to PackageReference, removing Properties/AssemblyInfo.cs in favor of auto-generation, eliminating explicit Compile Include lists via implicit globbing, consolidating shared settings into Directory.Build.props. Indicators of legacy projects: ToolsVersion attribute, an Import of Microsoft.CSharp.targets via $(MSBuildToolsPath), .csproj files over 50 lines for simple projects. DO NOT USE FOR: projects already in SDK-style format, non-.NET build systems (npm, Maven, CMake), .NET Framework projects that cannot move to SDK-style.

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

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

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

Portfolio dashboard for all GSD-tracked projects. Scans ~/Projects and ~/gsd-workspaces for .planning/ directories, shows phase status, git state, blockers, and next actions for every project. Run /ops projects to see the full portfolio.

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

Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents", "evaluations", "datasets", "connections", "deployments .NET".

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

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

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

Manages MATLAB projects for Simulink workflows: path management, file registration, labels, source control configuration, and project lifecycle. Use when creating projects, adding models/dictionaries/requirements to projects, configuring labels for automation, fixing broken model references, or setting up source control for Simulink artifacts.

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

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

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

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

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

Guide for modernizing and migrating MSBuild project files to SDK-style format. USE FOR: converting legacy .csproj/.vbproj with verbose XML to SDK-style, migrating packages.config to PackageReference, removing Properties/AssemblyInfo.cs in favor of auto-generation, eliminating explicit Compile Include lists via implicit globbing, consolidating shared settings into Directory.Build.props. Indicators of legacy projects: ToolsVersion attribute, an Import of Microsoft.CSharp.targets via $(MSBuildToolsPath), .csproj files over 50 lines for simple projects. DO NOT USE FOR: projects already in SDK-style format, non-.NET build systems (npm, Maven, CMake), .NET Framework projects that cannot move to SDK-style.

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