AI-native project directory

Start at the root domain, then branch into the right repo with intent.

This site is the technical front door for NatsuFox projects. It is designed to capture root-domain search traffic, clarify what each project does, and route visitors to the right repository or live project page without forcing them to guess from repo names alone.

2 public repos currently featured and routed through this root domain
1 root hub host-level crawl control, sitemap, and internal discovery surface
Intent-first routing guide users by problem, not just repository labels
Search-ready pages canonical metadata, structured data, indexable project guides

Featured projects

Indexable entry pages for the public tools that already define the account.

The root domain should not duplicate full project landing pages. It should summarize, differentiate, and move qualified traffic deeper into the correct repo or project site.

2 matching projects

Knowledge Systems Live site available

Tapestry

AI-native web knowledge base and content intelligence workflow for turning URLs into durable, publishable knowledge assets.

web intelligence knowledge base agent workflow
Quant Research Repo-first

A-Stockit

AI-native A-share research and decision workflow for turning scattered market data into structured analysis, watchlists, and reusable outputs.

A-share investment workflow decision support

Route by need

Use-case paths that turn broad root-domain traffic into higher-intent clicks.

Visitors often know the problem they want solved before they know the project name. These routes are the root domain’s core click-through engine.

“I want to turn URLs into a searchable knowledge base.”

Tapestry is the right path if the job starts with web content capture, feed normalization, synthesis, and publishing.

“I want an AI-native workflow for A-share market research.”

A-Stockit is the right path if the job centers on watchlists, market interpretation, and reusable decision support in the China A-share market.

Root-domain role Capture broad branded and category traffic, then route it cleanly.
Project-page role Pre-qualify visitors with use-case specific explanations and repo links.
Repo-page role Convert qualified visitors into stars, docs readers, and users.

FAQ

Questions the root domain should answer before users bounce.

Why not send everyone straight to GitHub?
GitHub profiles are strong trust surfaces, but weak routing surfaces. The root domain gives each public project a search-optimized, intent-based entry page that can rank, explain, and then deliver better-qualified traffic into the repo.
What is the technical SEO job of this root domain?
Control host-level crawl signals, publish a clean sitemap, establish a canonical root hub, and create indexable project guides that capture broader discovery terms than repository names alone.
Will more projects fit here later?
Yes. The site is structured to expand with new project guide pages and a registry-backed sitemap workflow, while keeping the root page focused and easy to scan.
Current scope

The root hub currently focuses on the two public repositories visible on the account: Tapestry and A-Stockit.