# Fec Pattern Library

> Maintains or extends FEC.gov interfaces with the official Federal Election Commission Pattern Library source and documentation. Use for FEC product work that already participates in the FEC CMS asset pipeline; do not treat it as a portable government-wide package.

- Skill: `blencorp/fec-pattern-library` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add blencorp/fec-pattern-library`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blencorp/fec-pattern-library/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: blencorp (https://skillmd.com/u/blencorp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/blencorp/fec-pattern-library

---


# FEC Pattern Library

## Before editing

1. Confirm the product is inside this system's scope.
2. Read [references/implementation.md](references/implementation.md) before installing, copying, or changing upstream assets.
3. Read [references/sources.md](references/sources.md) for provenance, version, and license.
4. Inspect and preserve the target project's framework, package manager, asset pipeline, and accessibility tests.

## Workflow

1. Choose one documented delivery path and pin an exact package, commit, release, or downloaded asset snapshot.
2. Use only official components, tokens, templates, and examples that are actually public.
3. Extend through documented mechanisms. Label every unsupported addition as custom.
4. Record the upstream version or commit and the accepted maturity/maintenance risk.
5. Test keyboard operation, focus, names/roles/states, errors, status messages, contrast, zoom/reflow, responsive behavior, and supported browsers.

## Boundaries

- **Scope:** FEC.gov and its coupled CMS/frontend environment.
- **Delivery:** Source repository and generated pattern library coupled to the FEC CMS assets.
- Do not invent a registry package, public repository, component API, or release commitment.
- Do not imply that a beta, hosted asset, code example, or product-specific repository is government-wide.
- Do not claim legal or WCAG conformance for the completed service solely from component use.
- If this system does not fit the product's requirements, route to the governing system or stop and explain the gap.

## References

- [Implementation](references/implementation.md)
- [Sources](references/sources.md)