agentleFS
temporaliotemporalio/ui/CLAUDE.md

ui

CLAUDE.md447 starsChanged 3 months agoMITView on GitHub

SvelteKit + Svelte 5 + TypeScript + TailwindCSS + Io and Holocene design systems

We split this CLAUDE.md into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Type checking: Run pnpm check to verify TypeScript compliance

    line 55
  2. Distinctive:

    Test execution: Run appropriate test suites based on changes

    line 56
  3. Distinctive:

    Follow patterns: Use existing component patterns and utility functions

    line 57
  4. Very specific:

    Design system: Prefer Io components (src/lib/io), then Holocene components (src/lib/holocene), over custom implementations.

    line 58
  5. Distinctive:

    Accessibility: Ensure proper ARIA attributes and semantic HTML

    line 59
  6. Distinctive:

    No comments: Don't add code comments unless explicitly requested

    line 63
  7. Distinctive:

    Type safety: Always provide proper TypeScript types

    line 64
  8. Distinctive:

    Test coverage: Write tests for new utilities and business logic

    line 66
  9. Distinctive:

    Import organization: Follow the established import order

    line 67
  10. Distinctive:

    Validation: Use Zod for runtime type validation

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
CLAUDE.md

Claude AI Assistant Rules for Temporal UI

SvelteKit + Svelte 5 + TypeScript + TailwindCSS + Io and Holocene design systems

Commands

pnpm lint              # Run all linters
pnpm check             # TypeScript type checking
pnpm test -- --run              # Run unit tests

Svelte 5 Patterns

// Props
let { class: className = '', adapter }: Props = $props();

// State
let count = $state(0);

// Computed
const doubled = $derived(count * 2);

// Effects
$effect(() => {
  console.log('Count:', count);
  return () => cleanup();
});

// SuperForms
const { form, errors, enhance } = $derived(
  superForm(data, {
    SPA: true,
    validators: zodClient(schema),
    onUpdate: async ({ form }) => {
      /* handle submit */
    },
  }),
);

Import Order

  1. Node.js built-ins
  2. External libraries (with svelte/** first)
  3. SvelteKit imports ($app/**, $types)
  4. Internal imports ($lib/**)
  5. Component imports ($components/**/*.svelte)
  6. Relative imports (./, ../)

Workflow

  1. Always run linting: Execute pnpm lint after making changes
  2. Type checking: Run pnpm check to verify TypeScript compliance
  3. Test execution: Run appropriate test suites based on changes
  4. Follow patterns: Use existing component patterns and utility functions
  5. Design system: Prefer Io components (src/lib/io), then Holocene components (src/lib/holocene), over custom implementations. Io replaces Holocene over time
  6. Accessibility: Ensure proper ARIA attributes and semantic HTML

Code Generation

  • No comments: Don't add code comments unless explicitly requested
  • Type safety: Always provide proper TypeScript types
  • Component reuse: Leverage existing components and utilities
  • Test coverage: Write tests for new utilities and business logic
  • Import organization: Follow the established import order

Error Handling

  • Validation: Use Zod for runtime type validation
  • Error boundaries: Implement proper error boundaries for components
  • Network errors: Handle API failures gracefully
  • User feedback: Provide clear error messages and loading states

Naming

  • Files: kebab-case (workflow-status.svelte)
  • Components: PascalCase in imports, kebab-case for files
  • Functions: camelCase
  • Types: PascalCase
  • Use import type for type-only imports

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.