agentleFS
alamenaialamenai/terrae/.claude/skills/check/SKILL.md

check

Skill245 starsChanged 9 months agoMITView on GitHub

Verify all outputs exist after creating a new component and fix any issues

  • Reads credentials

88 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 75 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify that all 8 required outputs exist and are wired correctly after creating a new component.

    line 9
  2. Very specific:

    Default values use SCREAMING_SNAKE_CASE constants above the component

    line 22
  3. Very specific:

    If the component exposes a control hook, it is also exported (e.g., useCycloneControl)

    line 29
  4. Very specific:

    Every example rendered on the page has a matching getExampleSource call

    line 54
  5. Very specific:

    If the component has configurable props, a properties Table section exists

    line 55
  6. Distinctive:

    All documented props match the actual component props (no missing, no extra)

    line 56
  7. Distinctive:

    After the table, list specific issues with file paths and line numbers.

    line 102
  8. Distinctive:

    If any checks have fail or warn status, fix them automatically:

    line 106
  9. Distinctive:

    After all fixes, re-run the checks to confirm everything passes

    line 110
  10. Distinctive:

    If a fix requires a decision (e.g., which sidebar section to place the component in), ask the user before proceeding.

    line 113

“Common” is measured: kept by at least 6 in 10 of the 75 edited versions of this file we could read. “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

Check Component Skill

Verify that all 8 required outputs exist and are wired correctly after creating a new component.

Instructions

Given a component name (e.g., cyclone, MapCyclone), normalize it to its kebab-case slug (e.g., cyclone) and run through every check below.

Check 1: Component Source File

  • File exists: src/registry/map/{slug}.tsx
  • Has "use client" directive (if it uses hooks, event handlers, or browser APIs)
  • Exports a named component (e.g., MapCyclone)
  • Uses type not interface for type definitions
  • Uses arrow functions with explicit returns
  • Default values use SCREAMING_SNAKE_CASE constants above the component
  • Required props come before optional props in the type definition
  • Cleanup in useEffect return functions (removes layers, sources, markers, event listeners)

Check 2: Barrel Export

  • src/registry/map/index.tsx has an export line for the component
  • If the component exposes a control hook, it is also exported (e.g., useCycloneControl)

Check 3: Registry Entry

  • registry.json has an entry in items with:
    • name in kebab-case (e.g., cyclone)
    • registryDependencies includes "https://www.terrae.dev/map.json"
    • files[0].path matches the source file path
    • files[0].target follows components/ui/map/{slug}.tsx

Check 4: Example Files

  • At least one example exists: src/app/docs/_components/examples/{slug}-example.tsx
  • Examples import from @/registry/map
  • Examples wrap the map in <div className="h-full w-full">
  • Examples use process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || "" as access token
  • Examples that use hooks or event handlers have "use client"

Check 5: Documentation Page

  • File exists: src/app/docs/{slug}/page.tsx
  • Exports metadata with a title
  • Uses DocsLayout with title, description, prev, and next
  • First section is "Installation" with two CodeBlocks (base map + component)
  • Basic ComponentPreview appears directly after Installation
  • Every example rendered on the page has a matching getExampleSource call
  • If the component has configurable props, a properties Table section exists
  • All documented props match the actual component props (no missing, no extra)

Check 6: Sidebar Navigation

  • src/app/docs/_components/docs-sidebar.tsx has a NavItem for the component
  • The href matches /docs/{slug}
  • Has badge: "new"
  • Placed in the correct section ("Core" or "Features")
  • The Lucide icon is imported

Check 7: Components Page

  • src/app/docs/components/page.tsx has a ComponentItem entry
  • The href matches /docs/{slug}
  • Has isNew: true
  • category matches the sidebar section
  • installCommand URL matches https://www.terrae.dev/{registry-name}.json
  • The Lucide icon is imported

Check 8: Changelog

  • src/app/docs/changelog/page.tsx has an entry in the most recent ChangelogEntry
  • Entry has title, description (with <code> tag for component name), and href
  • href matches /docs/{slug}

Output Format

Present results as a checklist table:

| #   | Output             | Status | Notes                   |
| --- | ------------------ | ------ | ----------------------- |
| 1   | Component source   | pass   |                         |
| 2   | Barrel export      | pass   |                         |
| 3   | Registry entry     | fail   | Missing target path     |
| 4   | Examples           | pass   | 3 examples found        |
| 5   | Documentation page | warn   | Missing props: `scale`  |
| 6   | Sidebar navigation | pass   |                         |
| 7   | Components page    | pass   |                         |
| 8   | Changelog          | pass   |                         |
  • pass: Everything correct
  • warn: Works but has minor issues (e.g., missing optional prop in docs table)
  • fail: Missing or broken, needs fixing

After the table, list specific issues with file paths and line numbers.

Fix Phase

If any checks have fail or warn status, fix them automatically:

  1. Work through issues in check order (1–8)
  2. Apply the minimal change needed for each issue
  3. After all fixes, re-run the checks to confirm everything passes
  4. Present the updated checklist table showing all checks as pass

If a fix requires a decision (e.g., which sidebar section to place the component in), ask the user before proceeding.

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.