RampStack Claude Skills

Install

/plugin marketplace add rampstackco/claude-skills
/plugin install rampstack-skills@rampstack

This is third-party code. Review the repository files before installing.

What it does

Every skill follows one structure: when to use it, when not to and which sibling to pick instead, required inputs, a working framework, and reference files with templates and checklists. Sections cover brand strategy and identity, design systems, content, SEO, product management and experiments, frontend and accessibility, launch and incidents, and UX research. Skills reference each other, for example creative-brief builds on brand-voice. The SEO audit suite assumes a connected Ahrefs MCP; the rest are stack-agnostic.

Who it is for. For web studios, marketers and product teams running a site from brand to growth.

Example request

Run a WCAG accessibility audit of the home page and write a remediation plan

Limitations

Skills provide methods and templates, not data. The SEO audit suite needs a paid Ahrefs account and its MCP. The full catalog is large, so the authors offer focused subsets for SEO, product and a starter pack.

How to disable. Uninstall rampstack-skills or a subset via /plugin, or delete the skill folders from the agent's directory.

Security check

• The skills consist of instructions, templates and checklists

README in short

The README shows installation through the Claude Code marketplace with the full catalog and three focused plugins. It describes the library principles: uniform structure, stack independence and cross-references. There is a showcase of creative-direction and logo-design output on the authors' site, a list of recommended MCP servers and authoring conventions. MIT licensed.

SKILL.md

---
name: accessibility-audit
description: "Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation."
category: development
catalog_summary: "WCAG compliance audit with remediation plan"
display_order: 3
---

# Accessibility Audit

Run a thorough accessibility audit and produce a remediation plan. Stack-agnostic. Anchored to WCAG 2.1 AA, with notes on AAA where relevant.

This skill goes deeper than the accessibility checks in `qa-testing` and `design-standards`. Use this when accessibility itself is the goal.

---

## When to use

- Pre-launch accessibility verification
- Compliance preparation (ADA, EN 301 549, AODA, Section 508)
- Remediation after an audit finding or complaint
- Annual or quarterly accessibility health check
- Onboarding accessibility into a team that hasn't prioritized it before

## When NOT to use

- General QA after deploys (use `qa-testing`)
- Component-level accessibility implementation (use `frontend-component-build`)
- Color contrast for design tokens (use `design-standards` or `brand-identity`)

---

## Required inputs

- The site or product under audit
- The scope (full site, specific section, specific user flow)
- The target standard (WCAG 2.1 AA is most common)
- Any specific concerns or known issues
- Tools available (automated scanners, screen readers, manual testing)

Related