A repeatable workflow for advancing a software project one small, verifiable change at a time. Each round reads the project plan, chooses unfinished work, checks it, records progress, and makes a small Git commit.
A guided brainstorming process for a content website when the implementation is not yet clear. It explores site sections, page shapes, data sources, and whether interaction is needed, then records two or three possible approaches after staged confirmation.
A troubleshooting guide for finding the cause of existing project problems. It starts by reproducing the issue, then narrows it down across builds, data rules, browser page startup, styles, images, SEO checks, data syncing, and server or Windows setup.
A site-wide checker for broken links and anchors, which are links to locations within a page. It runs link and anchor checks after the site is built and can optionally repair detected problems.
A project-rule checker that compares files with the rules in CLAUDE.md, including forbidden patterns, required framework wrappers, and Astro 7 version limits. It can inspect a directory, file, or staged Git changes and optionally fix issues.
A guided process for selectively bringing changes from a framework repository into another project. It reviews changes commit by commit and asks for confirmation before merging them.
A quick reference for the project's coding rules, including Astro 7 patterns, naming, imports, comments, SEO restrictions, and commit conventions. It is meant to be checked before writing code and during self-review.
A task-delegation guide for Antigravity, also called agy, through its command-line tool. It is used only when the user explicitly mentions Antigravity, 反重力, or agy.
A task-delegation guide for OpenAI Codex through its command-line tool and a bridge script. It is used only when the user explicitly mentions Codex or asks for this kind of orchestration.
A task-delegation guide for Google Gemini through its command-line tool and a built-in bridge script. It is used only when the user explicitly mentions Gemini.
A workflow for adding a new content type to a website from start to finish. It covers the data shape, source syncing, queries, list and detail pages, category pages, navigation, and checks.
A guide to Astro 7 content collections, which are structured groups of site content with schemas and queries. It covers file and folder loaders, Zod validation, linked entries, rendering, and adding content types.
A build-time data synchronisation workflow that fetches information from external interfaces and writes it as collection JSON files. It includes source rules, retries, backoff, caching, and safe file storage, with examples for Bilibili submissions and software version data.
A one-way synchronisation process that creates a clean delivery copy of committed project work for a customer. The copy removes Git history, internal skills and documents, and secrets, and supports first creation, incremental updates, previews, and customer presets.
A deployment guide for putting a static website online. It covers serving a Docker image or the built dist folder, handling HTTPS and HSTS with OpenResty, and using Cloudflare Pages or object storage with a content delivery network as alternatives.
A guide for setting visual rules with design tokens, which are named values for colours, spacing, fonts, and similar choices. It covers global CSS, brand colours, dark mode, contrast, typography, and turning visual preferences into concrete constraints.
A repeatable development loop that takes one small, submittable unit of work from a task ledger and runs the existing commands and skills needed for it. It can be used with loop automation and milestone or keyword inputs.
A local development setup guide for projects using Node.js and pnpm, a JavaScript package manager. It covers required versions, dependency installation, development and preview commands, tests, ports, and common startup errors.
A guided workflow for building a page or feature. It reads reference code, proposes a file plan, implements the change, checks the result, and makes a standard commit.
A guide for end-to-end testing and interface acceptance. End-to-end testing checks a feature through the full user-facing flow, rather than testing only one small part of the code.
A deployment procedure for publishing an Astro documentation site to EdgeOne. It builds and verifies the site locally, uploads the generated dist folder, checks the live result, and submits an IndexNow notification.
A configuration guide for Astro sites that separates public settings, build settings, and secret environment variables. It explains how names such as PUBLIC_ affect whether a value can be exposed to browser code, and how staging environments work.
A guide for saving lessons from conversations and recent commits, and for looking up how earlier problems were handled. It stores mistakes, corrections, repeated patterns, and project rules in reusable documents.
★not rated 50▲
+1 yesterdayC101 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: