Back to Projects

AI-Assisted Data Tools

A-Share Data Analysis Tools

A small collection of AI-assisted A-share data tools. The two Streamlit apps organize intraday transactions, technical indicators, basic fundamentals, flow estimates, and risk views; the companion checker parses AKShare's stock documentation and tests endpoints with timeouts, retries, resume support, and structured reports.

Period

Aug 2025 - Jun 2026

Tools / Tech

PythonStreamlitAKSharePlotlyPandasScikit-learn

Why I built it

I used these projects to turn recurring market-data questions into reusable views and to understand how unstable upstream interfaces affect data tools. The outputs are for observation and review, not trading recommendations.

Links

What it includes

  • Presents intraday prices, tick transactions, large-order behavior, technical indicators, basic fundamentals, flow estimates, and risk statistics in Streamlit views.
  • Keeps data access, field normalization, analysis, charts, and page logic in separate modules so changing an AKShare field does not require rewriting the whole app.
  • Parses documented AKShare stock endpoints and runs each check in a separate process with timeout, retries, rate control, and resume support.
  • Writes searchable HTML plus CSV, JSON, and XLSX reports so failed endpoints can be reviewed rather than reduced to one pass/fail count.

What I worked on

  • Defined the questions each tool should answer and used AI assistance to implement and reorganize data fetching, cleaning, indicators, charts, and interface-checking workflows.
  • Reviewed generated code and reports against real AKShare responses, including alternate field names, empty data, timeouts, upstream failures, and cached results.
  • Separated experimental anomaly detection and classification examples from the main dashboards, and kept all financial wording at the level of observation rather than prediction.

What I Learned

  • Learned that a data tool needs to preserve error context because an endpoint failure can come from parameters, dates, rate limits, or an upstream provider.
  • Practiced reviewing AI-assisted modules as a connected workflow rather than accepting isolated code snippets.
  • Improved awareness of how financial-data uncertainty should be reflected in both interface behavior and wording.