GravionLabs/elysion / .agents/skills/ng-implementation
ng-implementation
VerifiedAngular 21+ implementation and review rules (standalone, signals, DI, forms). Use when writing or changing Angular code.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| references/component.md | markdown | 1.4 KB |
| references/mcp.md | markdown | 2.3 KB |
| references/signal-store.md | markdown | 982 B |
| references/version-notes.md | markdown | 3.0 KB |
references/component.md
View on GitHub# Scaffold a standalone component
Scaffold one standalone Angular component.
## Steps
1. Ask: component name (kebab-case), selector prefix, target folder, modules to import
2. Validate: name format, folder exists, which file-naming convention the project uses (see below)
3. Create the `.ts` file with `@Component`: `selector: '<prefix>-<name>'`, `changeDetection: ChangeDetectionStrategy.OnPush`, `templateUrl`, `styleUrl` (singular), imports ordered Angular core → Angular common → third-party → local, empty class. Do not add `standalone: true`, it is the default.
4. Create the `.html` file with a minimal placeholder and an empty `.scss` file
5. Add the export to the nearest `index.ts` or `public-api.ts` if one exists
6. Verify: `ng lint`, `ng build`
## File naming
Match the project's existing convention. New Angular 20+ projects follow the CLI default: no `.component` suffix (`header.ts`, `header.html`, `header.scss`, class `Header`); projects that still use `*.component.ts` keep it (class `HeaderComponent`). Never mix both in one project.
## Constraints
- Always `OnPush`; no NgModules
- Class PascalCase, files kebab-case, class and file names must match
- Selector prefix consistent across the project (taken from the project, e.g. `app-*`)
- Barrel export updated, or the component is not importable from the library
Report: summary, files created/updated, 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |