Welcome & Why We Built This
This is where every Full-Stack Engineer hire at Senzary starts. Not a tutorial — a working briefing.
You're walking into a company where the work is real, the systems are live, and the standard Eric holds is simple: every claim ships with proof. For this track that proof lives across GitHub, Vercel, DigitalOcean, ThingsBoard 4.3.
Three laws govern everything you'll do here:
1. **Prove it with a url.** No claim without proof. A status update is not real without the artifact (URL, screenshot, file, ticket). Eric will ask for it. Have it ready. 2. **Skills do the structural work, you do the judgment.** `smart-industry-architecture`, `smart-industry-mcp`, `senzary-mcp`, `senzary-custom-mcp`, `thingsboard-pe` — these do the heavy lifting. You decide what matters and what ships. 3. **No generic next steps.** "I'll keep an eye on it" is not an answer. Every item carries an owner and a date or it gets escalated.
By the end of this chapter you'll know the core skills that power the Full-Stack Engineer motion, the systems you must be fluent in, and the exact prompts Eric uses to drive his own day.
How Eric talks about this
“load smart-industry-architecture and run the standard motion”
This is the load phrase. When you say it, the skill engages: it reads its triggers, pulls referenced docs, and prepares the structural work. If you skip the load and just describe what you want, you get a generic answer.
“prove it with a URL”
This is the rule that distinguishes a Senzary update from a vendor update. Prove it with a url is non-negotiable. Eric will not act on a status that lacks proof.
“no generic next steps”
Eric corrected me here. Early on I tried 'we should monitor this' as a next step. He killed that pattern. Every item has an owner and a date, or it doesn't exist.
Try these exact phrasings
Try it yourself
Pick any open item from GitHub that falls in your track. In ≤300 words: name the skill you would load to advance it (must be one of ['smart-industry-architecture', 'smart-industry-mcp', 'senzary-mcp']), name the next action with an owner and a date, and paste the GitHub record URL as proof.
- names a real skill from this track's required list
- names a concrete next action with an owner and a date
- includes the GitHub record URL
Quick check
1. Which skill is loaded for Full-Stack Engineer morning work?
- a. smart-industry-architecture
- b. smart-industry-architecture
- c. thingsboard-pe
- d. create-skill
Reveal answer
smart-industry-architecture is the primary load for this track. The triggers for it match the day-1 morning motion.
2. What makes a status update real in Senzary?
- a. A confident summary
- b. A link to the artifact
- c. A meeting follow-up
- d. An emoji reaction
Reveal answer
'Prove it with a url' is the rule. No claim without proof. A link, a screenshot, a file path — something verifiable.
3. What's wrong with 'I'll keep an eye on it' as a next step?
- a. Nothing, it's fine
- b. It hides the decision
- c. It's too long
- d. It's not in Spanish
Reveal answer
Generic next steps hide whether the work is real. Every item needs an owner and a date or it gets escalated.
Built 2026-07-31 · 3 teaching moments · 3 prompts