Content Designer · 2026 · Skylight

AI-assisted build

I co-created a design system file that guides Claude, then used it to build and iterate on a federal migration site for 12 divisions.

The problem

The federal client needed to share frequent updates on a process migration project, but its web publishing model was too slow. Divisions didn't know the project's status or their next steps.

What I did

I proposed a new site, owned by Skylight, so we could control the publishing schedule. Sharing updates through the federal publishing team couldn't keep pace with the project, so stakeholders immediately chose a Skylight-owned site.

To build it quickly, I worked with a UX designer and a developer on a design system file based on the United States Web Design System (USWDS), so the site would match the federal branding the client's employees expect. I added content standards for capitalization, grammar, voice and tone, and accessibility, such as never using all caps and keeping a helpful, plain-language tone. The goal was for Claude to apply the same standards to every page. I also worked with engineering to adopt CI/CD, which let us release updates every two weeks.

Using a Claude-assisted workflow in GitHub, I built the site myself and iterated on it by incorporating feedback from Skylight and federal stakeholders and by correcting mistakes Claude made.

For example, federal stakeholders wanted to see all updates and artifacts on one page, so I merged the Artifacts and Updates pages into a single Roadmap page that shows linked artifacts as part of the project timeline. Claude mistakenly kept the original pages in the top navigation and linked to them, so I corrected the navigation and removed the old pages from the GitHub repo. Claude also forgot some of the content standards, often adding all caps eyebrow text above headings. I removed that text or, where it was useful, kept it with corrected capitalization.

Takeaway: The design system file set the UX standard, but it didn't guarantee compliance, so I reviewed each build against the design and content guidelines.

The outcome

Divisions stayed on track during the project phase that Skylight owned, with updates going out every two weeks, compared with every two months before. When the project moved to a new team, the site held all the information they needed, and served as the single source of truth.

The final site had 3 top-level topics and 9 project deliverables, each on its own page: