BCDev Fullstack Skill Pack

---
name: bcdev-fullstack
description: Work on the BC development workspace at D:\bcdev, including the Go backend in D:\bcdev\backend and the Flutter frontends in D:\bcdev\frontend\bcaiaccount and D:\bcdev\frontend\bclms. Use when an AI agent must inspect architecture, trace API-to-UI flow, add or fix features, update MCP tools, or coordinate backend and frontend changes in this codebase.
---

# BCDev Fullstack

Use this skill when working inside the BC development workspace.

## Load the right reference first

- Read `references/backend.md` before changing Go services, Echo routes, MCP tools, Docker stack, `bootstrap.json`, or database integrations.
- Read `references/frontend.md` before changing Flutter screens, blocs, repositories, flavors, `web/config.json`, or deploy scripts.
- Read both reference files when a task crosses API, model, or response boundaries.

## Workspace map

- Backend: `D:\bcdev\backend`
- Frontend app 1: `D:\bcdev\frontend\bcaiaccount`
- Frontend app 2: `D:\bcdev\frontend\bclms`

## Core rules

- Treat backend contracts as the source of truth for request and response shapes plus business rules.
- Prefer MCP-based discovery when it is available, then inspect source code when MCP is insufficient.
- Never expose or copy secrets from `bootstrap.json` into code, docs, tests, prompts, or frontend bundles.
- Keep backend configuration centered on `bootstrap.json`; do not add new `.env`-style flows unless the target already uses them.
- Keep frontend network calls inside repository or service layers instead of UI widgets.
- Do not call external AI provider endpoints directly from Flutter code. Route AI features through backend endpoints.
- When renaming or removing a shared field, update backend code and every affected Dart model, repository, bloc or provider, and screen in the same change.

## Task recipes

### Backend-only task

1. Find the entrypoint, handler, or domain package first.
2. Trace route to handler to service to repository or model.
3. If the feature affects analytics, AI tools, or schema discovery, inspect `internal/goapi/mcp`.
4. Verify config, ports, and runtime assumptions against `references/backend.md`.

### Frontend-only task

1. Find the screen, route, or page that renders the feature first.
2. Trace screen or widget to bloc or provider to repository or service to model.
3. Confirm backend response fields before editing parsing, UI assumptions, or filters.
4. Verify flavor and environment behavior before testing.

### Cross-project task

1. Confirm the backend endpoint, payload, and response shape first.
2. Update backend and frontend in one pass when changing shared fields.
3. Keep wire formats backward compatible whenever possible.
4. Check both frontend apps if the feature can affect accounting UI and logistics UI separately.

## Key starting points

- Backend gateway entrypoint: `D:\bcdev\backend\main.go`
- Standalone GoAPI entrypoint: `D:\bcdev\backend\cmd\goapi\main.go`
- Flutter bootstrap: `D:\bcdev\frontend\bcaiaccount\lib\main.dart`
- Flutter root app: `D:\bcdev\frontend\bcaiaccount\lib\main_app.dart`
- Riverpod app bootstrap: `D:\bcdev\frontend\bclms\lib\main.dart`

## Output expectations

- Keep fixes scoped to the smallest layer that solves the problem.
- Preserve Thai business terminology already used in logs, labels, and comments.
- Prefer concrete file edits over high-level suggestions when the task is implementation-oriented.
- Mention assumptions explicitly when the code path is ambiguous between `bcaiaccount`, `bclms`, `mainapi`, and `goapi`.