AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Init

skill-makigjuro-cloudstack-ai-plugins-init · by makigjuro

Scan a project and generate cloudstack.json configuration. Use when setting up cloudstack-ai-plugins for the first time, onboarding a new project, or when the user says "init", "setup", "configure", "get started", or "onboard".

No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-makigjuro-cloudstack-ai-plugins-init

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-makigjuro-cloudstack-ai-plugins-init)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Init? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Initialize Project

Scan the project structure, detect the tech stack, and generate a cloudstack.json configuration file. This is the first thing users should run after installing cloudstack-ai-plugins.

Arguments

  • --minimal -- Generate only the essential fields, skip optional sections

Process

Step 1: Check for existing config

test -f cloudstack.json && echo "EXISTS" || echo "NONE"

If cloudstack.json already exists, ask the user whether to overwrite or update it.

Step 2: Detect project structure

Run these scans in parallel:

Backend detection:

# .NET solution
find . -name "*.sln" -maxdepth 3 -not -path "./.git/*" 2>/dev/null

# Shared domain project
find . -path "*/Domain/Entities" -type d -not -path "*/bin/*" -not -path "*/obj/*" 2>/dev/null

# Shared infrastructure project
find . -path "*Shared*Infrastructure*" -name "*.csproj" -not -path "*/bin/*" 2>/dev/null

# Microservices (directories containing .Application subfolder)
find . -name "*.Application" -type d -not -path "*/bin/*" -not -path "*/obj/*" 2>/dev/null

# Messaging framework
grep -rl "WolverineFx\|MediatR\|MassTransit" --include="*.csproj" -l 2>/dev/null | head -1

# ORM detection
grep -rl "Microsoft.EntityFrameworkCore" --include="*.csproj" -l 2>/dev/null | head -1

Frontend detection:

# Package.json location
find . -name "package.json" -maxdepth 3 -not -path "*/node_modules/*" -not -path "*/tools/*" 2>/dev/null

# If found, detect framework and libraries from dependencies
cat /package.json | grep -E "react|vue|angular|@tanstack|zustand|redux|shadcn|@mui|vite|webpack|next"

Infrastructure detection:

# Terraform
find . -name "*.tf" -maxdepth 4 -not -path "./.git/*" 2>/dev/null | head -1

# Terragrunt
find . -name "terragrunt.hcl" -maxdepth 4 2>/dev/null | head -1

# Helm charts
find . -name "Chart.yaml" -maxdepth 4 2>/dev/null

# Docker Compose
find . -name "docker-compose*.yml" -o -name "docker-compose*.yaml" -maxdepth 3 2>/dev/null

# .NET Aspire
find . -name "*AppHost*" -type d -maxdepth 4 2>/dev/null

# CI/CD
ls .github/workflows/*.yml 2>/dev/null || ls .gitlab-ci.yml 2>/dev/null || ls azure-pipelines.yml 2>/dev/null

Repository detection:

git remote get-url origin 2>/dev/null

Step 3: Resolve ambiguities

Use AskUserQuestion for anything that can't be auto-detected:

  • Multiple solutions found -- Ask which is the primary one
  • No namespace detectable -- Ask for the root C# namespace
  • Multiple frontend directories -- Ask which is the main one
  • Cloud provider unclear -- Ask Azure vs AWS vs GCP

Keep questions to a minimum. If a value is clearly detectable, don't ask.

Step 4: Generate cloudstack.json

Build the configuration object from detected values. Include:

  • $schema reference for IDE autocompletion
  • project -- name (from solution name or directory), namespace (from .csproj)
  • repository -- owner/name (from git remote)
  • backend -- solutionPath, sharedDomainPath, sharedInfraPath, services[], orm, messaging
  • frontend -- path, framework, stateManagement, uiLibrary, bundler, devPort
  • infrastructure -- cloud, iac, iacWrapper, terraformPath, chartsPath, namespace
  • localDev -- orchestrator, appHostPath or composePath
  • conventions -- branchFormat (detect from existing branches), commitStyle

If --minimal was passed, only include project, backend.solutionPath, and backend.services[].

Write the file:

# Write cloudstack.json to project root

Step 5: Recommend plugins

Based on what was detected, recommend which plugins to install:

## Project Initialized

Created `cloudstack.json` with:
- {N} microservices detected
- {frontend framework} frontend at `{path}/`
- {iac tool} infrastructure at `{path}/`

### Recommended plugins:

| Plugin | Why | Install |
|--------|-----|---------|
| dotnet-architect | {N} .NET services detected | `/plugin install dotnet-architect@cloudstack-ai-plugins` |
| react-developer | React frontend at `{path}/` | `/plugin install react-developer@cloudstack-ai-plugins` |
| cloud-infra | Terraform + Helm detected | `/plugin install cloud-infra@cloudstack-ai-plugins` |
| dev-workflow | Git workflow + CI/CD | `/plugin install dev-workflow@cloudstack-ai-plugins` |

### Next steps:
1. Review `cloudstack.json` and adjust any values
2. Install recommended plugins above
3. Try `/dotnet-architect:check-architecture` to validate your project

Only recommend plugins relevant to what was detected (e.g., skip react-developer if no frontend found).

Error Handling

  • Not a git repo: Warn but continue -- skip repository section
  • No .NET solution found: Skip backend section, note it
  • No frontend found: Skip frontend section
  • Permission denied on scan: Note the directory and skip it

Related Skills

  • /dotnet-architect:check-architecture -- Run after init to validate architecture
  • /dev-workflow:start-work -- Begin implementing with proper branch workflow

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.