geovendas360

Centralizes CRM360 architecture documentation for cross-stack development and onboarding.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill geovendas360
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geovendas360
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/geo-360/skills/geovendas360
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill geovendas360

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CRM360 teams often rely on dispersed architectural docs across multiple projects and stacks; this Skill consolidates the CRM360 architecture into a single, navigable knowledge base to speed onboarding and ensure consistency.

Core Features & Use Cases

  • Centralized architecture map covering CRM360 workspace including geovendas-vue, geovendas-vaadin23, geochat-api, geovendas-dotnet/Comm, and Evolution API.
  • Cross-stack guidance for backend Java, frontend Vue/Vaadin, .NET middleware, and Node.js services.
  • Onboarding and product reviews: quick access to project references, integration points, and tech stacks to accelerate new teammate ramp-up.

Quick Start

Browse the CRM360 workspace overview and open the referenced projects to get oriented.

Frequently Asked Questions about geovendas360

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize CRM architecture documentation for cross-stack projects?

Centralize CRM architecture documentation by loading a knowledge base that enforces YAML frontmatter and Markdown structured sections, consolidating cross-stack system onboarding and architectural references into a single navigable workspace.

What is the best way to speed up developer onboarding across Java and Vue CRM projects?

Speed up developer onboarding by accessing a centralized architecture map that covers CRM workspace projects, cross-stack guidance, and integration points to accelerate new teammate ramp-up and reduce misalignment.

How does architectural review work for systems spanning .NET, Node.js, and Vaadin stacks?

Architectural reviews for cross-stack CRM development apply a structured knowledge base that provides backend, frontend, and middleware guidance to ensure consistency and reduce onboarding time across diverse tech stacks.

Does this architectural knowledge base support integration points for geochat-api and Evolution API?

Yes, the architectural knowledge base supports CRM360 workspace projects including geochat-api and Evolution API, providing quick access to project references, integration points, and tech stacks for product reviews.

Can I browse the CRM360 workspace overview to get oriented across multiple tech stacks?

Yes, you can browse the CRM360 workspace overview covering geovendas-vue, geovendas-vaadin23, geochat-api, and geovendas-dotnet to get oriented and open referenced projects for cross-stack development.

Why do I need YAML frontmatter and Markdown body structure for CRM architectural documentation?

YAML frontmatter with name and description and a Markdown body with structured sections are required to standardize CRM architectural documentation, ensuring consistent loading into context and reducing misalignment across cross-stack teams.