Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Web Interface Guidelines Compliance Reviewer

agent coding skill risk: low

Web Interface Guidelines Compliance Reviewer

Fetches the latest web interface guidelines from a GitHub URL, reads specified files or prompts for them, checks compliance with all rules, and outputs findings in terse file:line…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: antigravity-awesome-skills-web-design-guidelines
description: "Review files for compliance with Web Interface Guidelines."
---
# Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

## How It Works

1. Fetch the latest guidelines from the source URL below
2. Read the specified files (or prompt user for files/pattern)
3. Check against all rules in the fetched guidelines
4. Output findings in the terse `file:line` format

## Guidelines Source

Fetch fresh guidelines before each review:

```
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
```

Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.

## Usage

When a user provides a file or pattern argument:
1. Fetch guidelines from the source URL above
2. Read the specified files
3. Apply all rules from the fetched guidelines
4. Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

REQUIRED CONTEXT

  • file or pattern argument

TOOLS REQUIRED

  • web_fetch

ROLES & RULES

  1. Use this skill only when the task clearly matches the scope described above.
  2. Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  3. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

EXPECTED OUTPUT

Format
plain_text
Schema
text_format
Constraints
  • terse file:line format
  • use format specified in fetched guidelines

SUCCESS CRITERIA

  • Review files for compliance with Web Interface Guidelines.
  • Output findings in the terse file:line format

FAILURE MODES

  • May be used outside its intended scope.
  • Output may not substitute for validation or testing.

CAVEATS

Dependencies
  • Requires fetching guidelines from https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
  • Requires user-provided file or pattern argument (or prompts for it)
Missing context
  • Explicit definition of the expected output format instead of deferring entirely to fetched content.
  • Examples of valid file/pattern inputs.
Ambiguities
  • Output format described as both 'terse `file:line` format' and 'format specified in the guidelines' without clarifying precedence.
  • Name 'antigravity-awesome-skills-web-design-guidelines' does not clearly relate to the described task.

QUALITY

OVERALL
0.71
CLARITY
0.78
SPECIFICITY
0.72
REUSABILITY
0.68
COMPLETENESS
0.65

IMPROVEMENT SUGGESTIONS

  • Replace the generic 'When to Use' and 'Limitations' sections with task-specific constraints.
  • Embed or summarize the key rules from the guidelines source so the prompt is self-contained for review.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT