AI Coding workflow: ship a site in ten minutes
Harden an AI-assisted SSG workflow with Cursor rules templates, so the coding agent stays inside a controlled boundary and ships runnable code.
Quick answer
Are Cursor rules and CLAUDE.md the same?
They are both hard-constraint files for coding agents, just for different tools. Both should pin stack, dependencies, and prohibitions.
Machine-readable page data: /data/ai-coding-workflow.json
In-depth analysis
AI Coding (Vibe Coding) means using agents like Claude Code, Cursor, and v0 to assist development: first encode your rules in CLAUDE.md or .cursorrules, then let the model produce runnable code inside that controlled context. The workflow: (1) write a rules file pinning stack, package manager, secret placeholders, and no-Chinese-comments policy; (2) one-command scaffold (npx create-astro@latest); (3) let the agent iterate under the rules, validate locally with a build. Bottom line up front: a rules file beats a long prompt, because context bloat dilutes attention. Common pitfall is pasting secrets into the conversation context where they echo back and leak.
# .cursorrules / CLAUDE.md — hard constraints for the coding agent (context tightening)
stack: Astro + Tailwind v4 + Cloudflare Pages (output: static)
package: pnpm only, lockfile committed, --frozen-lockfile in CI
secrets: always use the placeholder <CF_API_TOKEN>, never paste real values into code or conversation
comments: no Chinese in code or comments
# One-command scaffold
npx create-astro@latest my-site --template minimal --no-install
cd my-site && pnpm install && pnpm devAI Coding Overview · Key takeaways
- Tech choice and boundaries confirmed
- Core config in place
- Locally verified
- Postmortem notes recorded
FAQ & pitfalls
How do I keep AI-generated code from leaking secrets?
Secrets always go through placeholders. They never enter code or conversation context. CI uses --frozen-lockfile to lock dependencies.
Explore the hub
See all 5 guides in AI AgentsSame category as this article, sorted across the codebase.
AEO architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of AEO's layering and data flow.
AEO best practices: engineering conventions for production
Field-tested AEO practices from production, avoiding the common anti-patterns.
AEO deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven AEO deployment in practice: commit to build, atomic publish to every edge node.
AEO engineering practice: a full guide from architecture to production
Production architecture and core pain points for AEO.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 02
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide → - 03
Why are _headers / _redirects not taking effect?
Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.
See the full guide →