| name | sample-app-production |
| description | Build and maintain a small sample application that demonstrates recommended integration patterns without becoming an unofficial framework or stale toy. |
Sample App Production
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using official SDKs, API contracts, supported runtime versions, user scenario, and CI validation. Do not fill material gaps with assumptions when they can change the result.
- Define the concept taught, keep architecture minimal, pin supported versions, exercise realistic errors, and automate smoke verification.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
The sample remains runnable, idiomatic, versioned, and clearly scoped to the concept it teaches.