How do I install the Delaware Lighthouse skill?

Run npx skillmds@latest add blencorp/delaware-lighthouse in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Delaware Lighthouse safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Delaware Lighthouse?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Delaware Lighthouse free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Delaware Lighthouse?

blencorp (@blencorp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Delaware Lighthouse by blencorp — Agent Skill

Name: Delaware Lighthouse
Author: blencorp

Delaware Lighthouse

Builds Delaware agency websites from the official Lighthouse versioned CDN stylesheets and scripts, HTML components, WordPress-oriented templates, colors, and accessibility guidance. Use for Delaware state and agency sites; load the state-hosted CDN assets, since no npm package is published.

blencorp 3413780 4 files · 6.2 KB Updated Sep 17, 2026

File contents

Delaware Lighthouse Design System

Before editing

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

Workflow

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

Boundaries

Scope: Delaware agency websites, particularly GIC-supported and WordPress implementations.
Delivery: State-hosted versioned CDN CSS/JS with a Bootstrap dependency, copy-ready HTML components, WordPress-oriented templates, downloadable assets, and official documentation.
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
Sources

---name: delaware-lighthousedescription: Builds Delaware agency websites from the official Lighthouse versioned CDN stylesheets and scripts, HTML components, WordPress-oriented templates, colors, and accessibility guidance. Use for Delaware state and agency sites; load the state-hosted CDN assets, since no npm package is published.---# Delaware Lighthouse Design System## Before editing1. 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.## Workflow1. 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:** Delaware agency websites, particularly GIC-supported and WordPress implementations.- **Delivery:** State-hosted versioned CDN CSS/JS with a Bootstrap dependency, copy-ready HTML components, WordPress-oriented templates, downloadable assets, and official documentation.- 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)

Frequently asked questions