Skip to content
Skills Library
Programming · Building & coding

agentuity-project

/agentuity-project

Use when creating, importing, running, building, or deploying an Agentuity app. Covers framework-first project structure, agentuity.json, .env setup, agentuity dev, agentuity build, agentuity deploy, monorepo --dir usage, and deployment bundle inspection.

Repository
sdk ↗
Licence
Apache-2.0
Last repository change
31.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 31.07.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when creating, importing, running, building, or deploying an Agentuity app. Covers framework-first project structure, agentuity.json, .env setup, agentuity dev, agentuity build, agentuity deploy, monorepo --dir usage, and deployment bundle inspection.

Original author description

Use when creating, importing, running, building, or deploying an Agentuity app. Covers framework-first project structure, agentuity.json, .env setup, agentuity dev, agentuity build, agentuity deploy, monorepo --dir usage, and deployment bundle inspection.

How it works

  1. Choose Create or Import
  2. What Agentuity Adds
  3. Development Loop
  4. Build and Deploy
  5. Existing App Checklist
  6. Working With Services
  7. Common Mistakes
  8. Useful Docs
Original SKILL.md headings · 131 lines, 572 words
SKILL.md preview
---
name: agentuity-project
description: >-
  Use when creating, importing, running, building, or deploying an Agentuity app.
  Covers framework-first project structure, agentuity.json, .env setup,
  agentuity dev, agentuity build, agentuity deploy, monorepo --dir usage, and
  deployment bundle inspection.
license: Apache-2.0
metadata:
  author: agentuity
  version: "1.0.0"
---

# Agentuity Project Lifecycle

Agentuity deploys framework apps as they are. Keep the framework's routing,
pages, server functions, and config in their normal locations. Agentuity adds
project metadata, local environment wiring, build packaging, deployment, and
managed services.

## Choose Create or Import

Use `agentuity create` for a new app:

```bash
agentuity create --name my-app --framework nextjs
```

Use `agentuity project import` for an existing framework app:

```bash
agentuity project import --name my-app --confirm
```

For monorepos, run commands from the app package or pass `--dir`:

```bash
agentuity project import --dir apps/web --name web --confirm
agentuity deploy --dir apps/web
```

## What Agentuity Adds

After create/import, expect these files next to the app's `package.json`:

| File | Purpose |
|---|---|
| `agentuity.json` | Project, org, region, and deployment metadata |
| `.env` | Local SDK key and linked resource values |
| `.agentuity/launch.json` | Build output contract produced by `agentuity build` |

The framework still owns `dev`, `build`, and route files. Agentuity adds deploy tooling and cloud resource wiring.

## Development Loop

Use the framework's normal dev command for everyday framework work. Run through
Agentuity when you want the CLI to inject linked project credentials, expose the
Agentuity tunnel, or validate the deployed-like environment:

```bash
agentuity dev
```

Read the terminal output for the actual local URL and tunnel URL. Do not invent
localhost ports or public deployment URLs.

## Build and Deploy

Build locally when you need to inspect packaging:

```bash
agentuity build
```

Check `.agentuity/launch.json` after a build. It describes the process Agentuity will start after deployment.

Deploy from a linked project:

```bash
agentuity deploy
```

For multiple environments (same code, different cloud projects):

```bash
agentuity deploy \
  --project-config agentuity.staging.json \
  --env .env \
  --env .env.staging
```

`--project-config` selects the project metadata file (default `agentuity.json`).
Global `--env` loads env files in order; later files override earlier keys.

The deploy flow syncs non-Agentuity env values, builds the app, packages the
bundle, uploads assets, provisions the deployment, and prints the deployment ID
plus URLs.

## Existing App Checklist

Before deploying an existing app:

1. Run `agentuity project import --validate-only`.
2. Fix any reported framework, package, or build issues.
3. Run `agentuity project import --name <name> --confirm`.
4. Run `agentuity build`.
5. Inspect `.agentuity/launch.json`.
6. Run `agentuity deploy`.

## Working With Services

When adding Agentuity services to app code, import standalone clients in the server-side module that owns the work:

```typescript
import { KeyValueClient } from '@agentuity/keyvalue';

const kv = new KeyValueClient();

export async function saveDraft(userId: string, draft: string): Promise<void> {
  await kv.set('drafts', userId, { draft }, { ttl: 60 * 60 * 24 });
}
```

For service selection and client examples, use the `agentuity-services` skill.
For terminal management of resources, use the `agentuity-cloud` skill.

## Common Mistakes

| Mistake | Better approach |
|---|---|
| Moving framework files into Agentuity-owned folders | Keep route and page files where the framework expects them |
| Creating project metadata by hand | Use `agentuity create` or `agentuity project import` |
| Treating `agentuity dev` as mandatory | Use it only for CLI env wiring, tunnel output, or deploy-like validation |
| Guessing deployment URLs | Read `agentuity deploy` output or inspect deployments with the CLI |
| Importing from the repo root in a monorepo | Run from the app package or use `--dir` |

## Useful Docs

- Project structure: https://agentuity.dev/get-started/project-structure
- Import existing app: https://agentuity.dev/get-started/import-existing-app
- Deployment: https://agentuity.dev/reference/cli/deployment
- Build configuration: https://agentuity.dev/reference/cli/build-configuration

Versions

The database has no other skills named agentuity-project.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 5683e278aee9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agentuity-cli
    Use when working with the Agentuity CLI itself: installation, authentication, profiles, JSON output, command discovery, schema inspection, non-interactive automation, structured input, and deciding which Agentuity command family to use.
  • 100agentuity-database
    Use when adding relational data to an Agentuity app. Covers creating or linking managed Postgres, DATABASE_URL, pg, Drizzle ORM, pooling, transactions, migrations, safe parameter binding, and the narrow admin-script role for DBClient.
  • 100dev
    Local development guide for the Happy monorepo. How to build, install, test, and run the CLI, server, mobile app, and desktop (Tauri) locally. Use when the user types /dev, asks how to "build", "start dev", "install locally", or "run the ___ package".
  • 100app-dev-practices
    Practical guide for building Fusebase Apps apps. Use when: (1) Creating a new app, (2) Setting up project structure, Vite config, or authentication, (3) Building or registering apps, (4) Configuring permissions or public access, (5) Navigating between apps, (6) Fetching user…
  • 100monorepo
    Monorepo scripts, package boilerplate, conventions. Use when: "how do I run", "bun run", "build this", "run tests", "typecheck", "create a new package", linting, scaffolding packages.
  • 100dev
    Development workflows for WordPress ActivityPub plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, building assets, or working with wp-env.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.