agentleFS
petarzarkovpetarzarkov/dunx/.claude/skills/spike/SKILL.md

spike

Skill93 starsChanged 4 months agoMITView on GitHub

Resolve an open technical question by measuring it on real Bun instead of assuming, then record the verified result in docs/architecture/constraints.md. Use for an open item in docs/ROADMAP.md that turns on runtime behaviour, before committing to any API shape that depends on runtime or tsc behaviour, and whenever a design argument turns on "does Bun/TypeScript actually do X?".

56 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-news-monitor, blocked-page-recovery 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.
  • Samin12Skill

    competitor-news-monitor

    Watch named companies for material news; cited digests.

    Also in 6 projects that use this

  • nobodyohm-webSkill

    blocked-page-recovery

    Recover blocked/paywalled/WAF'd pages via fallbacks.

    Also in 6 projects that use this

  • Samin12Skill

    document-to-action-items

    Extract cited obligations, deadlines, tasks from documents.

    Also in 6 projects that use this

  • michaellam26Skill

    sdlc-review

    Trigger stage-specific reviews for an SDLC project and save results to reviews/

    Also in 5 projects that use this

  • john-data-chenSkill

    teams-meeting-pipeline

    Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

    Also in 8 projects that use this

  • Tommy-ywSkill

    songwriting-and-ai-music

    Songwriting craft, AI music generation prompts (Suno focus), parody/adaptation techniques, phonetic tricks, and lessons learned. These are tools and ideas, not rules. Break any of them when the art calls for it.

    Also in 8 projects that use this

  • +1 more from Samin12

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 0

    Distinctive

    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:

    If the question came from an Open items row in docs/ROADMAP.md, update its file under internal/notes/roadmap/, or delete it and the row …

    line 35
  2. Very specific:

    Never write "should work", "presumably", or "in theory" into docs/architecture/constraints.md.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 52 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

/spike

An entry in docs/architecture/constraints.md cites the probe or type-check output it rests on, which is why the decisions built on it hold. A spike adds entries of that kind. Open questions live in the Open items section of docs/ROADMAP.md, one file each under internal/notes/roadmap/.

Procedure

  1. State the question as a falsifiable claim and name what it gates, for example "does @Post(path, { body: Schema }) constrain the method signature through the method decorator's generic?" gates the typed-input API.
  2. Write a throwaway probe in the scratchpad directory, never under packages/ or examples/. It is not code that ships and it must not reach a commit, a coverage run, or a build.
  3. Run it on real Bun and record bun --version alongside the output. A type-level question runs through the repo's tsc instead; record its version.
  4. Delegate the probing when it is noisy or wide. Give a subagent the claim and the probe location; ask back for the literal command, the literal output, and a one-line verdict. Iterating a decorator probe through six type errors is exactly the kind of output that should never enter the main thread.
  5. Record the result in docs/architecture/constraints.md, under the topic it belongs to:
    • confirmed → an entry with the command, the Bun version, and the literal output in a fenced block. Match the existing terseness - the paramtypes: [ "Db", "Object", "Number" ] entry is the model.
    • refuted → write down the fallback and why, under the decision it affects. A rejected approach recorded is the whole point of that document.
    • If the question came from an Open items row in docs/ROADMAP.md, update its file under internal/notes/roadmap/, or delete it and the row when the spike settles it. A resolved question left listed is worse than no list.
  6. Delete the probe.

Rules

  • Never write "should work", "presumably", or "in theory" into docs/architecture/constraints.md. If it was not run, it does not go in.
  • A spike that changes the public API shape belongs before the code it gates, not after.
  • One spike, one claim. Two questions are two probes.
  • Probes may use anything - including the dialects this repo bans in shipped code (experimentalDecorators, reflect-metadata) if refuting them is the point. That is how the existing emitDecoratorMetadata entry was produced. Scratchpad only.

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.