Scope
A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.
npx -y skills add bromso/metapowers --skill scopeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Define the scope and plan for an accessibility audit
SKILL.md
1.6 KB, as published. Nobody here has run it
Scope
Define the accessibility audit scope for "$ARGUMENTS". Determine what to test, which WCAG level to target, and what pages or features to include.
Prerequisites
None — this is the first phase.
Process
-
Understand the audit target:
- What is "$ARGUMENTS"? A website, app, component, feature, or page?
- Ask the user to clarify if ambiguous
-
Define the scope:
- Which pages or features to test (sample representative pages)
- Which WCAG level to target (A, AA, or AAA — recommend AA as baseline)
- Any specific compliance requirements (Section 508, EN 301 549, EAA)
- Any known accessibility concerns to prioritize
-
Identify testing approach:
- Automated testing: code analysis, ARIA validation, contrast checks
- Manual testing: keyboard navigation, screen reader flow, focus management
- Content review: alt text quality, heading structure, link text
-
Write the artifact to
.metapowers/accessibility/$ARGUMENTS/01-scope.mdwith sections:- Target — what's being audited
- WCAG Level — target conformance level
- Pages/Features — specific items to test
- Compliance Requirements — applicable standards
- Testing Methods — automated + manual approach
- Known Concerns — pre-existing issues to prioritize
Output
The audit scope written to .metapowers/accessibility/$ARGUMENTS/01-scope.md. Present a summary to the user highlighting:
- Scope boundaries
- Target WCAG level
- Testing approach