Projen Project Manager

This skill provides expert assistance for projects managed by [projen](https://github.com/projen/projen), a powerful project configuration management tool. It ensures all modifications follow projen conventions and best practices.

What This Skill Does

Guides proper task execution using projen's task runner

Prevents manual editing of generated files

Manages dependencies through projen configuration

Enforces correct workflow for configuration changes

Provides task completion criteria and validation

Instructions

1. Task Execution Protocol

**ALWAYS use projen for running tasks:**

Execute tasks with `node ./projen.js <task-name>` instead of npm, yarn, or other package managers

Before running any task, check `.projen/tasks.json` to see available tasks, descriptions, and steps

Common tasks to use:

- `node ./projen.js` - Synthesize project configuration files

- `node ./projen.js build` - Full build including tests

- `node ./projen.js test` - Run tests only

- `node ./projen.js compile` - Compile source code only

- `node ./projen.js eslint` - Run linter

**When developing projen itself:**

Avoid full builds (they're slow)

Run specific tests: `node ./projen.js test test/path-to-test.test.ts`

Run linter frequently: `node ./projen.js eslint`

2. File Modification Rules

**CRITICAL: Never manually edit generated files**

Files with comments like "~~ Generated by projen. To modify..." are off-limits

If asked to modify package.json, tsconfig.json, or similar files, FIRST check if they're projen-managed

If managed by projen, redirect changes to `.projenrc.ts`, `.projenrc.py`, or `.projenrc.json`

**Configuration change workflow:**

1. Identify the appropriate .projenrc file (`.projenrc.ts`, `.projenrc.py`, `.projenrc.json`, etc.)

2. Make changes to .projenrc configuration

3. Run `node ./projen.js` to regenerate files

4. Review the changes to generated files

5. Commit BOTH .projenrc and generated files together

3. Dependency Management

**Add dependencies through projen configuration:**

NEVER manually edit package.json or run `npm install` directly

In .projenrc, use these methods:

- `addDeps()` - Add runtime dependencies

- `addDevDeps()` - Add development dependencies

- `addPeerDeps()` - Add peer dependencies

After adding dependencies, run `node ./projen.js` to regenerate package.json

Then run `npm install` or your package manager to install

4. Task Completion Criteria

**A task is NOT complete until:**

All tests pass: `node ./projen.js test`

No compilation errors: `node ./projen.js compile`

No linting errors: Check build output or run linter task

Full build succeeds: `node ./projen.js build`

**After modifying source or test files:**

ALWAYS run `node ./projen.js build` to validate changes

Do not consider work done until build passes

5. Common Workflows

**Adding a new dependency:**

```typescript

// In .projenrc.ts

project.addDeps('new-package@^1.0.0');

```

Then run `node ./projen.js` and `npm install`

**Modifying TypeScript configuration:**

```typescript

// In .projenrc.ts

project.tsconfig?.addInclude('custom-path/**/*');

```

Then run `node ./projen.js`

**Adding a custom task:**

```typescript

// In .projenrc.ts

project.addTask('custom-task', {

description: 'My custom task',

exec: 'echo "Running custom task"'

});

```

Then run `node ./projen.js`

Examples

**User asks: "Can you add lodash as a dependency?"**

Correct response:

1. Read .projenrc file to understand project type

2. Modify .projenrc to add: `project.addDeps('lodash');`

3. Run `node ./projen.js` to regenerate package.json

4. Instruct user to run `npm install`

**User asks: "Can you update the tsconfig.json to include a new path?"**

Correct response:

1. Check if tsconfig.json has a projen-generated comment

2. If yes, modify .projenrc instead: `project.tsconfig?.addInclude('new-path/**/*');`

3. Run `node ./projen.js` to regenerate

4. DO NOT manually edit tsconfig.json

**User asks: "Run the tests"**

Correct response:

1. Execute `node ./projen.js test`

2. Report results

3. If failures occur, help debug but ensure fixes also pass build

Important Notes

Projen configuration lives in .projenrc files at repository root

All project metadata, dependencies, scripts, and tooling should be managed through .projenrc

When in doubt, check `.projen/tasks.json` for available tasks

Generated files should always be committed alongside .projenrc changes

Resources: [Projen Documentation](https://projen.io) | [GitHub Repository](https://github.com/projen/projen)

Constraints

NEVER edit files marked as generated by projen

NEVER use npm/yarn commands directly for tasks that projen provides

NEVER add dependencies by manually editing package.json

ALWAYS synthesize after .projenrc changes

ALWAYS validate with full build before marking work complete

Projen Project Manager

Projen Project Manager

What This Skill Does

Instructions

1. Task Execution Protocol

2. File Modification Rules

3. Dependency Management

4. Task Completion Criteria

5. Common Workflows

Examples

Important Notes

Constraints

Reviews (0)