smithery/rzyfront

vendix-frontend-component

Angular component structure rules for Vendix: reuse shared components first, follow zoneless/signals patterns, and align component folder shape with real repo conventions instead of rigid outdated rules. Trigger: When creating Angular components.

Installation

$ npx skills add smithery/rzyfront --skill vendix-frontend-component

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/rzyfront · top by installs.

npx skills add smithery/rzyfront

Browse all from smithery/rzyfront

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version2.0
LicenseMIT
More metadata
author
rzyfront
version
2.0
scope
["root"]
auto_invoke
Creating Angular components

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,755 B
  • docs SUMMARY.md 67 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Vendix Frontend Component

Core Rule

Reuse existing shared components before creating new ones. Check apps/frontend/src/app/shared/components/index.ts first.

Current Reality

The repo mixes:

  • shared components under shared/components/
  • module-local components under components/
  • some components in their own folders
  • many legitimate loose *.component.ts files in a module directory

Do not enforce a false “every component must always live in its own folder with a README” rule on top of the existing codebase.

Required Patterns

  • Frontend code must follow vendix-zoneless-signals.
  • Prefer input(), output(), model(), signal(), and computed() in new code.
  • Keep components standalone when that matches the surrounding module pattern.
  • Match the nearest established pattern in the touched module instead of forcing a repo-wide folder migration.

Shared Component Check

Before creating a new component, inspect shared exports such as buttons, inputs, tables, modals, stats, responsive-data-view, date-range picker, paywall/modal components, diff viewers, pricing cards, and other reusable primitives exposed from shared/components/index.ts.

Related Skills

  • vendix-zoneless-signals
  • vendix-frontend-module
  • vendix-frontend-modal
  • vendix-frontend-data-display