Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/effect-development

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

Effect development guidance. Use when implementing or reviewing code that composes Effect APIs or patterns, or that adds or changes API signatures.

  • 1 file
  • 1.4 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/effect-development

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈42 tokens for metadata: the name and description. ≈306 when used: this file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈168 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Use the repository's AI documentation as targeted reference, not ambient context:

  1. Identify the Effect APIs and concepts involved in the change.
  2. Search LLMS.md and ai-docs/src for those names and concepts, then read the matching sections and examples.
  3. Apply the relevant guidance and inspect nearby source and tests for any repository-internal conventions not covered by the documentation.

The task is ready for implementation when every material Effect API or pattern has matching local guidance, or the search has established that none exists.

API conventions

Write option types inline in the signature by default. Mark fields readonly and add | undefined to optional fields:

export const make = (options: {
  readonly capacity: number
  readonly strategy?: "dropping" | "sliding" | undefined
}): Effect.Effect<Queue> => ...

Declare a named options type only in these cases:

  • A substantial set of options is shared across several APIs, so a named type keeps them in sync.
  • The options type needs complex conditional logic, such as conditional or mapped types driven by type parameters.

A long option list for a single API is not on its own a reason to extract a named type.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

README badge

README badge for pingdotgg/t3code/effect-development