justice-league-factory

Methodology for analyzing factory telemetry and proposing evidence-based improvements. Query patterns, evidence standards, and risk classification. Injected into Oracle's context.

Shared architectural and engineering principles for planning, implementing, and reviewing code. Single source of truth for SOLID, 12-factor, DRY, KISS, and defensive design. Referenced by Martian Manhunter, Cyborg, and Wonder Woman.

Database migration and schema change standards for any project using raw SQL migrations. Activate whenever a task involves schema changes, column renames, field additions, table creation, data backfills, index creation, or any modification to how data is stored. Also activate when backend TypeScript interfaces need to reflect a new database shape.

Deep research methodology for refining abstract concepts into shippable product specs. Six phases: concept extraction, landscape survey, constraint discovery, shape definition, risk assessment, and output crystallization. Can be invoked directly by users or injected into Brainiac's context.

Documentation methodology. What to document, format templates, and accuracy-first principles. Injected into Lois Lane's context.

Comprehensive Playwright E2E regression testing methodology. Activate this skill when Flash needs to create a full regression test suite by auditing an entire codebase from scratch — not when testing specific acceptance criteria from a plan. That is testing-methodology's domain. This skill applies when the instruction is "regression test this application", "write a full E2E suite", or "test coverage from scratch". It covers codebase discovery, live app exploration via Playwright MCP tools, Page Object Model architecture, multi-viewport testing (375px / 768px / 1280px), measurable coverage thresholds, and output artifact production.

Orchestration playbook for the Justice League factory. Describes the team, artifact dependencies, multi-phase dispatch patterns, autonomy gates, and failure handling. Injected into Batman's context — not user-invocable.

Frontend styling, component structure, and UI consistency standards for any project. Activate whenever a task involves UI components, buttons, modals, forms, tabs, badges, inputs, color choices, inline styles, component organization, shared components, API types, file attachments, or any frontend code change. Also activate when a new backend field needs frontend consumption.

Standards for implementing code changes from a plan. Briefing format, verification steps, pattern-following guidance. Injected into Cyborg's context.

Decision frameworks for infrastructure choices: cost modeling, managed vs self-hosted, deployment topology, observability, reliability, security posture, and vendor lock-in. Teaches agents HOW to evaluate infrastructure decisions, not WHAT to choose. Vendor-agnostic.

Methodology for decomposing features into implementation plans. How to write acceptance criteria, assess parallelizability, and structure architecture documents. Injected into Martian Manhunter's context.

User-centric reasoning for research and planning. User journey mapping, edge case enumeration, notification flows, and outcome framing. Injected into Brainiac and Martian Manhunter to ensure features are designed for real users, not just technical correctness.

Code review methodology. Severity classification, plan compliance checklist, architectural principles compliance, definition-of-done verification, and test coverage matrix checks. Injected into Wonder Woman's context.

Security review methodology using OWASP Top 10 and STRIDE frameworks. Reference material for scanning code changes for vulnerabilities. Injected into Green Lantern's context.

Guidance for planning the creation of new skills and agents. Covers delivery vehicle decisions (skill vs agent vs both), validation strategy, integration checklists, and coordination with skill-creator. Load when the feature request involves creating a new skill or agent.

Methodology for evaluating skill quality at creation and modification time. Content quality rubric, cross-skill coherence analysis, and token efficiency assessment. Complements improvement-methodology: this skill evaluates craft, improvement-methodology evaluates effectiveness from telemetry.

Testing methodology for writing tests against plan acceptance criteria, user journeys, and edge cases. Framework detection, coverage hierarchy, coverage matrix output, and test quality guidance. Injected into Flash's context.