agentleFS
dmmulroydmmulroy/skills/prelude/SKILL.md

prelude

Skill428 starsChanged 4 months agoMITView on GitHub

Prelude bootstrapping for TypeScript. Use when creating or rebuilding a prelude.ts from ambient generic helpers and types.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. laceyp99/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 12 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read repository instructions, package manifests, TypeScript configuration, source layout, and import conventions.

    line 14
  2. Distinctive:

    every caller of plausible ambient helpers.

    line 20
  3. Distinctive:

    Search by both filenames and concepts.

    line 22
  4. Distinctive:

    Completion criterion: Every plausible ambient definition found by repository-wide filename, symbol, and duplication scans is inventoried …

    line 24
  5. Distinctive:

    no domain, application service, adapter, protocol, or focused generic module is a more precise owner.

    line 31
  6. Distinctive:

    Completion criterion: Every inventoried candidate has one decision grounded in its semantics and callers.

    line 40
  7. Very specific:

    Read the bundled prelude.ts completely.

    line 44
  8. Very specific:

    When the project uses Effect, use Effect's result/error facilities and remove the template's local Result fallback.

    line 48
  9. Very specific:

    When the project uses better-result, use it and remove the local fallback.

    line 49
  10. Very specific:

    When the project uses neither, ask whether to install better-result.

    line 50
  11. Distinctive:

    If accepted, install it and remove the local fallback.

    line 51
  12. Very specific:

    If declined, enable the template's local Result types and helpers.

    line 52
  13. Distinctive:

    update every caller to import from the prelude directly.

    line 64
  14. Distinctive:

    remove superseded definitions and compatibility re-exports after their callers move.

    line 66
  15. Distinctive:

    Keep the resulting module side-effect free.

    line 68
  16. Distinctive:

    Completion criterion: Every approved candidate has one canonical definition, every caller uses it, and no removed source remains as a …

    line 70
  17. Distinctive:

    Run the repository's formatter, type checker, linter, and focused tests.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Bootstrap a TypeScript Prelude

A prelude is an explicitly imported module for ambient helpers and types: ubiquitous, domain-neutral building blocks that have no more precise owner. Use the bundled prelude.ts as the foundation, then adapt it to evidence from the target repository. Apply ../coding-standards/SKILL.md throughout.

Ambient describes a helper's role, not a TypeScript global. Keep prelude exports behind ordinary imports; do not add global declarations or global augmentation.

1. Map the repository

Read repository instructions, package manifests, TypeScript configuration, source layout, and import conventions. Locate:

  • an existing prelude or equivalent shared module;
  • files named utils, helpers, common, types, result, errors, or similar;
  • generic type aliases and tiny generic functions repeated across modules;
  • established libraries for results, schemas, redaction, branding, collections, and exhaustive matching;
  • every caller of plausible ambient helpers.

Search by both filenames and concepts. Use the ubiquitous generic helper/type categories in the coding standards as seed search terms, then inspect definitions and callers rather than classifying from names alone.

Completion criterion: Every plausible ambient definition found by repository-wide filename, symbol, and duplication scans is inventoried with its owner, callers, dependencies, and current behavior.

2. Classify every candidate

A symbol belongs in the prelude when all of these hold:

  • it is domain-neutral and useful across unrelated modules;
  • no domain, application service, adapter, protocol, or focused generic module is a more precise owner;
  • centralizing it reduces duplication or gives a ubiquitous concept one canonical implementation;
  • its dependencies are minimal, stable, and already justified by the project;
  • its behavior is small enough to understand at the import site or hidden behind a precise type.

Keep a symbol with its focused owner when it encodes domain meaning, application policy, boundary translation, framework behavior, I/O, or a cohesive generic concept such as string casing or non-trivial collection operations. Prefer an established library over a local duplicate. A prelude is a curated foundation, not a barrel or miscellaneous dumping ground.

Record one decision for every candidate: use the established library, keep the current owner, move into the prelude, merge with a template symbol, or delete as an unused duplicate.

Completion criterion: Every inventoried candidate has one decision grounded in its semantics and callers; no candidate remains classified only by its filename or name.

3. Seed from the template

Read the bundled prelude.ts completely. Copy it to the project's established shared-module location as the starting point. If a prelude already exists, merge deliberately instead of overwriting it.

Choose exactly one expected-failure foundation:

  1. When the project uses Effect, use Effect's result/error facilities and remove the template's local Result fallback.
  2. When the project uses better-result, use it and remove the local fallback.
  3. When the project uses neither, ask whether to install better-result.
    • If accepted, install it and remove the local fallback.
    • If declined, enable the template's local Result types and helpers.

Retain each other template export only when repository usage, the coding standards, or the requested foundation justifies it. Preserve compatible existing behavior when merging equivalent helpers; surface semantic conflicts rather than silently choosing one implementation.

Completion criterion: The target file is founded on the template, has exactly one result strategy, and every retained template export has an explicit justification.

4. Consolidate ambient helpers and types

Move or merge the approved repository candidates into the prelude. For each moved symbol:

  • preserve behavior unless a behavior change was requested;
  • preserve or deliberately migrate its public name and type contract;
  • update every caller to import from the prelude directly;
  • retain required JSDoc, safety comments, and targeted lint suppressions;
  • remove superseded definitions and compatibility re-exports after their callers move.

Keep the resulting module side-effect free. It must not read configuration, acquire resources, register handlers, perform I/O, contain domain/application policy, or re-export unrelated modules.

Completion criterion: Every approved candidate has one canonical definition, every caller uses it, and no removed source remains as a second source of truth.

5. Verify the foundation

Run the repository's formatter, type checker, linter, and focused tests. Search again for the old symbols, duplicate definitions, stale import paths, and broad utility files that were part of the inventory. Review every prelude export for current usage or an explicit foundational reason.

Report:

  • the chosen result strategy;
  • template exports retained or removed;
  • repository helpers moved, merged, left in place, or deleted;
  • verification commands and outcomes.

Completion criterion: Repository checks pass, every inventory decision is reflected in code, duplicate ambient definitions are gone, and every prelude export is justified.

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.