Skip to content

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Security policy

Stars

5 stars

Watchers

0 watching

Forks

Latest commit

 

History

132 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NgAutoPilot 🚀

English · Español · Documentation map

Give your coding agent a route, not a pile of instructions.

NgAutoPilot is a CLI and a catalog of small engineering guides (skills). It helps an agent inspect your project, detect versions, choose relevant guidance, make a bounded change, and validate the result. It is not an Angular runtime library or an automatic code migrator.

From the catalog to a useful pack, to your project and evidence; you lead the process.

🧭 Start here: one command

Explore the 15 options, choose a pack and agent, install, then list the installed skills.

You only need Node.js 22.20+, npm and an existing project. No global NgAutoPilot installation is required for the recommended workflow.

Run inside the project you want to improve:

npx skills add janpereira-dev/ngAutoPilot

Choose one or more of the 15 focused bundles. Each choice installs full canonical procedures as local Markdown references, so your agent can read them without installing the NgAutoPilot CLI. For a direct Angular example:

npx skills add janpereira-dev/ngAutoPilot --skill ngautopilot-angular-20-22 -a codex

To inspect before installing, run npx skills add janpereira-dev/ngAutoPilot --list. To check installed entries, use npx skills list. Review the selected agent and installation scope before confirming; installing instructions does not edit or automatically migrate your app.

Next: first Angular task · installation · troubleshooting.

📦 The 15 install choices

For broad discovery, NgAutoPilot exposes 15 curated gateway skills instead of placing all 413 canonical micro-skills in the interactive selector:

# Interactive: choose one or more curated gateways
npx skills add janpereira-dev/ngAutoPilot

# Direct examples
npx skills add janpereira-dev/ngAutoPilot --skill ngautopilot-angular-20-22
npx skills add janpereira-dev/ngAutoPilot --skill ngautopilot-angular-upgrades
npx skills add janpereira-dev/ngAutoPilot --skill ngautopilot-full
Gateway Scope
ngautopilot-core Intake, stack detection, routing, compatibility, risk
ngautopilot-angular Complete Angular capability gateway
ngautopilot-angular-upgrades All bounded Angular upgrade routes
ngautopilot-angular-microfrontends Hosts, remotes, federation, contracts, rollback
ngautopilot-frontend UX, accessibility, responsive UI, design systems
ngautopilot-performance Angular/frontend performance and optimization
ngautopilot-quality Quality plus TypeScript/JavaScript/CSS safety routes
ngautopilot-angular-2-5 Angular 2→4→5 legacy era; Angular 3 was never released
ngautopilot-angular-6-8 Workspace, RxJS 6, HttpClient, pre-Ivy era
ngautopilot-angular-9-12 Ivy, localize, testing, build and browser-policy era
ngautopilot-angular-13-15 Ivy-only, typed forms, standalone start, Material MDC
ngautopilot-angular-16-17 Signals, standalone, hydration, control flow, defer
ngautopilot-angular-18-19 Runtime/testing changes and standalone-by-default
ngautopilot-angular-20-22 Zoneless, resources, Signal Forms, SSR, AI/MCP
ngautopilot-full Explicit all-in routing gateway

The gateways keep discovery small and include the canonical procedure bodies locally. Use the native CLI only for advanced operations (exact hop plans, backups, managed updates or the separate MCP). This avoids a 400-item picker without losing useful technical detail.

🎒 Pick the pack for today's job

Choose a public pack for Core, Angular, an era, upgrades, quality, performance, frontend, or microfrontends.

Your task Start with
Basic workflow, any project ngautopilot-core
Angular architecture, components, forms, state, tests ngautopilot-angular
Guidance for an Angular era An era pack, e.g. ngautopilot-angular-20-22
Angular upgrade guidance ngautopilot-angular-upgrades
Measured rendering and web performance ngautopilot-performance
Language safety and code quality ngautopilot-quality
Framework-neutral accessibility and UX ngautopilot-frontend
Federation, hosts and remotes ngautopilot-angular-microfrontends

Every ID in this table works with npx skills add janpereira-dev/ngAutoPilot --skill <id>. You can install multiple public packs together. For upgrades, open only the procedure for the next supported major hop.

The optional native CLI has additional granular packs such as ngautopilot-angular-foundations and ngautopilot-angular-17-to-18. Those IDs belong to ngautopilot install --pack, not to the 15-option npx skills selector. Its managed selection and pack-switching rules are described in advanced native pack installation. Use ngautopilot-full only when you need the entire catalog.

🧩 Five useful concepts

A pack contains selected skills and optional roles; an adapter places them for the host; guardrails guide review, not permissions.

Concept Plain meaning
Skill A procedure for one engineering problem
Pack A selection of skills and optional specialist assets
Adapter The installation layout for your agent
Subagent role A Markdown specialist definition; not a running agent by itself
Guardrail A review rule requiring evidence or mitigation; not runtime enforcement
Your task → inspect → detect versions → select guidance → check risks
         → make a small change → validate → report evidence

Five steps: inspect project and versions, choose a skill, approve a bounded change, validate, and report evidence.

The decorative animation runs once for 3.6 seconds and respects reduced motion. All steps remain readable in a static preview.

The human directs the task. Skills guide the agent. Tests and review prove the result. Installing Markdown does not grant permissions, deploy services, register MCP, or automatically start subagents.

💬 Try a useful prompt

Brief the agent with task, versions, skill and plan; request named guidance, real checks and remaining limits.

Inspect this project's Angular, Node, TypeScript, and RxJS versions. Identify the installed NgAutoPilot skill for lazy-loaded routes. Explain the smallest safe change before editing, then validate using the project's existing checks. Report checks you could not run.

For test review, substitute “review fragile TestBed setup and asynchronous behavior.” For upgrades, name the current and next major version and keep modernization separate.

Success means: detected versions, a named applicable skill, a bounded plan, and real validation output—not just “done.”

🔎 Catalog and repository map

Canonical sources feed generated catalog, native bundles and portable packages; edit sources, not generated copies.

Current catalog size: 413 skills

This checkout's doctor reports 36 packs and 10 adapters. Run doctor, packs, and adapters for your installed version instead of assuming every release matches.

Source Responsibility
skills/_core/ Intake, detection, routing, compatibility, risk
skills/angular/versioning/ Version-aware decisions
skills/angular/upgrades/ Major hops, including skills/angular/upgrades/21-to-22/
skills/angular/modernization/ Standalone, control flow, @defer, zoneless adoption after stability
skills/angular/architecture/ Application boundaries and patterns
skills/angular/microfrontends/ Distributed frontend boundaries
skills/angular/docs/ ADRs, upgrade reports, review packets
skills/frontend/, skills/css/ Accessibility, UX, design, layout, performance
skills/typescript/, skills/javascript/, skills/quality/ Cross-cutting language and quality procedures

skills/ remains canonical. skills/SKILL.md is an internal discovery boundary, while .agents/skills/ is the generated 15-gateway public surface for broad discovery. catalog.json, plugins/, and agent-plugins/ are generated distributions; do not hand-edit their copies. Architecture.

🛤️ Choose the right distribution

CLI, native marketplace, Agent Plugins Preview and discovery routes have different contracts and separate host checks.

Route What it does What it does not prove
NgAutoPilot CLI Focused packs or supported Angular profiles Host discovery or invocation
npx skills add janpereira-dev/ngAutoPilot 15 curated bundles with local canonical procedures No automatic source edits or MCP registration
Claude/Codex marketplace manifests Native bundle descriptions Publication, approval, universal compatibility
Agent Plugins Preview Portable skills plus separate read-only stdio MCP End-to-end installation in every host
Pi metadata The same curated gateway surface from the npm package Verified host runtime behavior

Adapter IDs: claude, codex, copilot, cursor, gemini, generic, hermes, openclaw, opencode, pi. Native, adapter, experimental, and unverified are different statuses. Installation matrix.

The OpenAI packet in this branch is skills-only, not submitted, and not OpenAI verified. Human attestations remain human actions. Run npm run openai:validate and npm run openai:pack for the current skills-only package. Release boundary.

📚 Choose your next chapter

Three reading routes: first use, daily work, and maintaining or contributing.

You want to… Read
Start without knowing the terminology Getting started
Follow a complete first-use example First Angular project
Install, switch, export, or work offline Installation
Find an exact command CLI reference
Understand Angular guidance Version support, era map
Maintain installed files Updating, uninstalling
Understand roles and review rules Roles, prompts and guardrails
Register the separate MCP server MCP and ChatGPT
Contribute or release Contributing, maintainer guide, release checklist

All guides, historical records, and translation status: English map · Mapa en español.

🛠️ Maintainer checkpoint

Maintainer route: validate sources, generate the index, sync bundles, check consistency, review diff before release.

For catalog changes, use the existing source pipeline:

npm run skills:validate
npm run skills:catalog
npm run plugins:sync
npm run agent-plugins:sync
npm run npx-skills:sync
npm run npx-skills:validate
npm run consistency:validate

The release checklist covers the full validation and packaging procedure. These commands can regenerate files: inspect the diff. Local checks do not prove publication or review approval.

License and community

MIT · License · Security reporting · Code of conduct · Changelog · Roadmap

Release and publication roadmap

0.11.0 release and publication tasks · Capability platform · Native exports · Safe pack transitions

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Security policy

Stars

5 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages