Buscar habilidades.../

Teco Main Map Workflow | Skills Pool

Archivo del skill

Teco Main Map Workflow

Build and evolve TECO main map page using Feature-First + Clean Architecture. Use for map UI work, open requests integration, strict RPC list_requests_with_geojson consumption, GeoJSON lon/lat parsing, 25km filtering, and flutter analyze/test validation.

CaioMtho0 estrellas6 abr 2026

Ocupación
Categorías: Depuración

Contenido de la habilidad

Scope

Map area only. This skill covers the TECO main map page and its direct request-map integration workflow.

Outcome

Deliver a working map-page iteration that preserves:

Feature-First + Clean Architecture layout.
Material-based top and bottom shell components.
Strict open-request ingestion from RPC plus GeoJSON parsing.
25km business rule enforcement and project validation gates.

When To Use

Use this skill when you need to:

Create or refactor the main map page.
Integrate open requests into map markers.
Parse GeoJSON location payloads from RPC responses.
Enforce request-radius filtering around the main user point.

Required Inputs

Iteration objective (UI shell, data, refactor, validation).
Confirmed backend contract for current RPC payload.

Skills relacionados

Instalación rápida

Teco Main Map Workflow

npx skills add CaioMtho/teco-app

Descargar Skill Abrir repositorio

Autor: CaioMtho
estrellas: 0
Actualizado: 6 abr 2026
Ocupación

En esta página

Confirmation that RPC name is list_requests_with_geojson (or explicitly updated contract).

Workflow

Confirm iteration scope is map-only.
Confirm contract before coding:
- Source: RPC list_requests_with_geojson.
- Required fields per row: id, title, status, location_geojson.
- GeoJSON Point coordinates format: [lon, lat].
Map target files and keep boundaries clean:
- lib/app.dart
- lib/main.dart
- lib/features/requests/data/...
- lib/features/requests/domain/...
- lib/features/requests/presentation/...
Implement data-layer changes with strict parsing:
- Call RPC explicitly.
- Parse latitude/longitude from GeoJSON coordinates.
- Throw a clear error for invalid or missing location payload.
Implement business rules:
- Keep only open requests.
- Keep only requests within 25km radius from main point.
Implement/adjust presentation:
- Render flutter_map markers for user point and requests.
- Keep Material top/bottom bars as requested (no scope creep).
Run quality checks:
- flutter analyze
- flutter test
- Manual map sanity check (centering, markers, radius behavior).
Summarize change delta:
- Files touched.
- Contract assumptions.
- Remaining follow-up items.

Branching Rules

If RPC/schema contract changed or is uncertain:
- Stop implementation and request explicit contract alignment.
- Do not add schema heuristics or alternate field fallbacks.
If device location is unavailable:
- Use the project-defined fallback location.
If request is UI-only:
- Do not add navigation/auth/domain extensions unless explicitly requested.

Quality Gate (Definition Of Done)

Architecture remains in features/requests with clear data/domain/presentation split.
No heuristics for schema fields or status mapping.
GeoJSON parsing uses [lon, lat] correctly.
25km filter rule is applied.
flutter analyze reports no issues.
flutter test passes.

Common Pitfalls

Reversing latitude/longitude from GeoJSON coordinates.
Leaking data logic into presentation widgets.
Reintroducing schema fallback logic after contract mismatch.
Expanding scope beyond map area tasks.

Example Prompts

/teco-main-map-workflow Integrate map markers from list_requests_with_geojson using strict GeoJSON parsing.
/teco-main-map-workflow Refactor map page while preserving open-only and 25km filtering rules.
/teco-main-map-workflow Update top and bottom Material bars without touching data contract logic.

02

Outcome

04Required Inputs

06Branching Rules

07Quality Gate (Definition Of Done)

08Common Pitfalls

09Example Prompts

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.