What does this skill do, and when should you use it?
angular-new-app is an Agent Skill in the angular/skills repository, maintained by the Angular Team at Google. It activates whenever a user wants to create a new Angular application, instructing the agent to verify the Angular CLI, scaffold a project with ng new, and wire up AI configuration. It then standardizes how components, services, and other artifacts are generated, and covers Tailwind CSS integration. Ideal for developers whose coding agent should produce code aligned with current Angular conventions.
Checks for the Angular CLI via which ng / where ng and suggests npm install -g @angular/cli if missing; creates the app with npx ng new <app-name> using --interactive=false and an --ai-config option, plus flags like --style, --routing, --ssr and --prefix; generates components, services, pipes, directives, interfaces, guards, interceptors, resolvers, enums and classes via npx ng generate; validates and repairs with npx ng build; adds Tailwind v4 via npx ng add tailwindcss; and points the agent to the CLI's bundled MCP server (ng mcp) for best practices.
- A developer wants an agent to bootstrap a brand-new Angular project instead of hand-writing files
- A team wants generated Angular code to follow official best practices, with the agent loading the AI config that ng new emits
- An agent should continue generating components, services and other Angular code right after project creation
- You want server-side rendering (--ssr) or Tailwind CSS set up at scaffold time
- Angular developers using Agent Skills-capable tools like Gemini CLI or Antigravity
How do you install this skill?
- Static review only; no commands were executed, and actual outcomes must be verified by the user.
- The core flow fully depends on the npm registry and internet access (including tailwindcss.com); npx installs and doc access may fail in mainland-China networks.
- npm install -g and npx fetches execute third-party code; users should confirm source and versions before consenting.
- No rollback or uninstall guidance is provided; trial in a controlled environment first.
- Maintenance happens in the angular/angular repository; the skills repo is generated output, so updates should be tracked there.
- Shell / CLI
- Network access
- Local filesystem
Node.jsnpmAngular CLI
In an Agent Skills-capable environment (Gemini CLI, Antigravity, or via the community tool skills.sh), run: npx skills add https://github.com/angular/skills. The repo bundles two skills, angular-developer and angular-new-app; this one lives at angular-new-app/ (containing SKILL.md). Consult your specific tool's docs for its install location.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/angular/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/angular-new-app" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Scaffold a new Angular project called my-app with SCSS and routing
After installing, simply ask your agent to create a new Angular app, e.g. "Scaffold a new Angular project called my-app with SCSS and routing". The skill requires node, npm, and internet access; prefer the --ai-config value matching your environment (agent, claude, copilot, cursor, gemini, jetbrains, none, windsurf). Note: don't start the app until features exist — use npx ng build to catch errors.
What are this skill's strengths and limitations?
- Officially maintained by the Angular Team; commands and flags follow current CLI usage
- Covers the full flow: environment check, scaffolding, code generation, Tailwind setup
- Leverages ng new's --ai-config so the generated project ships with AI tooling config
- Surfaces the CLI's bundled MCP server (ng mcp) as a best-practices source
- Repo README shows no license; only SKILL.md declares MIT, and the repo lacks a description and topics
- Contributions and issues must go through the angular/angular repo, an indirect feedback path
- No evidence of a test suite or cross-platform validation beyond what the docs state
- Scoped to new-app creation only; day-to-day development on existing projects needs the angular-developer skill
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Angular New App Skill this page | 52 · Use with care | ★ 685 | 11d ago | — |
| Angular Developer Skill | 63 · Recommended | ★ 685 | 11d ago | — |
| Context7 Project Bootstrapper ✓ Microsoft · Official | 36 · Not recommended | ★ 194k | 11d ago | MIT |
| Azure Blob Storage for TypeScript ✓ Microsoft · Official | 51 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Azure File Share TypeScript Skill ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
The sibling angular-developer skill in the same repo handles code generation and architectural guidance for existing projects (signals, forms, routing, SSR, etc.); angular-new-app focuses purely on scaffolding. They complement each other — pick this one for new projects.
How did FollowSkills review this skill?
Instructions only invoke official Angular CLI commands; no sensitive-data access or covert exfiltration; user is asked before global installation. However, it relies on npx/npm fetching external packages, lacks rollback guidance and explicit permission scoping, so full marks are not justified. Score 15; deducted for incomplete dependency-security and rollback/data-flow disclosure.
Steps are self-consistent (check CLI, create, generate), and the missing-CLI failure path is handled. But there is no test or reproduction evidence, and abnormal inputs (npx failure, network errors, invalid flags) lack diagnosable feedback; static cap is 10. Score 9; deducted for thin error handling and failure feedback.
Trigger scenario is clear (creating a new Angular app) with useful flags and ai-config options listed. Non-fit boundaries are undeclared, and the core flow fully depends on npm registry and internet access, posing mainland-China reachability risk, which is deducted per rules. Score 8.
SKILL.md carries name, description, MIT license, version and author metadata; README gives a clear contribution/maintenance path via angular/angular. Documentation layering is reasonable, but versioning is a bare '1.0' with no changelog and repo-level license metadata is unknown. Score 10; deducted for incomplete versioning/governance and known-limitation disclosure.
The described workflow is complete and plausibly produces a consistent modern Angular app via the CLI; however, static review cannot verify output correctness, comparative benefit is unevidenced, and the static cap is 7. Score 6; deducted for lack of representative output verification.
Only declarative instructions and external links; no committed tests or third-party execution evidence; key claims are not independently reproducible, static cap is 5. Score 4; deducted for absence of reproducible test coverage.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →