feat(twister): twist-scoped LLM docs and compiled example twists

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?

[KrisBraun]

What

Adds two exports to @plotday/twister/creator-docs for building LLM prompts that generate twists:

• getTwistDocumentation() — the same per-module LLM documentation as getBuilderDocumentation(), but scoped to what a twist author needs: it omits the Connector base class and the mail-protocol tools (tools/imap, tools/smtp). Twists must never extend Connector, and including its full API in a generation prompt invites exactly that mistake. getBuilderDocumentation() is unchanged.
• TWIST_EXEMPLARS — three complete, minimal example twists rendered as a formatted string (specification + implementation for each): reacting to new notes with the AI tool, an authenticated periodic import using a secure Options field with store-based dedup, and a recurring scheduled digest with an idempotency guard.

Why

Type definitions alone don't teach tool wiring — how build() declarations, this.callback, the store, and scheduling fit together in a working twist. Whole-program examples anchor those patterns and improve generated-twist quality.

How it stays correct

The exemplars are real sources under twister/src/exemplars/, compiled by the package build on every run, so they can't rot. A prebuild step splits each file into its leading /* SPEC: ... */ comment and implementation and embeds them into the exported string, failing the build loudly if an exemplar is missing its spec header.

Notes

• Changeset included (minor).
• typedoc.json and tsconfig.build.json gain scoped config so the exemplars typecheck via the package's own export conditions without affecting emitted output.

🤖 Generated with Claude Code

[KrisBraun]

Does it work?