BOUNDARIES · DECISIONS · EVIDENCE
Reducing ambiguityBOUNDARIES · DECISIONS · EVIDENCE
Reducing ambiguityTHANARATTANAN / PLAYGROUND
Owner-created demos and source examples with status, evidence, trade-offs, and limitations.
← Back to home
Source name: template cli สำหรับ angular
A source example for generating a repeatable Angular application foundation so teams begin from explicit conventions instead of rebuilding setup decisions in every repository.
Source name: template cli สำหรับ netcore api clean architecture
A CLI source example that generates a .NET API with presentation, use-case, domain, repository-port, and infrastructure boundaries.
Source name: template cli สำหรับ netcore worker clean architecture
A source template for background-processing services where scheduling, domain rules, adapters, retries, and operating behavior need separate ownership.
Source name: code base netcore
A reusable application foundation intended to centralize cross-cutting behavior while keeping feature ownership visible.
Source name: code base libraries
A library collection for reusable capabilities whose value depends on explicit contracts, versioning, and a narrow dependency surface.
Source name: realtime chat + AI translator
A demo that combines realtime message delivery with AI-assisted translation while keeping transport, translation, retention, and failure behavior as separate responsibilities.
Source name: Oauth login
An identity-flow demo focused on trust boundaries beyond the login screen: redirect state, PKCE, nonce, account mapping, expiry, and recoverable failures.
Source name: two way factor authentication scan QRCode
A QR-enrollment demo for a second authentication factor, with attention to one-time challenges, expiry, replay, recovery, and explicit session boundaries.
Source name: agrimap-agent-skills
A public agent-skill source example that makes instructions, boundaries, reusable context, and expected outputs explicit for agricultural-map work.
Source name: sql-context-pack
A public context-pack source example for making SQL constraints, naming, safety expectations, and review context available before generation or modification.
Source name: e2e-test-skill (api/sp)
A source example for framing API and stored-procedure end-to-end tests around boundaries, fixtures, observable outcomes, and failure evidence.
CONTACT
Share the outcome, constraints, current system, and the evidence that is still missing. That is enough to begin reducing ambiguity.
[email protected]