agentsclimarketplace
Sign in

Reviewer

Skill suntay44/buildable-plugin-skills/skills/reviewer

Review a Buildable prototype against its app spec and quality rubric for build correctness, workflow completeness, state coverage, accessibility, responsiveness, and local-first discipline. Do not use for ordinary code review, pull-request review, or unrelated repository audits.From its SKILL.md

Install
npx -y skills add suntay44/buildable-plugin-skills --skill reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.2 KB, as published. Nobody here has run it

Buildable Reviewer Skill

Use this skill to review generated prototypes against the app spec and quality rubric.

Resolve all referenced paths from the Buildable plugin or repository root.

buildable review is a static/local quality gate. Treat it as a strong first pass for structure, local-first guardrails, source coverage, responsive-layout risk, accessibility signals, and optional build checks; it does not replace manual QA, real device/simulator checks for mobile, or browser/screenshot review when visuals matter.

Reference Loading Contract

Mandatory order:

  1. Run buildable review from the selected app workspace when available. Pass a path only when reviewing a different folder.
  2. Load the app spec and selected rubric.
  3. Load only files related to reported issues.
  4. Do not load all templates.
  5. Do not load unrelated archetypes or starter source.

Workflow

  1. Run buildable review when the CLI is available. Add --build only when the user wants typecheck/build scripts run and dependencies are installed.
  2. Read the app spec and selected quality rubric.
  3. Run available build, typecheck, lint, or test commands (or rely on review --build).
  4. Inspect the generated UI when possible — start the app and run buildable preview --url <url> from the app workspace to render it, screenshot it, and catch runtime/visual errors that build checks miss.
  5. Check required interactions, state coverage, responsive behavior, and accessibility.
  6. Produce a focused fix list.
  7. Apply fixes when operating as the active coding agent.

Review Priorities

  • build correctness
  • primary workflow
  • missing interactions
  • empty/loading/error states
  • mobile and desktop layout
  • accessible form controls
  • unnecessary backend or hosted features

Output Format

Lead with blocking issues, then polish issues, then checks run. If no issues remain, say so and note residual risks.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.