Skip to content
Back to skills

Build

ASecurity

Build (compile) the solution via the developer CLI - backend (.NET), frontend (React/TypeScript), and the developer CLI itself.

  • 438 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 26, 2026
developmenttypescriptgobashreactfrontendbackend

Works with

  • cli

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add platformplatform/PlatformPlatform --skill build --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Build?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Build
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/platformplatform-build/badge)](https://www.skillsdirectory.com/skills/platformplatform-build)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: build
description: Build (compile) the solution via the developer CLI - backend (.NET), frontend (React/TypeScript), and the developer CLI itself.
---

# Build

```bash
dotnet run --project developer-cli -- build [--backend] [--frontend] [--cli] [--self-contained-system <name>] --quiet
```

Use `developer-cli` exactly as written - do not expand to an absolute worktree path.

- `--backend` - .NET
- `--frontend` - React/TypeScript
- `--cli` - the developer CLI itself
- `--self-contained-system <name>` - narrows the backend build to one SCS (e.g. `account`, `main`)

No arguments builds everything.

## Examples

```bash
dotnet run --project developer-cli -- build --quiet                                           # everything
dotnet run --project developer-cli -- build --backend --quiet                                 # all backend
dotnet run --project developer-cli -- build --frontend --quiet                                # frontend
dotnet run --project developer-cli -- build --backend --self-contained-system main --quiet    # one SCS
```

## Always pass --quiet

Verbose output goes to a log file. On success the CLI prints a single line; on failure it prints a short error summary - read the log if you need the full errors. Without `--quiet` the build floods the conversation.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.