Everything we ship at FC compounds — the research feeds the strategy, the strategy ships as tools, the tools get pressure-tested and deployed. Each layer makes the next one faster.
This wasn't planned. It emerged from a simple realization: every session with Claude Code could ship something real. Here's what happened.
One HTML file. A tool to help international student ministry workers understand their context. No framework, no build step — just a single file deployed to Cloudflare Pages in 20 minutes. It worked.
Every session can ship. The pattern became clear: identify a real problem, build a focused tool, deploy it the same day. One session, one tool. The portfolio grew faster than expected.
Quality became the constraint. Fast shipping is easy. Shipping things that don't embarrass you is harder. We built the roast cycle — 3 rounds of 10-expert panel review, 150 findings per project — to pressure-test AI-generated work before it goes live. Speed stayed. Slop went away.
The Missions Library changed the scale. We scraped 161,000 articles from 101 missions and faith-and-work organizations. That corpus didn't just become searchable — it became the research base for the Faith & Work Hub strategy, partner analysis, and content tools. Research and product stopped being separate tracks.
50+ deployed projects. A custom skill library. Automated review loops. Research infrastructure that feeds live products. And a workflow that gets faster the more you use it — because every session builds on what came before.
Each layer of work feeds the next. This isn't a collection of projects — it's a system.
The corpus isn't just data — it surfaces what practitioners actually talk about. When we built the Faith & Work Hub strategy, we weren't guessing at what Asian returnee professionals need. We had 161,000 data points from the organizations already serving them. The strategy came out of the research, not despite it.
The strategy isn't just a plan — it becomes the brief for tools. Clear audience, clear problem, clear success criteria. That's why tools built from the corpus take a session instead of a week. Half the thinking is already done.
The tools go through the quality loop so they don't embarrass the org. Three rounds of expert review, a 30-point anti-AI audit, and real deployment. Not perfect — but intentional.
And because the infrastructure already exists — the CLAUDE.md files, the custom skills, the deploy pipeline — the next thing is always faster than the last one.
No version numbers, no install instructions. Just the tools and the reason each one earned its place.
/roast /deploy /resume /wrapup — the parts of the workflow that happen every time, automated. Each skill is a slash command that launches a specialized agent loop.Walk through a real build from start to finish. This is the CAMH Directory — 550+ verified Asian American Christian therapists, built in a single session.
550+ Asian American Christian therapists exist, but they're scattered across Psychology Today, PAAC, and personal websites with no centralized, searchable directory. A real gap. A fixable one.
Python scripts pull from Psychology Today and PAAC. Structured CSV gets cleaned into JSON — therapist name, location, specialties, languages, insurance, photo. No AI needed here; just file I/O and parsing.
Single HTML file. Fuse.js for client-side fuzzy search. Tailwind CDN for styling. One wrangler pages deploy command. Live at camh-directory.pages.dev. Total time: one session.
Three rounds of 10-expert panel review. 150 findings total. Accessibility, performance, copy clarity, trust signals, mobile layout. Prioritize the ones that matter, implement them in order.
A 30-point checklist that finds AI aesthetics: gradient washes, vague copy ("empowering individuals to thrive"), corporate jargon, excessive border-radius, shadow stacking. Replace with specific language and human-feeling design. This is what separates a tool people trust from a tool that feels generated.
381 therapist photos matched and loaded. State pages added. Submit form wired. OG image generated. Sitemap built. Done — and the loop is exactly the same whether it's a 1-page tool or a 10-page product.
Five projects that show range: from the org's public face to a co-built product to a client site to a real community tool. Not a complete list — the complete list has 50+ items.
If you're joining FC, you're not starting from scratch. The tools are here, the methodology is documented in every CLAUDE.md, and everything built so far is open to the next person who wants to take it further.
What's coming next: the Faith & Work Hub listening tour (50 returnee interviews in Singapore), real users on Accent Trainer, Care Navigator going public, and whatever surfaces from the corpus next. The pipeline doesn't stop.
The first thing to run when you open any project:
The methodology is learnable. The infrastructure is already running. The only thing left is to build.