agentleFS
Sign inStart free
thoughtfulllcthoughtfulllc/gridland/.claude/skills/debug-layout/SKILL.md

debug-layout

Skill363 starsChanged 7 months agoMITView on GitHub

Diagnose layout issues in Gridland components. Spawns the layout-debugger agent with the relevant component. Use when a component renders incorrectly or layout looks wrong.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS provided, find the component file matching the argument (component name or file path).

    line 8
  2. Distinctive:

    If no argument, ask which component has the layout issue.

    line 10
  3. Distinctive:

    Read the component file to understand its JSX structure.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Diagnose layout issues in a Gridland component.

  1. If $ARGUMENTS provided, find the component file matching the argument (component name or file path).
  2. If no argument, ask which component has the layout issue.
  3. Read the component file to understand its JSX structure.
  4. Spawn the layout-debugger agent with the component file path and a description of the visual problem.
  5. Present the diagnosis: what's wrong, why, and how to fix it.
  6. Suggest running bun run demo <component-name> to visually verify the fix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free