# EraAI Developer Skills

Complete portable bundle for the Developer Hub skill catalog.

---

# Brandbook Steward

## Purpose

Keep visual identity, component language, product marks, and the live Brandbook aligned with
implemented UI.

## Run when

Run when a shared visual decision, mark, shell pattern, or component treatment changes.

## Procedure

1. Inspect the implementation and identify the reusable visual decision.
2. Update the canonical Brandbook rule without duplicating product behavior requirements.
3. Update the live Brandbook specimen when the decision needs visual demonstration.
4. Add a concise Brandbook changelog entry.
5. Check that product-specific styling still conforms without flattening specialized workflows.

## Required outputs

- Canonical Brandbook update
- Live specimen update when applicable
- Change record

---

# Developer Hub Curator

## Purpose

Maintain the three-level information architecture, page maturity, navigation marks, route ownership,
and canonical references.

## Run when

Run when a Dev Hub page, route, label, content status, or navigation group changes.

## Procedure

1. Inventory active, external, planned, and removed destinations.
2. Keep planned destinations visible but disabled and free of redirect links.
3. Assign a distinct mark to every active non-product destination and reuse established product
   marks.
4. Update navigation documentation and route references.
5. Verify active links, disabled semantics, mobile scrolling, theme behavior, and route status.

## Required outputs

- Updated navigation
- Accurate maturity states
- Route and documentation alignment

---

# Product Vision Sync

## Purpose

Keep suite positioning, product narratives, architecture concepts, and work stories coherent after
strategy changes.

## Run when

Run after changes to product scope, positioning, audience, capabilities, or suite relationships.

## Procedure

1. Identify every product and narrative affected by the change.
2. Update suite vision, dedicated product pages, work stories, and architecture only where relevant.
3. Preserve explicit maturity boundaries between vision and implemented capability.
4. Check previous and next product relationships and navigation labels.
5. Record the update in Developer Hub documentation.

## Required outputs

- Synchronized product narratives
- Updated maturity boundaries
- Developer Hub change record

---

# Production Delivery Verification

## Purpose

Prove requested routes render correctly, remain intentionally static or dynamic, and survive
production packaging.

## Run when

Run before completing frontend delivery or when routing, rendering, or deployment behavior changes.

## Procedure

1. Preview every requested route and repair current runtime or build failures.
2. Run the repository-prescribed production verification command.
3. Inspect the complete production route table and confirm fixed pages remain static.
4. Visit every generated public route and record non-success responses.
5. Verify relevant responsive states, console errors, images, and interactions.

## Required outputs

- Production verification result
- Route classification
- Public route coverage

---

# Rebuild All

## Purpose

Run a complete Developer Hub resynchronization after cross-cutting project work and invoke every
relevant specialist skill.

## Run when

Run after several related changes, before a major review, or whenever Developer Hub references may
have drifted.

## Procedure

1. Inspect project and Developer Hub changes since the last synchronized state.
2. Map each changed area to affected references, routes, marks, requirements, and delivery checks.
3. Invoke every relevant specialist skill; do not run unrelated rewrites.
4. Run Brandbook Steward, Requirements Sync, Developer Hub Curator, and Skill Catalog Curator when
   their sources changed.
5. Resolve contradictions, regenerate downloads, and update all applicable changelogs.
6. Finish with Production Delivery Verification and report completed, skipped, and blocked skills.

## Can invoke

- UI Consistency Review
- Brandbook Steward
- Requirements Sync
- Product Vision Sync
- Developer Hub Curator
- Skill Catalog Curator
- Production Delivery Verification

## Required outputs

- Resynchronized Developer Hub
- Invocation report
- Updated references and downloads
- Delivery evidence

---

# Requirements Sync

## Purpose

Propagate major shared behavior, access, navigation, interaction, and delivery decisions into
canonical requirements.

## Run when

Run whenever a prompt introduces common behavior or a reusable functional contract.

## Procedure

1. Separate behavioral requirements from visual identity decisions.
2. Update the canonical requirements with implementation-aligned language.
3. Add the corresponding requirements changelog entry.
4. Cross-check affected routes and components for contradictions.
5. Link to the Brandbook or Developer Hub reference instead of copying their full content.

## Required outputs

- Requirements update
- Requirements changelog entry
- Cross-reference corrections

---

# Skill Catalog Curator

## Purpose

Reorganize the reusable skill catalog, explain changes, and keep view and download artifacts
synchronized.

## Run when

Run whenever a skill is added, revised, renamed, deprecated, or requested for reorganization.

## Procedure

1. Inventory every skill, its category, trigger, dependencies, outputs, and current maturity.
2. Merge duplicates and split overloaded skills only when responsibilities are materially distinct.
3. Update descriptions in plain operational language and preserve invocation relationships.
4. Regenerate individual download files and the complete skill bundle.
5. Update the Reusable Skills page, canonical skill documentation, and changelog.

## Can invoke

- Developer Hub Curator
- Requirements Sync when behavior changes

## Required outputs

- Reorganized catalog
- Skill update summary
- Synchronized download artifacts

---

# UI Consistency Review

## Purpose

Audit changed interfaces against EraAI’s common shell, typography, spacing, controls, states,
accessibility, responsive behavior, and visual language.

## Run when

Run after shared UI changes or when a product surface looks inconsistent.

## Procedure

1. Identify the changed surfaces, routes, breakpoints, and interaction states.
2. Compare them with Common UI Guidelines and the canonical Brandbook.
3. Check control alignment, focus visibility, icon treatment, dark mode, overflow, and reduced
   motion.
4. Fix root inconsistencies with existing tokens and components rather than page-specific patches.
5. Record any new reusable visual rule in the Brandbook and changelog.

## Required outputs

- Resolved UI inconsistencies
- Verification notes
- Brandbook update when required
