Baelfyre

Cross-specialist coordination specialist for contract assembly, contradiction detection, semantic invalidation, and re-entry recommendations.

Workflow continuity, validation, and transition governance specialist. See SKILL_INDEX.md.

Routing and orchestration layer. Chooses the smallest effective skill stack. See ROUTING_MAP.md and SKILL_INDEX.md for detailed routing behavior.

QA, Test Strategy, Validation, CI, and Release Readiness Specialist. See SKILL_INDEX.md.

Implementation and Navigation Specialist. Owns minimal safe edits. See SKILL_INDEX.md.

Workflow continuity, validation, and transition governance specialist. See SKILL_INDEX.md.

Routing and orchestration layer. Chooses the smallest effective skill stack. See ROUTING_MAP.md and SKILL_INDEX.md for detailed routing behavior.

QA, Test Strategy, Validation, CI, and Release Readiness Specialist. See SKILL_INDEX.md.

Use only when the user explicitly requests controlled destructive testing, negative testing, fuzz testing, adversarial QA, boundary or failure-mode testing, guardrail or crash testing, invalid-input testing, database constraint stress testing, resilience testing, or pre-production pressure testing. Do not invoke automatically. Operate only on authorized, non-production systems with a completed safety gate and explicit approval for risky execution.

Amalgam Conductor is the routing and orchestration layer of the Amalgamatic Orchestra. Use it for project orientation, multi-skill routing, workflow planning, readiness reviews, or deciding which specialist should handle UI/UX, documentation, diagrams, databases, QA, security/privacy, or gated resilience testing. It chooses the smallest effective skill stack, sequences work by dependency, controls token usage, prevents duplicate reviews, and protects projects from unnecessary or risky actions.

The Clockwork Meister guards the moving framework of the codebase: OOP discipline, architecture layering, service/repository boundaries, dependency flow, transaction safety, and structural refactor integrity.

Review quality assurance, test strategy and plans, test cases, acceptance criteria, requirements testability, unit/integration/system/user-acceptance testing, smoke and regression planning, defect triage, verification and validation evidence, CI test workflows, quality gates, release readiness, and quality documentation. Use when project quality or readiness must be assessed from available evidence.

Perform defensive, evidence-based security and privacy review, documentation, evidence synthesis, threat review, and remediation planning. Use when the user asks about application or API security, privacy, data protection, authentication, authorization, RBAC, sessions, secrets, sensitive-data handling, classification, minimization, retention, logging, dependencies, supply chain, secure SDLC, privacy risk, or security/privacy documentation gaps. Do not use for offensive or destructive testing.

Review and improve the visible and experiential layer of software systems, including UI, UX, accessibility, visual hierarchy, frontend architecture, dashboards, JavaFX screens, React/HTML/CSS components, design systems, responsive layouts, user flows, information architecture, interaction design, forms, component consistency, and frontend implementation guidance. Use for evidence-based interface audits and practical visible-layer improvements.

Review, document, and improve database architecture, schemas, ERDs, tables, columns, keys, constraints, indexes, normalization, reference and seed data, migrations, stored procedures, views, audit tables, reporting tables, SQL, data dictionaries, integration documentation, and database testing plans. Use when database facts must be validated against schema, migration, dump, live metadata, or project requirements.

Create, review, correct, and document UML class, use case, sequence, activity, state, component, deployment, ERD, database relationship, system architecture, layered architecture, data-flow, workflow, process, user-flow, and feature-interaction diagrams. Use when a diagram must accurately reflect project objectives, system behavior, data relationships, implementation boundaries, or supplied source evidence.