Skip to content
Skills Library
Programming · Building & coding

forge-idiomatic-developer

/forge-idiomatic-developer

Load this whenever you are about to write, edit, or review code that uses the forgelib library in any language.

Repository
forge ↗
Licence
MIT
Last repository change
26.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Load this whenever you are about to write, edit, or review code that uses the forgelib library in any language.

Original author description

Load this whenever you are about to write, edit, or review code that uses the forgelib library in any language.

How it works

  1. Pick the primitive deliberately
  2. Core contracts
  3. Before finishing
Original SKILL.md headings · 50 lines, 463 words
SKILL.md preview
---
name: forge-idiomatic-developer
description: Load this whenever you are about to write, edit, or review code that uses the forgelib library in any language.
---

# Building on Forge

Forge provides the backend primitives most applications need, with Postgres backends by default. Initialize one client from `forge.toml` and use Forge's actual API rather than inferring behavior from similar libraries.

Use the Forge version resolved by the project. Check its installed declarations when an exact signature or behavior matters; when editing Forge itself, use the repository source.

Read the relevant sections of the language reference:

- Node.js/TypeScript: [references/node.md](references/node.md)
- Python: [references/python.md](references/python.md)
- Rust: [references/rust.md](references/rust.md)
- Go: [references/go.md](references/go.md)

Read these only when they apply:

- [references/runtime-contract.md](references/runtime-contract.md) for configuration, errors, deployment, queues, scheduling, rate limits, pub/sub, presigning, flags, or maintenance.
- [references/application-design.md](references/application-design.md) for a nontrivial service, storage decision, authentication workflow, cross-system side effects, lifecycle, or test strategy.
Do not preload unrelated language references.

## Pick the primitive deliberately

| Need | Forge primitive | Core constraint |
| --- | --- | --- |
| Direct-key values, TTL state, counters, CAS | `kv` | Single-key operations; weakly consistent prefix scans |
| Durable background work and retry | `queue` | Requires an owning consumer; at-least-once |
| Ephemeral live fan-out | `pubsub` | At-most-once, live subscribers only |
| Files and presigned transfer URLs | `blob` | Application must enforce its ownership policy |
| Passwords, sessions, API keys, one-time tokens | `auth` | Application owns user and authorization records |
| Request throttling | `ratelimit` | Fail mode is a security/availability choice; not a business counter |
| Cron or delayed enqueue | `schedule` | Application must run scheduler ticks |
| Runtime settings and rollout flags | `config` | Cached; secrets remain environment-backed |

## Core contracts

- Queue delivery is concurrent and at-least-once. Settle with the delivery receipt or leased job, not its stable id. Ack only after the logical effect succeeds.
- Scope idempotency to the logical effect. A job id is a useful base for redelivery, but fan-out may require `job-id:recipient-id`, and duplicate jobs may require a stable domain operation id.
- Use managed workers where practical. Retain their promise/task/future, signal shutdown, and await completion.
- Run scheduler and maintenance loops when the selected features require them.
- Keep connection strings server-side and keep Forge's internal tables private.
- Presigning requires a non-empty secret without an empty fallback. Authorize access and verify the issued method, key, expiry, maximum bytes, and signature exactly.

## Before finishing

- Verify method names, sync/async use, option order, defaults, and error behavior against the project's installed Forge version.
- Confirm the chosen primitive supports the required behavior.
- Confirm every produced queue has an identified consumer in the deployed system; test redelivery at the logical side-effect boundary.
- Verify lifecycle behavior in the application's real process topology.
- Test the Forge boundary and the failure modes that matter to the change.
Files in this package (8)
  • SKILL.md 3 KB
  • evals/evals.json 8 KB
  • references/application-design.md 6 KB
  • references/go.md 5 KB
  • references/node.md 11 KB
  • references/python.md 11 KB
  • references/runtime-contract.md 8 KB
  • references/rust.md 8 KB

Versions

The database has no other skills named forge-idiomatic-developer.

Database snapshot: 13.11.2026 · package version b75d995a1097 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100idiomatic-rust
    Use when writing, reviewing, or refactoring Rust code. Routes the task to handbook chapters on idioms, lints, errors, testing, generics, and pointers under the edition 2024 and current-stable pins.
  • 91go
    Expert Go programming skill authored by spf13 (former Go team lead, author of Cobra, Viper, Hugo, Afero). Covers idiomatic Go — package design, error handling, interfaces, concurrency, testing, and project layout, current through Go 1.27. Use whenever Go code is written,…
  • 100forge
    Implement tasks from a change. Use when the user wants to start or continue implementation of an existing change.
  • 90port-review
    Review an existing SDK for idiomatic quality, consistency, and developer ergonomics. Use when asked to "review this SDK", "is our SDK idiomatic", or "assess SDK developer ergonomics".
  • 95go-coding-standards
    Go coding standards following idiomatic Go patterns, error handling, concurrency best practices, and modern Go tooling. Use for Go projects requiring clean, efficient, production-ready code with comprehensive testing.
  • 100flutter-idiomatic-flutter
    Compose modern Flutter layouts and widgets idiomatically. Use for widget trees, layout constraints, mounted safety, and UI composition—not BLoC state management, routing, dependency injection, or tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.