Skip to content
cccskills
FreePublished on GitHubEnglish overview

agent-loops

Use `@solidjs/diagnostics` to capture evidence from Solid 2.0 scenarios. Check diagnostic findings, rerun and waste budgets, the visible response to user interactions, and server-render waits and calls, then compare captures after repairs.

OriginalShow the original description

Verify Solid 2.0 reactive code with evidence from @solidjs/diagnostics captureArtifact instead of reading it; generation, acceptance, attribution, responsiveness and server-render loops. Use when checking that generated or ported Solid code is quiet, within budget and re-runs only for the right reasons.

solidjs/solid36,427 stars(GitHub 36,427 + cccskills 0)
Works withPlaywright

Run score Not tested

See how to install

Good for

  • Checking generated or ported Solid code
  • Setting rerun and wasted-work limits
  • Finding why a scope reruns
  • Checking whether interactions acknowledge waits
  • Inspecting server-render waits and calls

Overview

What it does

Use captureArtifact from @solidjs/diagnostics to run Solid 2.0 scenarios and collect diagnostic and rerun records for checking code. The guide covers a repair loop that repeats until diagnostics are cleared, as well as acceptance checks with limits for reruns, wasted recomputations, and individual scopes. Attribution records help trace which change caused a rerun and which work took time. You can also check whether the screen shows a loading state while async work is pending after a user interaction. For server rendering, the captured records can show loading boundary waits and server function calls.

When it helps

Use these loops to verify generated code or code migrated from Solid 1.x against execution evidence. They are also useful when you want tests to enforce performance budgets, check whether the interface acknowledges a wait after a click, or look for repeated waits during server rendering.

Example requests

  • “Capture diagnostics for this interaction and check that reruns stay under two.”
  • “Check whether the screen shows a loading state while async work is pending after a click.”
  • “Use the capture to inspect waits and calls during server rendering.”

Notes

captureArtifact is used with a development build. Inspecting a live page in a browser requires additional setup, such as adding a bridge to the development entry point.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
BPartly lackingIt runs scenarios and captures records, but the scenario's effects are not bounded.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt requires `@solidjs/diagnostics` and a dev build; browser capture needs setup.

Not counted in the score. Rated by AI (OpenAI Codex) as of Nov 17, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md12.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use this guide to interpret Solid 2.0 diagnostic codes from warnings, test failures, or captured reports. It explains what each finding means and gives concrete repairs for tracking, writes, ownership, loading boundaries, and performance issues.

  • Fixing a Solid warning or test failure
  • Tracing a diagnostic code to its cause
  • Reducing unnecessary reactive work
solidjs/solid36.4KUpdated Nov 17, 2026

Use this guide to write or review Solid 2.0 server components that return templates. It explains where server markup belongs, how client components fill slots, and how to handle forms, event behavior, shared components, and compilation setup.

  • Writing a Solid server component
  • Deciding whether markup belongs on server or client
  • Passing client behavior through a slot
solidjs/solid36.4KUpdated Nov 17, 2026

solid-2.0

FreeSummary

Use this primer when writing, reviewing, or migrating Solid 2.0 code. It explains core API patterns, highlights differences from Solid 1.x and React, and shows the appropriate primitives for reactive values, effects, stores, async work, and UI boundaries.

  • Writing a new Solid 2.0 component
  • Reviewing unfamiliar Solid 2.0 code
  • Migrating a Solid 1.x project
solidjs/solid36.4KUpdated Nov 17, 2026

See all skills by solidjs

Report a problem with this skill