transporte-terrestre
Official@transporte-terrestre
Standardized Angular architecture and component library implementation for enterprise-grade frontend development and design system consistency.
Agent Skills by transporte-terrestre
Showing 8 vetted skills indexed across 1 GitHub repositories.
angular-api
Configure the auto-generated backend.api.ts client in Angular's dependency injection system.
angular-theme
Manage Angular light and dark theme state with signals and localStorage.
angular-components
Create reusable Angular UI components with Signals and global overlays.
angular-route
Manage Angular routing with lazy loading and role-based guards.
angular-architecture
Define standardized Angular project directory structures and naming conventions.
angular-style
Manage global CSS styles and typography for Angular applications using CSS variables.
angular-icon
Integrate FontAwesome and SVG icons into Angular projects via angular.json.
angular-tailwind
Configure Tailwind CSS with PostCSS in an Angular project.
Frequently Asked Questions About transporte-terrestre
FAQPage SchemaWhat specific frontend tasks does this registry enable?▼
This registry enables the configuration of standardized Angular project structures, the implementation of reusable UI components using Signals, and the integration of Tailwind CSS with PostCSS. It further supports managing global typography, theme state persistence, and secure lazy-loaded routing with role-based guards.
Which engineering personas benefit from these Angular configurations?▼
Frontend engineers and technical leads focused on maintaining consistent design systems and scalable architecture benefit from these configurations. It is specifically designed for developers building enterprise-grade web interfaces who require standardized directory structures, dependency injection patterns, and efficient global style management.
What are the prerequisites for implementing these Angular patterns?▼
Implementation requires an existing Angular environment and familiarity with the framework's dependency injection system. Users must have a project configured with PostCSS for Tailwind integration and be prepared to map backend endpoints to the provided client structure within the project's directory hierarchy.