Agent Skills: bbl-senior-fullstack

Use for coordinated THB-BBL cross-layer work spanning UI, API routes, services/data, and optional legacy Python parity when shared contracts or data flow can drift. Do not use for docs-only work, pure UI polish, or low-risk isolated fixes.

UncategorizedID: therealityreport/THB-BBL/bbl-senior-fullstack

Install this agent skill to your local

pnpm dlx add-skill https://github.com/therealityreport/THB-BBL/tree/HEAD/skills/bbl-senior-fullstack

Skill Files

Browse the full folder contents for bbl-senior-fullstack.

Download Skill

Loading file tree…

skills/bbl-senior-fullstack/SKILL.md

Skill Metadata

Name
bbl-senior-fullstack
Description
Use for coordinated THB-BBL cross-layer work spanning UI, API routes, services/data, and optional legacy Python parity when shared contracts or data flow can drift. Do not use for docs-only work, pure UI polish, or low-risk isolated fixes.

Use this skill when THB-BBL changes cross UI/API/data boundaries and require coordinated sequencing.

When to use

  1. Work spans src/app/**, src/components/**, src/app/api/**/route.ts, and src/server/services/** in one change stream.
  2. API contract, schema (prisma/schema.prisma), serialization, or pipeline semantics can change.
  3. Backend and UI must be updated together to prevent drift.
  4. Legacy Python parity in backend/** may need verification or follow-up.

When not to use

  1. Docs-only tasks.
  2. UI-only tasks with no backend contract risk.
  3. Backend-only low-risk tasks with no downstream impact.
  4. Trivial read-only requests.

Preflight

  1. Read touched repo guidance (agents.md and relevant docs).
  2. Confirm impacted contracts and consumer surfaces inside THB-BBL.
  3. Identify any TS/Python duplicated logic requiring parity checks.
  4. Establish rollout order and rollback boundaries.

Stop condition: if contract surface is unclear, stop and resolve before coding.

Execution checklist

  1. Build an impact matrix: schema/contracts, API/services, UI consumption, and parity dependencies.
  2. Execute in THB-BBL order: schema/contracts first, API/service implementation second, UI consumption third, end-to-end verification last.
  3. Coordinate backend semantics and compatibility explicitly.
  4. Coordinate frontend UX and state handling explicitly.
  5. Run validations: npm run lint, npm run typecheck, npm run test, and python3 -m pytest backend/tests when backend/** changes.
  6. Record deferred parity or migration follow-ups with owners.

Fallbacks

  1. If work resolves backend-only, route primary ownership to bbl-senior-backend.
  2. If work resolves UI-only, route primary ownership to bbl-senior-frontend.
  3. If partial rollout is requested, record deferred updates and explicit risk.

Completion contract

Return:

  1. scope_statement
  2. impacted_layers
  3. contract_surfaces
  4. schema_impact
  5. parity_dependencies
  6. files_changed
  7. validations_run
  8. blocked_checks
  9. residual_risks
  10. rollback_notes
  11. handoff_dependencies