ng-add-demo

Automates adding Angular demo modules with registry, component, route, and guide creation.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/alexander-kastil/advanced-angular-agentic-swe --skill ng-add-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ng-add-demo
Source: https://github.com/alexander-kastil/advanced-angular-agentic-swe/tree/main/.github/skills/ng-add-demo
Command: npx skills add https://github.com/alexander-kastil/advanced-angular-agentic-swe --skill ng-add-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding a new Angular demo across modules requires repetitive boilerplate: registry updates, component generation, route wiring, and guide creation. This skill automates those steps to ensure consistency and reduce manual errors.

Core Features & Use Cases

  • Register in db.json and include the new demo in the registry.
  • Generate the Angular component, integrate MarkdownRenderer, and wire the route.
  • Create a minimal markdown guide and ensure the route renders correctly.

Quick Start

Register the demo in the module's db.json, generate the component, configure the Markdown renderer, create the markdown guide, and update the routes.

Frequently Asked Questions about ng-add-demo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate adding a new Angular demo component and route?

Automate Angular demo creation by registering the demo in db.json, generating the component, wiring routes, integrating a Markdown renderer, and creating a placeholder guide to ensure end-to-end consistency.

What boilerplate is required when adding an Angular demo to an existing module?

Adding an Angular demo requires repetitive boilerplate including registry updates in db.json, component generation, route wiring, and markdown guide creation to avoid manual errors across project modules.

How does a Markdown renderer integrate with new Angular component routes?

A Markdown renderer integrates with new Angular components by wiring the generated route to render a minimal markdown guide, ensuring the route displays the documentation placeholder correctly within the module.

Can I auto-generate Angular demo guides and registry entries for multiple modules?

Yes, the automation applies to Angular module workflows where demos need to be added consistently across projects and teams by modifying db.json, generating components, and updating routes.

What are the limitations of automating Angular component generation and route wiring?

The automation targets Angular module workflows and requires modifying db.json, generating components, and updating routes, limiting its use to projects following this specific registry and markdown guide structure.