etendosoftware

Use when creating or modifying overview/dashboard pages, adding KPIs, kanban boards, alert panels, or activity feeds to module landing pages. Triggers - aggregate-contract.json, overview page, module dashboard, KPI header data.

Use when classifying schema fields or business rules for a window. Triggers on classify window, classify fields, classify rules, curate schema, curate rules, pre-classify. AI-guided replacement for manual Decision Panel.

Use when auditing Schema Forge for architecture drift, duplicated window logic, cross-window dependencies, shared code in concrete windows, selector repetition, related-document duplication, or generic components containing window-specific fixes.

Use when working with Schema Forge windows — generating, regenerating, or modifying frontend/backend code from schemas and contracts. Triggers: "regenerate window", "update schema", "generate frontend", "run pipeline", "contract.json", "schema-curated", working in artifacts/ directory.

Report a bug in the Schema Forge tooling. Use this skill when something is broken in the tool itself — CLI generators, frontend components, pipeline steps, NEO Headless integration — regardless of which window is being worked on. Do NOT use for window classification decisions (which fields to show, which rules to keep). Triggers on: "bug", "broken", "no funciona", "roto", "error en el pipeline", "siempre pasa en todas las ventanas".

Use when closing, preparing, reviewing, or documenting a development task, PR, delivery, bugfix, refactor, regression fix, functional change, test evidence, QA validation, or when asked if a task is done.

Audit Schema Forge for architecture drift, duplicated window logic, cross-window dependencies, generic components leaking window-specific fixes, selector/related-document repetition, AND propose grounded refactors. Triggers on architecture audit, duplicated code, código repetido, duplicado, dedupe, DRY, complejidad cognitiva, cross-window imports, generic leak, refactor, selector repetition, related documents duplication.

Use when closing, preparing, reviewing, or documenting a development task, PR, delivery, bugfix, refactor, regression fix, functional change, test evidence, QA validation, or when asked if a task is done.

Plan and estimate a development task using an additive, component-based point system (Fibonacci base points per item type + risk factors). Produces a decomposed estimate, an hours range, a t-shirt size, and a list of the difficulties/risks that drive the cost. Also runs calibration: comparing an estimate against the real worklogs once a task is done, and proposing tweaks to the points table. Use when the user wants to estimate, plan, size, or score a task, asks "how long will this take", "cuánto va a costar", "estimemos esto", "puntuá esta tarea", "planificación", or wants to review why a task overran its estimate.

Verify that pending changes are behavior-preserving (innocuous) — that a refactor does NOT alter observable functionality. Use after refactoring to lower cognitive complexity, resolve SonarQube issues, rename, extract/inline functions, or apply guard clauses. Analyzes the diff hunk by hunk for behavior-changing edits, flags poor function names (generic auto-extract names, placeholders), then runs the affected tests. Optionally (opt-in) places START/END extraction markers in a too-complex function or .jsx component to plan a behavior-preserving extract-method/extract-component refactor. Triggers on: "is this safe", "inocuo", "inocuidad", "refactor", "bad function names", "did I break anything", "behavior preserving", "Sonar fix", "bajar complejidad cognitiva", "check my changes", "verify diff", "marca start/end", "marcadores para extraer", "comentarios para extraer", "extract markers", "ayudame a extraer", "WebStorm extract".

Import the latest local Claude Code session for the current project into the current OpenCode conversation.

Import a specific local Claude Code session by session ID into the current OpenCode conversation.

Create a Fyso agent team from natural language requirements. Diseña y despliega equipos de agentes IA en Fyso. Keywords: crear equipo, create team, nuevo equipo, agentes fyso, deploy agents, equipo de agentes, team setup.