Clerk auth for Expo and Hono

Clerk sign-in for the Expo app and session verification on the Hono API, with auth on by default behind a public-path allowlist, a dev bypass, and tests that run Clerk's real verification against a local keypair with no account or network.

Category: vendor

In your existing repository

Ask your agent to check compatibility, follow this fragment’s brief, and verify the resulting project. What happens next

Applies to:: mobile-expo

Add to your project

Paste the prompt into the coding agent working on your project.

View prompt

Add the clerk fragment to this existing repository. 1. Run npx @steamfield/stacks show clerk --json and check that it fits the project. If it does not, explain why before changing files. 2. Run npx @steamfield/stacks add clerk and follow the brief it prints. 3. In this repository, run npx @steamfield/stacks verify. Fix failures without weakening or skipping verification steps. 4. Summarize what changed and the verification result. Quote published stats only when they are available, including their interval and sample size. The stacks docs, written for agents, are at https://stacks.steamfield.io/llms.txt.

Or use the terminal

npx @steamfield/stacks add clerk

Verify steps
Step	Phase	Layer	Command

No additional verify steps declared. Run the project’s existing verification after applying the brief.

Use with a new stack

Starting fresh instead? These stacks support this fragment.

mobile-expodefault
npx @steamfield/stacks new mobile-expo

Files

This fragment supplies instructions rather than project files.

Usage

Among stacks projects in the 28 days through 30 Oct 2026: 10,325 projects; 79% reached a green verify (78–80%, n=7,085).

Weekly projects by stack

Projects whose final fragment set included this fragment, grouped by stack.

12 weeksAvailable history

mobile-expo

mobile-expo

Stacks projects per UTC week through 30 Oct 2026. Published stack counts only.

Data table

Week ending	Stack	Projects
5 Jul 2026	mobile-expo	520
12 Jul 2026	mobile-expo	840
19 Jul 2026	mobile-expo	1,105
26 Jul 2026	mobile-expo	1,385
2 Aug 2026	mobile-expo	1,500
9 Aug 2026	mobile-expo	1,645
16 Aug 2026	mobile-expo	1,805
23 Aug 2026	mobile-expo	1,940
30 Aug 2026	mobile-expo	2,000
6 Sept 2026	mobile-expo	2,020
13 Sept 2026	mobile-expo	2,260
20 Sept 2026	mobile-expo	2,300
27 Sept 2026	mobile-expo	2,465
4 Oct 2026	mobile-expo	2,470
11 Oct 2026	mobile-expo	2,665
18 Oct 2026	mobile-expo	2,760
25 Oct 2026	mobile-expo	2,925

By stack

How often this fragment stays in a default composition, or gets attached as an option.

mobile-expo

Default · kept92%

10,325 projects including the fragment

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table

Stack	Projects	Role	Share
mobile-expo	10,325	Default · kept	92%

Green rate with and without it

This compares projects; it isn't an effect of the fragment.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Often used with

Co-occurrence above the baseline, within a stack. Required fragment pairs are excluded.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.