GravionLabs/elysion / .agents/skills/ng-create-project
ng-create-project
VerifiedScaffold an Angular 21+ app or workspace with strict TypeScript, Vitest and ESLint/Prettier. Use when starting a new Angular project.
Scaffold a new Angular 21+ project with a production-ready baseline. Paths to scripts/ and templates/ are relative to this skill's directory.
Stack
@angular/cli≥ 21 (global or vianpx @angular/cli@latest), Node 22 LTS- TypeScript strict mode with Angular compiler options
- Vitest with jsdom (replaces Karma/Jest), on by default
- ESLint + Prettier + Husky via the
setup-prettier-eslint-huskyskill, on by default (Angular stays on Prettier, not Biome: no Angular template support, no SCSS)
Steps
-
Ask: project name, selector prefix (default
app), type app or workspace, whether to skip Vitest or ESLint -
Run the scaffold script:
pwsh scripts/New-AngularProject.ps1 -ProjectName <Name> [-SelectorPrefix app] [-ProjectType app|workspace] [-SkipVitest] [-SkipEslint] [-OutputDirectory .]It runs
ng new --style scss --ssr false, replacestsconfig.jsonwith the strict template, installs Vitest with the template config and patches thetestscripts, then runs the code-quality setup. -
Verify:
ng build,npm test,ng serve(http://localhost:4200) -
Next steps: components and signal stores via
ng-implementation(references/component.md,references/signal-store.md)
Templates
| File | Purpose |
|---|---|
templates/tsconfig.json | Strict Angular compiler options: noImplicitOverride, strictTemplates, module: preserve, target: ES2022 |
templates/vitest.config.ts | jsdom environment, globals, setup file, include: ['**/*.spec.ts'] |
templates/vitest.setup.ts | Empty setup file, extend as needed |
Constraints
- Standalone components only;
standalone: trueis the default, never add NgModules - SCSS for styles; SSR off unless explicitly requested
- Angular 21+ only
Report: summary, project path, verify commands.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |