Files

Cassel 647cbec54f docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-19 13:29:03 -04:00

2.2 KiB

Raw Permalink Blame History

name, description

name	description
workflow-design-system	Define, update, and review design system components used across page specifications.

[M] Manage Design System — Define and Update Components

Goal: Define, update, and review design system components used across page specifications.

When to use: When the user needs to create new components, update existing ones, or review the design system for consistency.

INITIALIZATION

Read design log at {output_folder}/_progress/00-design-log.md before starting.

Extraction Rules

Not everything extracts at the same time:

Objects: Extract on Second Use

The first time a button, card, or widget appears, it stays inline in the page spec — it's a one-off. The second time the same pattern appears (same states, same behavior), it's a real pattern. Extract it to the design system.

First use = one-off. Second use = pattern. Extract.

Spacing: Extract Immediately on First Use

Spacing extracts on first use — no waiting for a second occurrence. Spacing is relational: when you decide that a heading needs space-xl above a card grid, that's a universal design principle, not a page-specific detail.

Component Extraction Check

Before designing the 2nd+ page, scan completed specs for shared elements. If found, suggest extraction. Don't block the flow — the user can defer.

Entry

Load design system from {output_folder}/D-Design-System/ (if exists).

Steps

Execute steps in ./steps-m/:

Step	File	Purpose
01	step-01-review-current.md	Review existing design system state
02	step-02-define-component.md	Define or update a component
03	step-03-validate-usage.md	Check component usage across specs

Reference data:

./data/object-types/ — component type definitions and templates
./data/modular-architecture/ — three-tier architecture guide
./data/guides/TRANSLATION-ORGANIZATION-GUIDE.md — content organization

AFTER COMPLETION

Append a progress entry to {output_folder}/_progress/00-design-log.md under ## Progress: ### [date] — Design System: [components extracted/updated]
Suggest next action based on the adaptive dashboard

2.2 KiB Raw Permalink Blame History