Build a production-ready Ionic Capacitor mobile app with Angular standalone components, lazy-loaded routes, services for cross-cutting concerns, and @ngx-translate/core for i18n.
Build a production-ready Ionic Capacitor mobile app with Angular standalone components, lazy-loaded routes, services for cross-cutting concerns, and @ngx-translate/core for i18n.
Trigger when the user wants to create an Ionic Angular app, scaffold pages (onboarding, paywall, tabs, settings), or wire RevenueCat / AdMob / push notifications into an Angular Ionic project.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Files included with this skill beyond the listing page.
skill mdSKILL.md4,833 B
docsSUMMARY.md392 B
History
First seen on skills.sh
First recorded snapshot · 30 installs
SKILL.md
Ionic + Angular App Guidelines
This is a SKILL file, NOT a project. Never run npm install here. When creating a new project, ask for the project path or scaffold in a separate directory (e.g. ~/Projects/<app>).
When to consult these references
Project setup:
Create a new Angular Ionic project: [new-app.md](references/new-app.md)
❌ NgModules for new pages/components — use standalone components.
❌ IonicModule in standalone components — import the individual components (IonContent, IonButton, …).
❌ Inline template or styles in @Component — always use separate.html, .ts, .scss files via templateUrl and styleUrls.
❌ @angular/http (deprecated) — use @angular/common/http.
❌ any type — use real TypeScript types.
✅ Prefer Signals for reactive state — signal(), computed(), effect(). Services should expose readonly signals where it makes sense — see [signals.md](references/signals.md). Stick to stable signal APIs; avoid Angular features marked "developer preview" / "experimental" (e.g. linkedSignal, resource, Signal Forms) until they graduate.
✅ Use signal inputs / outputs (input(), input.required(), output()) for new components.
Before reporting done
npm install
npx ng build
npx cap sync
The build must complete without errors. cap sync is required after every web build before testing on native.