rzyfront/vendix-frontend-component
skills/vendix-frontend-component/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add rzyfront/vendix vendix-frontend-componentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 16, 2026, 5:06 AM135.5s1 file scanned
SKILL.md
- name:
- vendix-frontend-component
- description:
- >
- Angular component structure rules for Vendix:
- reuse shared components first, follow
- instead of rigid outdated rules. Trigger:
- When creating Angular components.
- license:
- MIT
- author:
- rzyfront
- version:
- 2.0
- scope:
- [root]
- auto_invoke:
- Creating Angular components
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.tsfiles 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(), andcomputed()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-signalsvendix-frontend-modulevendix-frontend-modalvendix-frontend-data-display
Related Skills
rzyfront/mobile-dev
development
VerifiedTrustedCommunity
Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features.
5SKILL.mdUpdated May 29, 2026
rzyfront/vendix-subscription-gate
development
VerifiedTrustedCommunity
Feature gating by store subscription state: global store write guard, AI feature gate, Redis feature resolution, quota consumption, frontend paywall interceptor, banner, and subscription UI states. Trigger: When adding feature gates, paywalls, subscription-based access control, protecting store write operations, AI feature gates, or rollout flags.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-saas-billing
testing
VerifiedTrustedCommunity
SaaS subscription billing for Vendix stores: plan pricing, invoices, Wompi platform payments, manual payments, partner commissions, payouts, proration, and dunning. Trigger: When creating SaaS invoices, working with partner rev-share, margin/surcharge pricing, invoice sequence allocation, partner payout batches, subscription payments, manual payments, or dunning flows.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-redis-quota
development
VerifiedTrustedCommunity
Periodic quota counters with Redis, UTC period keys, Lua-based idempotent AI quota consumption, request-id deduplication, and post-success consumption. Trigger: When building quota counters, enforcing monthly/daily feature caps, or reusing AI quota patterns for uploads, emails, exports, or rate-limited features.
5SKILL.mdUpdated May 16, 2026