TianMind Studio / 天智工坊 is an AI-assisted full-stack studio for practical demos, service pages, internal tools, local-first knowledge workflows, public-safe GitHub assets, and verification-first handoff.
天智工坊把模糊想法、业务流程、材料和工具需求，整理成可打开、可验证、可交付的 demo、页面、脚本、README、案例和交付包。
This repository is the public service catalog for TianMind Studio. It helps outside readers understand:
- What TianMind Studio can build.
- Which public pages, demos, and templates can be reviewed first.
- How to prepare a safe first brief.
- Which evidence should exist before a project moves deeper.
- What must stay private.
这个仓库只放公开安全的服务说明和评估入口，不放客户资料、私有业务记录、内部系统配置或未确认事实。
| Service Line | Best Fit | Public Proof Path |
|---|---|---|
| AI workflow diagnosis | You have repeated manual work, scattered files, or unclear AI usage. | Fit check, scope sheet, proof ledger, and a small first sprint. |
| Full-stack demo and launch | You need a usable website, dashboard, tool, H5 page, or demo that can be opened and reviewed. | Demo gallery, demo proof kit, delivery standard, and public-safe case format. |
| Local-first knowledge and operations tools | You need a private workflow, context layer, or repeatable toolchain that stays under clear boundaries. | Public-safe architecture notes, templates, and redacted sample outputs. |
| Public packaging and repo trust | You need README, GitHub profile, service pages, case studies, proof packs, or reusable templates. | GitHub surface, public audit, trust queue, repo proof pack, and verifier checks. |
| Surface | Link | Use |
|---|---|---|
| Public studio | https://junius.tianmind.com/studio.html | Studio positioning, services, demos, proof, and boundary. |
| Service one-pagers | https://junius.tianmind.com/service-one-pagers.html | Buyer-ready service cards with fit, first package, proof, and safe starter materials. |
| First package menu | https://junius.tianmind.com/packages.html | Small first phases that can be scoped and checked before deeper work. |
| Buyer evaluation guide | https://junius.tianmind.com/buyer-evaluation.html | 15-minute public evaluation path. |
| Fit check | https://junius.tianmind.com/fit.html | Decide whether the work is a good fit before sharing private material. |
| Scope sheet | https://junius.tianmind.com/scope.html | Turn a first conversation into outcome, safe inputs, sprint shape, and acceptance evidence. |
| Proof ledger | https://junius.tianmind.com/proof-ledger.html | Map public claims to openable evidence and verification paths. |
| Demo proof kit | https://junius.tianmind.com/demo-proof.html | Package demo URL, screenshot, command, acceptance checks, and known boundaries. |
| Repo proof pack | https://junius.tianmind.com/repo-proof.html | Turn a public repo into a flagship trust asset. |
| GitHub trust queue | https://junius.tianmind.com/github-trust-queue.html | Prioritize README, demo, verification, and proof-ledger work for visible repos. |
| Trust center | https://junius.tianmind.com/trust.html | Verification-first public evidence and publishing boundary. |
Start with public-safe context:
- Desired outcome.
- Target user or reader.
- Current public link, redacted sample, or screenshot with private details removed.
- Preferred delivery shape: page, demo, script, README, workflow, or handoff pack.
- Review date or launch window.
- What must stay private.
Use the public brief template:
- Project brief: https://junius.tianmind.com/brief.html
- English buyer brief: https://junius.tianmind.com/templates/english-buyer-brief-template.md
A first public-safe package should usually include:
- A short scope sheet.
- A working page, demo, script, README, or template.
- A verification path: command, screenshot, checklist, URL, or static output.
- A handoff note with acceptance evidence.
- A boundary statement explaining what was not exposed.
Do not put these in public issues, README files, public pages, screenshots, or this repository:
- No customer files.
- No raw private conversations.
- No credentials, tokens, cookies, SSH keys, or account access.
- No contracts.
- No sensitive commercial records.
- No private backend access.
- No database dumps.
- No full private vault content.
- No Hermes or safe-index configuration.
- No unconfirmed claims.
Use public links, redacted samples, sanitized screenshots, sample outputs, and verification commands instead.
The public showcase that supports this service catalog is checked by:
npm run test:public-showcaseThe verifier checks required files, local links, sitemap coverage, catalog entries, AI-readable brief coverage, high-risk secret-like patterns, public boundary markers, and public-safe copy coverage.
Public contact: wx@tianmind.com
For public repo suggestions, open an issue with public context and redacted evidence only.