v0.1.0

First public release.

38 agentic-AI prompts for software project delivery, built around
financial trading systems, Go backend development, and AWS cloud
infrastructure. MIT licensed.

Browse: https://shing1211.github.io/prompt-engineering/

What is in it

19 of the 38 prompts cover multi-broker trading systems — the vertical
wedge, and the reason this library is not another generic prompt collection:

• Broker SDKs, one prompt per venue: Longbridge, Tiger Trade, Webull, IBKR
  Client Portal, Futu OpenD, Hua Sing Tong vbroker, plus a generic HMAC pattern
• Consolidated L2 tape from six brokers into MSK, Redis, and S3
• Market microstructure: VPIN, order flow imbalance, arbitrage detection
• Intraday risk: VaR/CVaR, drawdown controls, margin calls, Greeks, kill switch
• Money correctness: multi-currency PnL, corporate actions, reconciliation
• MiFID II best execution, trade surveillance, audit trails

The other 19 are the cross-cutting practice behind that work: architecture,
API design, testing, security, performance, observability, migration,
incident response.

Corrections after this release

The v0.1.0 notes were published before a full audit of the broker prompts.
The audit found that broker-integration.md carried a per-broker adapter table
asserting endpoints and auth schemes as fact, and four of them were wrong:

	Published in v0.1.0	Corrected
Longbridge endpoint	openapi.longbridgeapp.com (404)	openapi.longbridge.com, with separate WebSocket hosts for quote and trade
Longbridge auth	HMAC-SHA256, X-Broker-Id headers	OAuth 2.0 by default; API-key signature is a legacy fallback
Tiger endpoint	openapi.tigerbroker.com (does not resolve)	openapi.tigerfintech.com
Tiger auth	Tiger-Open-API-Key + X-Signature	private-key signature, not HMAC headers
Webull endpoint	openapi.webull.com (does not resolve)	api.webull.com, plus separate gRPC and streaming hosts
Webull auth	OAuth2-like token flow	HMAC-SHA1 signature with x-app-key / x-signature, plus a reusable token

Also retracted: the claim that "Webull does NOT support order cancellation
via API". The current API exposes order place, replace, and cancel together.

trading-risk.md had the same class of error: broker-specific maintenance
margin thresholds presented as universal constants ("> 90% utilized = margin
call imminent", "max drawdown > 10%"). These are mandates that vary by broker,
account type, instrument, and market.

If you built an adapter from the v0.1.0 table, check it against the vendor
documentation before trusting it. The corrected table is in
prompts/broker-integration.md, with a working doc root per vendor, and every
broker prompt now carries an instruction to verify its specifics. CI enforces
this via scripts/check_vendor_claims.py.

Notable fixes made in getting this public

• 15 of 39 files had CRLF endings, split against the rest. Normalized, and
  .gitattributes plus .editorconfig now prevent recurrence.
• 62 [reference:N] artifacts removed from two prompts — generation noise
  that read as broken citations on a rendered page.
• Heading hierarchy in 19 prompts. Several used # for what were really
  top-level sections, so each document had multiple H1s and the generated
  table of contents listed the title three times. 455 headings fixed.
• Stale model pins unpinned to model: any.
• Counts made generated rather than hand-maintained, after they drifted.

Every check is proven to fail

Validation is verified by injection, not just by passing. A bad mode value,
a missing category, a malformed tag, a title/H1 mismatch, a hand-edited
count, a broken link, a prompt missing from the site nav, and a second H1 in
a document each produce a non-zero exit naming the file.

scripts/validate.sh

Contributing

Proposals go in an issue via the Prompt idea form; finished prompts go
straight to a pull request. CONTRIBUTING.md has the frontmatter contract
and review criteria. Adding a prompt touches three files, and the one that's
easy to miss is the site nav entry.

License

MIT. Use them, fork them, adapt them.