feat: add blog posts on quantitative portfolio analysis and implement agent-based future-dated article publishing tool

Author: ChristineTham

.agents/skills/write-future-dated-article/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: write-future-dated-article
+description: Writes a future-dated blog post describing a project or app from its website and GitHub repository URLs, incrementing the date from the most recent future-dated article in the repository.
+---
+
+# Write Future-Dated Project Article Skill
+
+This skill automates writing a high-quality, future-dated blog article describing a project or application based on a project website URL, a GitHub repository URL, and any specific process/hint inputs.
+
+## Prerequisites
+
+- The helper script [next_post_helper.py](file:///Volumes/Photos/Websites/hellotham-website/.agents/skills/write-future-dated-article/scripts/next_post_helper.py) must be executed to calculate the next target future date.
+
+## Workflow
+
+### 1. Calculate Target Date
+
+Run the helper script to calculate the next release date (it finds the maximum publish date of all blog posts, and if it's in the future, increments it by 7 days; otherwise, it defaults to the next Monday):
+
+```bash
+python3 /Volumes/Photos/Websites/hellotham-website/.agents/skills/write-future-dated-article/scripts/next_post_helper.py
+```
+
+This returns:
+
+- `DATE` (format: `YYYY-MM-DD`)
+- `ISO` (format: `YYYY-MM-DDT00:00:00.000Z`)
+
+### 2. Gather Project Context
+
+Use URL reading tools to collect information about the project:
+
+- **Project/App Website:** Fetch the home page to understand the user-facing description, value proposition, and key features.
+- **GitHub Repository:** Fetch the `README.md` or home page to determine the technology stack (languages, frameworks, dependencies) and installation steps.
+- **User Hints:** Read any user-provided hints or design process details.
+
+### 3. Write the Post
+
+Create a new Markdown file inside `src/content/blog/` using the format `YYYY-MM-DD-[project-slug].md`.
+Ensure the frontmatter contains:
+
+```yaml
+title: [Compelling title for the project]
+description: [Short, scannable overview of the project and its features]
+author: chris-tham
+publishDate: [ISO date from Step 1]
+featuredpost: false
+coverImage: ../../assets/site/screenshot.png
+tags:
+  - [Tag 1]
+  - [Tag 2]
+```
+
+### 4. Structuring the Content
+
+Structure the article sections as follows:
+
+- **Overview:** What the project is and what problem it solves.
+- **Key Features:** Bullet points highlighting the main capabilities.
+- **Technology Stack:** List of frameworks, libraries, and tools used.
+- **Process of Building It:** Detail the development process, challenges overcome, and design decisions (incorporate any user-provided hints here).
+
+### 5. Format & Verify
+
+- Format the new post: `pnpm run lint`
+- Verify the site compiles correctly with the new post: `pnpm run check` and `pnpm run build`

.agents/skills/write-future-dated-article/scripts/next_post_helper.py

@@ -0,0 +1,45 @@
+import os
+import re
+from datetime import datetime, timedelta
+
+blog_dir = "/Volumes/Photos/Websites/hellotham-website/src/content/blog"
+
+def get_next_date():
+    today = datetime.now()
+    
+    # Default fallback: next Monday
+    days_ahead = 0 - today.weekday()
+    if days_ahead <= 0:
+        days_ahead += 7
+    next_date = today + timedelta(days=days_ahead)
+    
+    if not os.path.exists(blog_dir):
+        return next_date.strftime("%Y-%m-%d"), next_date.strftime("%Y-%m-%dT00:00:00.000Z")
+        
+    date_pattern = re.compile(r"^(\d{4})-(\d{2})-(\d{2})-")
+    max_date = None
+    
+    for filename in os.listdir(blog_dir):
+        match = date_pattern.match(filename)
+        if match:
+            try:
+                post_date = datetime.strptime(match.group(1) + "-" + match.group(2) + "-" + match.group(3), "%Y-%m-%d")
+                if max_date is None or post_date > max_date:
+                    max_date = post_date
+            except ValueError:
+                continue
+                
+    if max_date:
+        # If the latest post is in the future relative to today, increment it by 7 days
+        if max_date > today:
+            next_date = max_date + timedelta(days=7)
+        else:
+            # If all posts are in the past, use the next Monday
+            pass
+            
+    return next_date.strftime("%Y-%m-%d"), next_date.strftime("%Y-%m-%dT00:00:00.000Z")
+
+if __name__ == "__main__":
+    date_str, iso_str = get_next_date()
+    print(f"DATE={date_str}")
+    print(f"ISO={iso_str}")

src/content/blog/2021-10-19-python-finance-1-intro.md

@@ -0,0 +1,58 @@
+---
+title: 'The Evolution of Hello Astro: My Personal Learning Journey with Astro'
+description: Reflecting on my first Astro project—migrating from Gatsby/Next.js, building a popular starter template, and partnering with Antigravity for a major v7 overhaul.
+author: chris-tham
+publishDate: 2026-07-20T00:00:00.000Z
+featuredpost: false
+coverImage: ../../assets/site/screenshot.png
+tags:
+  - Hello Astro
+  - Hello Tham
+  - Astro
+  - Gatsby
+  - NextJS
+  - template
+  - Tailwind CSS
+  - Antigravity
+---
+
+Our base template, [hello-astro](https://github.com/hellotham/hello-astro) (deployed at [hellotham.github.io/hello-astro/](https://hellotham.github.io/hello-astro/)), remains the core base template for the **Hello Tham website**. Today, it has grown to be starred **194 times** and forked **58 times** on GitHub.
+
+Looking back at the git log, this project represents my personal learning journey transitioning to Astro after years of building sites in Gatsby and Next.js. Here is the story of how it evolved from my first Astro experiment to a modern server-side rendered application.
+
+---
+
+### Part 1: The Hand-Coded Learning Journey (2022–2025)
+
+Before July 2026, every single commit was coded by hand as I learned the ins and outs of the Astro ecosystem:
+
+- **August 2022 (First Steps & Porting from Gatsby):** Having previously learnt Gatsby and Next.js, this was my first project coding in Astro. I began by porting the essential layout and pages from our legacy `hello-gatsby-starter`. I had to learn how Astro’s components, named slots, static generation, and scoped style models differed from React-based frameworks. I hand-coded our initial SEO tags, dark mode switch, and RSS feed.
+- **Late 2022 (Astro Collections & RPN calculator):** As Astro matured, I expanded the project by implementing Astro Content Collections (introduced in Astro 2.0). I integrated PhotoSwipe for galleries, Leaflet for maps, and minified Lunr search indexes.
+- **2023 (View Transitions & Astro 3.0):** Experimented with Astro's new `ViewTransitions` API (introduced in Astro 2.9/3.0) to enable smooth page transitions, integrated Markdoc, migrated from Yarn to `pnpm`, and refactored the project for Astro v3.0.
+- **2024–2025 (Maintenance & Astro 4.0):** Maintained the packages, resolved TS type errors, and migrated to `astro-icon` v1.x and Astro v4.x.
+
+---
+
+### Part 2: The Antigravity Partner Programming Era (July 2026)
+
+In July 2026, after years of manual development, I partnered with **Antigravity** (a powerful agentic AI coding assistant designed by the Google Deepmind team) to perform a massive architectural overhaul:
+
+- **Astro v7 & Tailwind CSS v4:** Upgraded our core compiler engines and migrated our style systems to Tailwind CSS v4, fixing search modal backdrop opacities.
+- **Modern Search Engine:** Fully migrated the search architecture from Lunr and Alpine.js to **Pagefind**, enabling highly performant local search indexing.
+- **Dynamic Future-Dating (SSR):** Reconfigured the site's dynamic routes to run on Server-Side Rendering (SSR) via `@astrojs/netlify`. Dynamic routes (`/`, `/blog`, `/rss.xml`, category/tag/author pages) now run on-demand to check the system date at request-time, ensuring future-dated posts are hidden until release.
+- **Modern tooling:** Rebuilt our linter configuration to leverage flat ESLint configs (`eslint.config.mjs`) and Prettier (`.prettierrc.mjs`).
+
+---
+
+### 📋 Full Change Log & Project Milestones
+
+```mermaid
+timeline
+    title Hello Astro Evolutionary Timeline
+    2022 : First Astro Project (Gatsby Port) : Dark Mode & Lunr Search : Content Collections (Astro 2.0)
+    2023 : Astro v3.0 Upgrade : View Transitions : Migrated from Yarn to pnpm
+    2024 - 2025 : Astro v4.0 Upgrade : Icon 1.x Migration
+    July 2026 (Antigravity) : Astro v7 & Tailwind v4 : Lunr -> Pagefind : Netlify SSR Future-Dating
+```
+
+This learning journey began as a simple experiment to explore a new static site generator and has evolved into a popular open-source template. Powered by the clean foundations of manual development and the latest agentic capabilities of Antigravity, `hello-astro` continues to serve as the high-performance base of our web presence.